Cox Cable blocking port 80 and scans

Bryce C wrote:
> The nearly static IP has been my experience too. In fact, I just set up
> my fw to use this static IP and every once in a long while (weekly I
> think), I run my version of a dhcp client just to let them know I'm
> still alive as they do stop service somewhere along the way if you
> haven't "pinged" them.

I don't think thats what is happening. More likely you have a small
power outage that reset your cable modem.
What happens is that your cable modem allows the first card that is gets
a DHCP request from to access the internet. Without the DHCP request
you can set it static and you'll never get though, even though you were
just using it 30 seconds before your cable modem was power cycled.
Thats also the reason you have to powercycle your cable modem if you
change ethernet cards. It needs to flush the old MAC address that it
was bound to.

> FYI, the reason I use a static IP setup is so I can use the DNS servers
> I want and not have them overwritten by the DHCP server's values. *&^*@
> DNS servers, never updating and whatnot.

You can configure your dhcp client to hand back whatever you want. In
dhclient just add a line like:
supersede domain-name "yourdomain.com anotherdomain.com";
supersede domain-name-servers 111.112.113.114;

or in my case, I would like to get cox's domain servers but I would
perfer that it checked my local DNS first, so I put:
prepend domain-name-servers 127.0.0.1;

in my /etc/dhcp3/dhclient.conf
there's a TON of other stuff you can do in there too. It's really worth
a look.

You can do similar things with dhcpcd, althought they don't seem to be
as powerful, but would meet your needs. Just checkout the config file
in /etc/dhcpc/config You just need to comment out a line like:
SET_DNS='Yes'
and that will keep your DNS entries.

My paths are from a debian box, your machine might be different.

Brian Cluff