Re: Troubleshooting connection loss (continued)
- From: Allen Weiner <alweiner7@xxxxxxxxxxx>
- Date: Fri, 09 Nov 2007 16:36:24 GMT
Bit Twister wrote:
On Fri, 09 Nov 2007 04:22:10 GMT, Allen Weiner wrote:I'm not sure what you're asking. If you are asking about the time that Fedora became unbootable, here is the history:This problem is frustrating. I firmly believe (with almost no supporting evidence) that a reboot to regain a lost Internet connection should be a last resort.
I agree.
I might have missed it, but is that first boot after winME was running?
1. WinME ran with static IP on 11/3
2. Fedora ran OK with static IP on 11/4
3. Fedora failed to boot on 11/5.
You commented that it is OK to have dual boot where Linux uses static IP and Windows uses dynamic IP. To keep things simple, this is the config I would prefer. I kinda thought that when I configured for static IP, something was being permanently stored in flash memory in the NIC and/or modem/router. I thought that if I left Windows with dynamic IP, it would undo those flash changes I configured from Fedora.
I also believe (again with no supprting evidence), that there should be a straightforward troubleshooting procedure when a "service network restart" hangs.
It is staight forward, ethtoo/mii-tool says the nic is connected and
ping should tell where it fails.
So far, my guess is riding on the router is refusing the connection
because the dhcp lease issued to winME has expired. That is why I wanted your fedora
/etc/hosts file set somewhat as follows:
$ head -3 /etc/hosts
127.0.0.1 localhost
192.168.1.140 fedora.home.invalid fedora
192.168.1.1 gateway
$ cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=fedora.home.invalid
and you have set eth0 up as static for ip 192.168.1.140
I've been going over your suggested changes from both threads. For the time being, I want to make only changes needed for troubleshooting. For now, I'm not concerned about apps which want to communicate over 127.0.0.1. (I'm not aware of any problem this has caused.)
I'm concerned about making changes that will render Fedora unbootable. (I've already had a close call with the change to static IP). I don't have the experience to repair Fedora if it becomes unbootable.
Before making changes, I'm going to do some googling into /etc/hosts and FQDN to try to raise my confidence level. Also, I'd feel much more comfortable if I understood what went wrong with my change to static IP.
By the way, I remembered that I have a Ubuntu 6.06 CD. I've got many gigs of free HDD space, and available logical partitions. But that is too much of a detour to fix this problem.
.
- Follow-Ups:
- Re: Troubleshooting connection loss (continued)
- From: Bit Twister
- Re: Troubleshooting connection loss (continued)
- References:
- Troubleshooting connection loss (continued)
- From: Allen Weiner
- Re: Troubleshooting connection loss (continued)
- From: Clifford Kite
- Re: Troubleshooting connection loss (continued)
- From: Allen Weiner
- Re: Troubleshooting connection loss (continued)
- From: Bit Twister
- Troubleshooting connection loss (continued)
- Prev by Date: Re: Troubleshooting connection loss (continued)
- Next by Date: Re: Troubleshooting connection loss (continued)
- Previous by thread: Re: Troubleshooting connection loss (continued)
- Next by thread: Re: Troubleshooting connection loss (continued)
- Index(es):
Relevant Pages
|