Re: Network connections breaking after bootup
Hello Mumia:
On Tuesday 15 May 2007 03:28, Mumia W.. wrote:
> I suggest that you dedicate a runlevel, say 3, to debugging this
> problem. For RL (runlevel) 3, disable as many services as
> possible--making it almost the same as RL 1; then re-enable only those
> services that get you basic network connectivity. Note the configuration.
>
> Then re-enable more services until network connectivity is broken again.
> The last service that you enabled will probably be the culprit.
Will try this tomorrow.... (late here)
> I didn't see you say specifically whether or not you installed the beta
> version of Etch. Certainly if you still have the beta Etch, it's a good
> idea to update; I know, it's a catch-22 with the network down, but
> sneakernet (walking CD-ROMs from one machine to another) is an option.
> You could be facing a bug in the beta that has been fixed in the release
> version of Etch.
It was my _intention_ to download the *stable* version.
I downloaded the following:
debian-40r0-amd64-netinst.iso
Did I get the correct one?
> Back in RL 2, see if you can get the output from "route -n" before the
> connectivity is broken; after connectivity is broken, do another "route
> -n" and capture the output; post both output files here.
output follows:
before:
---------------------------------------------------------------------------------------
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
------------------------------------------------------------------------------------------
after
-------------------------------------------------------------------------------------------
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
-------------------------------------------------------------------------------------------
Given that I did the capture correctly, I don't see a difference.
> BTW, the "script" command is great for recording all text data from a
> terminal session.
Great tip.
As for debugging via runlevel, it is late here and will try that in the
morning, given that I understand your instructions fully.
thank you
tim
--
Tim Johnson <tim@johnsons-web.com>
Palmer, Alaska, USA
Reply to: