Well, this may put a hiccup in the theory that the cable company's DHCP is messed up...
I've seen exactly the same thing happen on my two RedHat systems (one is 7.3 and one is 7.2). I've not found any pattern that would help to identify what is really going on though. I do not use a cable modem. I do have an SMC Barricade router/switch/DHCP server that I use with a modem attached to it for sharing one net connection. The Barricade seems to settle on a particular IP address for each port and then stick with that address forever. So as long as I keep each box plugged into the same port it gets the same IP address every time. That would indicate that it is not a problem related to changing IP addresses. It still might be DHCP related but I haven't a clue what the relation might be. Michael O'Donnell wrote: > Here's a sequence of events (or observations) for which I'd > love to hear an explanation, or even a plausible guess: > > My firewall box was just running like it always > does. From a machine behind it, I started four or > five SSH sessions to a remote system (my employer) > and was busy using those masqueraded connections > when everything just froze. After saying many > bad words and flailing about on that internal > machine for a while, I eventually walked over to > the console of my firewall box (which is a DHCP > client of the AT&T cable modem network's DHCP > server) and said "ifconfig" and saw the following - > note how for eth0 it fails to mention any IP addr, > Bcast addr, etc... > > eth0 Link encap:Ethernet HWaddr 00:60:08:42:50:73 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1480187 errors:973 dropped:0 overruns:0 frame:973 > TX packets:239467 errors:0 dropped:0 overruns:0 carrier:0 > collisions:2290 txqueuelen:100 > RX bytes:220287284 (210.0 MiB) TX bytes:35966230 (34.3 MiB) > Interrupt:10 Base address:0x300 > > eth1 Link encap:Ethernet HWaddr 00:C0:DF:62:26:38 > inet addr:192.168.0.1 Bcast:192.168.1.255 Mask:255.255.254.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > . > . > . > . > ...at which point I said "WTF?!?!' and issued the following commands: > > ifdown -a > ifup -a > > ...which had the desirable but mystifying effect of (apparently) > fixing everything; ifconfig subsequently reported: > > eth0 Link encap:Ethernet HWaddr 00:60:08:42:50:73 > inet addr:24.128.xxx.yyy Bcast:255.255.255.255 Mask:255.255.252.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1480410 errors:973 dropped:0 overruns:0 frame:973 > TX packets:239476 errors:0 dropped:0 overruns:0 carrier:0 > collisions:2290 txqueuelen:100 > RX bytes:220307258 (210.1 MiB) TX bytes:35968421 (34.3 MiB) > Interrupt:10 Base address:0x300 > > eth1 Link encap:Ethernet HWaddr 00:C0:DF:62:26:38 > inet addr:192.168.0.1 Bcast:192.168.1.255 Mask:255.255.254.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > . > . > . > . > > I figured that maybe I just lost my DHCP lease or > something, but the outage lasted almost 15 minutes before > I (apparently) "fixed" it by issuing those ifdown/ifup > commands, so I wonder about the DHCP theory... > > > --M > > > ***************************************************************** > To unsubscribe from this list, send mail to [EMAIL PROTECTED] > with the text 'unsubscribe gnhlug' in the message body. > ***************************************************************** > > > -- Dan Coutu Managing Director Snowy Owl Internet Consulting, LLC http://www.snowy-owl.com/ Mobile: 603-759-3885 Fax: 603-673-6676 ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
