On Thursday 12 December 2002 03:27 am, -ray wrote:
> On Wed, 11 Dec 2002, Charles wrote:
>
> > As for the "68.14.X.X" IP blocks. If you obtain one from the DHCP
> > server it is a mistake. This block is reserved for our business
> > customers. And yes since they are part of the business block of
> > course they will allowed servers to pass traffic. If you are
> > "borrowing" one, down and dirty you are stealing.
>
> Hmmmm.... sure someone might down and dirty steal my car if i leave it in
> a parking lot. That doesn't mean i'll leave the windows down with keys in
> the ignition. Bottom line, if the network was properly secured, you
> wouldn't need to quietly handle abusers. We're not talking rocket
> science... if you see traffic from an ip with no lease, block it.
>
> And why are business customers on the same network as residential
> customers? I'm sure there is verbage somewhere that says the business
> service is more "secure and reliable, that's why we charge more for it."
> I would think it should be separate networks. Who gets to explain to the
> business customers why their e-commerce site turned into a porn site for a
> few hours cause little 12-year old Johnny borrowed their IP for a little
> while?
One of my friends from work had Cox@Work for a while, and although they
called it (and charged for) business service, his speeds were horrible once
everyone in the neighborhood got on. He wanted to switch to DSL, but
for some reason his phone can't support it in Kenner. About a month or
two ago, he switched back to residential using the modem I used to have.
There wasn't anything wrong with the modem, but for some reason it
would lease an IP address, so they gave up and gave him back the
static IP address he had with @Work. So.... residential customers can
get a static IP address assigned to them if they have enough patience.
And yes, Cox business internet is a blatant rip-off, as it is the same crappy
service as residential, just more money.
Andy Johnson
>
> I don't mean to start anything, and Charles i appreciate the info you have
> provided. But to the current and future network managers, this sort of
> abuse is preventable with proper network security. Falling back on your
> acceptable-use policies, contacting authorities, calling abuse managers,
> quietly handling users, etc etc etc... that's not the right way to handle
> it. If someone sniffs your admin password cause you are telnetting, you
> can't run to the CEO and say 'oh no no it's ok cause he violated the AUP
> by running a sniffer'. That won't cut it.
>
> Email abuse, breaking into other systems, threats, harassment... that is
> abuse, and by all means contact abuse managers and local authorities and
> get it dealt with. But don't threaten to sic the law on me cause i
> "borrow" an IP address. Just secure your network. I guarantee it'll be
> cheaper and cause everyone less headaches in the long run.
>
> -Ray
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Ray DeJean http://www.r-a-y.org
> Systems Engineer Southeastern Louisiana University
> IBM Certified Specialist AIX Administration, AIX Support
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> ___________________
> Nolug mailing list
> nolug@nolug.org
>
___________________
Nolug mailing list
nolug@nolug.org
Received on 12/12/02
This archive was generated by hypermail 2.2.0 : 12/19/08 EST