Have you tried using dhcpcd? Pump has some problems. Ken Ambrose said: >I see it frequently enough that I've taken to putting "pump" into cron. >Clearly, if DHCP were working the way it should, it wouldn't be an issue. >Since I plan on switching to DSL in the not-too-distant future, I haven't >bothered attempting to get Adelphia's brain-dead techsupport to t-shoot it >for me. > >-Ken > >On 11 Jul 2002, Kenneth E. Lussier wrote: > >> I have actually seen this before. Back when I had a cable modem, this >> would happen to me occasionally. The best explanation that I can give is >> that the DHCP server gave your IP address to someone else on your >> segment for reasons that I cannot fathom, nor could attbi suitably >> explain. Two systems end up with the same IP address, and everything >> goes wonky. Of course, it could be something completely different. >> >> C-Ya, >> Kenny >> >> On Thu, 2002-07-11 at 21:07, 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.25 >2.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. >> > ***************************************************************** >> -- >> "The ebb and flow of the Atlantic tides. >> The drift of the continents. >> The very position of the sun along it's ecliptic. >> These are just a few of the things I control in my world." >> >> >> ***************************************************************** >> To unsubscribe from this list, send mail to [EMAIL PROTECTED] >> with the text 'unsubscribe gnhlug' in the message body. >> ***************************************************************** >> >> > > >***************************************************************** >To unsubscribe from this list, send mail to [EMAIL PROTECTED] >with the text 'unsubscribe gnhlug' in the message body. >***************************************************************** >
-- ------- Tom Buskey ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
