Re: firewall eth0 weirdness
On Fri, 12 Jul 2002, at 10:06am, Michael O'Donnell wrote: > - I am using pump and this isn't the first time I've heard >its reliability questioned, so I'll give dhcpcd a try. It isn't so much that ISC dhcpcd is better or worse then pump; it is just that it happens to get along with some DHCP servers better. Likewise, there are DHCP servers that ISC dhcpcd does not like, that pump works well with. So when one doesn't work, you try the other. -- Ben Scott <[EMAIL PROTECTED]> | The opinions expressed in this message are those of the author and do not | | necessarily represent the views or policy of any other person, entity or | | organization. All information is provided without warranty of any kind. | * To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *
Re: firewall eth0 weirdness
In response to several points raised: - Yes, all my NAT'd connections probably would have been killed as a result of the ifdown/ifup sequence, but they were dead already. - When my firewall's eth0 connection became operational again, it had the same IP addr as before. - I am using pump and this isn't the first time I've heard its reliability questioned, so I'll give dhcpcd a try. Thanks to all for the feedback. * To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *
Re: firewall eth0 weirdness
On Thu, Jul 11, 2002 at 09:07:31PM -0400, Michael O'Donnell wrote: > > 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... > My old RH5.2 box that was acting as a NAT did the same thing, usually when MediaAT&Comcast decided to change my IP address. I was probably using pump at the time, but it didn't happen the regularity you're seeing. IIRC, bringing the interface down and up again will kill off any NAT connections you have. iptables may be smart enough, but I'm not sure. -Mark * To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *
Re: firewall eth0 weirdness
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. *
Re: firewall eth0 weirdness
On Thu, 11 Jul 2002, at 7:56pm, Ken Ambrose wrote: > I see it frequently enough that I've taken to putting "pump" into cron. Try switching from "pump" to ISC "dhcpcd". A lot of people have reported trying one, having troubles, switching to the other, and that solves their problem. It appears each one gets along with various DHCP servers better than the other one. -- Ben Scott <[EMAIL PROTECTED]> | The opinions expressed in this message are those of the author and do not | | necessarily represent the views or policy of any other person, entity or | | organization. All information is provided without warranty of any kind. | * To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *
Re: firewall eth0 weirdness
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
Re: firewall eth0 weirdness
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.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. > > * > -- > "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. *
Re: firewall eth0 weirdness
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.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. > * -- "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. *
