Well I was going to say the cable modem is the key. I guess it depends on what the modem itself does. My modem is a: Toshiba PCX2200 (http://www.toshiba.com/taisnpd/products/pcx2200.html) I assume it's the standard Cox modem. I got it from them. I assume that this behavior is a "feature" of the modem itself. It's really not that big of a deal now that I know how to get around it, but it can be agrivating if you don't know it's there.
As far as your setup, you have changed the machine that goes to the cable modem in each one of those changes? You used a different NIC each time? Perhaps you have a different modem than I? Two years ago when I first got the Cox (or @home) modem I didn't have any problem with this issue. But then I had a RCA modem. -- Brad Bendily - CNA On Sun, 11 Aug 2002 [EMAIL PROTECTED] wrote: > Now this is interesting. I've never had this symptom. I've taken my Linux > firewall out of the circuit and plugged a Windows box in, no problem. > Replaced my Linux firewall with a different box running ipchains, no problem. > Replaced my ipchains firewall with one of those "broadband router-switches", > no problem. My current situation is that I've got a cable modem, a D-Link > broadband router-switch, and a spread of machines receiving dhcp from the > router (NOT Cox) that changes regularly. If MAC addresses are an issue, they > must be looking at the MAC address of the cable modem itself, because that's > the only ingredient in my network that hasn't changed at least twice this > summer! (Actually, I even got a new cable modem this spring...) > > -j > > > > > From: Brad Bendily <[EMAIL PROTECTED]> > > Date: 2002/08/11 Sun AM 12:52:16 EDT > > To: [email protected] > > Subject: Re: [brlug-general] @Home DHCP saga continued > > > > Actually, I had the same problem. I called and said I needed to use a > > laptop from work on my cable connection. They said turn the modem off for > > about 5 minutes, this clears some file that the modem stores your MAC > > address in. Then plug in the new NIC. Works like a champ. I've had to > > do this several times. > > > > I was going to be pretty pissed off if they were to tell me I had to let > > them know every time I changed network cards. Fortunately I didn't have to > > yell at anybody! ;) > > > > > > -- > > Brad Bendily - CNA > > > > > > On Sat, 10 Aug 2002, Tim Fournet wrote: > > > > > I'm using RH 7.2 on my machine with dhcpcd and it works fine. When the > > > installer came by, I had him do all the installation on a Windows 2000 > > > box, > > > then after he left, I moved the card over to the linux one. The cable > > > connection didn't seem to agree with the nic that was already in the linux > > > machine, so I'm assuming it ties the account to the MAC address. Running > > > dhcpcd with the -d option, as well as tail -f /var/log/messages in the > > > background _should_ show you what's going on. I'm not clear from your > > > original post, do "windows side" and "linux side" refer to the same > > > machine > > > dual-booting, or different boxes? If they're different, I'd definitely > > > swap > > > their nics. > > > > > > -Tim > > > > > > > > > ----- Original Message ----- > > > From: "Terry Stockdale" <[EMAIL PROTECTED]> > > > To: <[email protected]> > > > Sent: Saturday, August 10, 2002 7:34 PM > > > Subject: Re: [brlug-general] @Home DHCP saga continued > > > > > > > > > > IFIRC, back in the days of RH70 and @Home, folks had to use pump instead > > > of > > > > dhcpcd. You might try that. I'm not sure you specified which distro > > > > and > > > > version you were using. > > > > > > > > On the subject of dhcpcd verbose option, you can always use the -d > > > > option. Quoting from the man file: > > > > -d With this flag dhcpcd will syslog(LOG_DEBUG,...) messages for > > > about > > > > every step it does. It's > > > > recommended to use this option since it > > > > doesn't really produce too much output but will > > > > greatly help in resolving a problems if any. > > > > > > > > > > > > At 06:15 PM 8/10/2002 -0500, John Cole wrote: > > > > >Tim- > > > > > > > > > >I was mistaken in my original statement. Further poking around shows > > > that > > > > >dhcpcd is not receiving anything back from Cox at all. The IP address > > > > >et > > > > >al.. which I thought were from Cox were cached settings from another > > > > >DHCP > > > > >experiment. dhcpcd does not have a verbose option, and returns without > > > > >writing anying to /etc/dhcpc, /etc/dhcpcd, or resolv.conf. I am going > > > > >to > > > > >do some more reading. If you have any thoughts, I would appreciate > > > > >hearing them. > > > > > > > > > >John. > > > > > > > > -- > > > > Terry Stockdale -- [EMAIL PROTECTED] -- Baton Rouge, LA > > > > website: http://www.dadstoy.net > > > > > > > > > > > > > > > > _______________________________________________ > > > > General mailing list > > > > [email protected] > > > > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > > > > > > > > > _______________________________________________ > > > General mailing list > > > [email protected] > > > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > > > > > _______________________________________________ > > General mailing list > > [email protected] > > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net >
