You have two ways of resolving this issue.
1) Keep your linux box connected for a couple of days with cable modem
(see reason below)
mins - 4hrs)
Whats going on.
Your cable modem is hooked to an ATM network. The ATM switch has a
cache of mac addresses that it is performing switching for. When you
hook up a different NIC to the cable modem the Mac address entry in the
ATM switch is now incorrect. All packets you send to the switch are
discarded. Once in while (not sure how long a while is) the ATM switch
will decide to update its cache and if you have changed the NIC, the
switch will update its switching table with the mac address for the new
So you can either wait, or suffer through LONG phone holds and
incompetent Level I tech support. Hard part is going to be to get the
Level I techs to understand what Mac addresses are, and why you need to
talk to Level II engineers. BTW only Level II engineers can re-push
> I had been sucessfully using a Linux Box as a ipchains firewall to
> After a month and a half of successful operation, today, it suddenly
> working. I don't think I touched *anything* to break the setup. But,
> it works fine. But when I switch back to my cable modem, it does not.
> dhcpcd seems to correctly determine the ip address and name server
> when I try a nslookup, I get:
> *** Can't find server name for address xxx.xxx.xxx.xxx: No response
> When I switch back to my NT connected to the cable modem, the NT box
> Anybody else suddenly getting this type of problem?
Sent via Deja.com http://www.deja.com/
Before you buy.