Recovering net connection. (kinda long)
Every once in a while, @home has a service outage (a little more frequently in my case since I live out in the sticks). Of course, when the net connection is down, I can't ping my router, or gateway, or anything other than my local box. The problem is that it seems that after @home has their end back up and running, the only way that I can get my net connection back is to reboot my machine. There _has_ to be another way to do this. Recently, @home dropped my connection. After I was assurred that everything was up and running on their end, I tried pinging the gateway and got nothing. I did a tcpdump -i eth0 and found that my box was making a bunch of arp request for the owner of the gateway address. But I also saw that the arp requests were saying to send a response to chester.fedwy1.wa.home.com. The problem is, @home doesn't know who chester is, they think I'm cxx-a (I forget the number right now, but it's not important). So, thinking that I'm clever, I changed my /etc/hostname to what @home said it should be. I still couldn't ping my router, and I goofed up X and syslog as well (I'm really clever that way). Since syslog was really being a booger and not starting up like it should (obviously becase of the hostname issue), I decided to reboot into single user mode and fix the problem. Well, I goofed that up too, and went into normal startup, but my box had already fixed the hostname issue and everything started up fine, including networking. So, I know that one way to fix this problem is to reboot my box, but I don't want to have to do that every time @home drops my connection. Any suggestions? Sorry for the long post. Thanks for the help. -- Stephen W. Juranich [EMAIL PROTECTED] Electrical Engineering http://students.washington.edu/sjuranic University of Washington http://rcs.ee.washington.edu/ssli
Re: Recovering net connection. (kinda long)
Steve Juranich wrote: Every once in a while, @home has a service outage (a little more frequently in my case since I live out in the sticks). Of course, when the net connection is down, I can't ping my router, or gateway, or anything other than my local box. The problem is that it seems that after @home has their end back up and running, the only way that I can get my net connection back is to reboot my machine. There _has_ to be another way to do this. Recently, @home dropped my connection. After I was assurred that everything was up and running on their end, I tried pinging the gateway and got nothing. I did a tcpdump -i eth0 and found that my box was making a bunch of arp request for the owner of the gateway address. But I also saw that the arp requests were saying to send a response to chester.fedwy1.wa.home.com. The problem is, @home doesn't know who chester is, they think I'm cxx-a (I forget the number right now, but it's not important). So, thinking that I'm clever, I changed my /etc/hostname to what @home said it should be. I still couldn't ping my router, and I goofed up X and syslog as well (I'm really clever that way). Since syslog was really being a booger and not starting up like it should (obviously becase of the hostname issue), I decided to reboot into single user mode and fix the problem. Well, I goofed that up too, and went into normal startup, but my box had already fixed the hostname issue and everything started up fine, including networking. So, I know that one way to fix this problem is to reboot my box, but I don't want to have to do that every time @home drops my connection. Any suggestions? Sorry for the long post. Thanks for the help. -- Stephen W. Juranich [EMAIL PROTECTED] Electrical Engineering http://students.washington.edu/sjuranic University of Washington http://rcs.ee.washington.edu/ssli -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null I think i have a similar setup with me... A linux box with a cable-modem that configures by dhcp? Well.. Why don't you build a perl script that runs in daemon mode, checking that you are up in the network. if you are disconnected it runs again the dhcp daemon script. Just an idea. André Esteves - PT Portugal -- LINUX EMPOWERS!!! If you have the guts to it...
Re: Recovering net connection. (kinda long)
I heard that Steve Juranich wrote this on 28/10/00: So, I know that one way to fix this problem is to reboot my box, but I don't want to have to do that every time @home drops my connection. I use NetCabo (a portuguese cable internet provider). We sometimes have this problem, as NetCabo frequently has service interruptions and, after that, I can't ping any machine besides my own. I usually do this instead of rebooting: dhcpcd -k eth1 dhcpcd -R eth1 (note that my internet NIC is eth1, and that I use the -R option in dhcpcd, which not everyone uses)... If you are using pump instead of dhcpcd, try this: pump -i eth1 -k pump -i eth1 That should do it... Regards, sena... -- [EMAIL PROTECTED] http://decoy.ath.cx/~sena/
Re: Recovering net connection. (kinda long)
On Sat, 28 Oct 2000 10:35:11 -0700 (PDT), Steve Juranich said: Every once in a while, @home has a service outage (a little more frequently in my case since I live out in the sticks). Of course, when the net connection is down, I can't ping my router, or gateway, or anything other than my local box. The problem is that it seems that after @home has their end back up and running, the only way that I can get my net connection back is to reboot my machine. There _has_ to be another way to do Well i have a GI sb3100 cable modem and to solve this problem all i have to do is reboot the modem by unplugging the ac power cord , waiting 20 secs and replugging. Incidently if you know your modems ethernet ip address, (mine is 192.168.100.1) just point your browser at it for some info and help pages. -- gEEk||dOOd^Deb+iaNXFce$aaZZ goesPronto(-_-)
