eth0 does not start during boot, but can be started manually
From: richard (recw_at_pobox.com)
Date: 09/29/05
- Previous message: Filipus Klutiero: "[RESOLVED] Re: Re: upgrade problem"
- Next in thread: Steven Jones: "RE: eth0 does not start during boot, but can be started manually"
- Maybe reply: Steven Jones: "RE: eth0 does not start during boot, but can be started manually"
- Maybe reply: richard: "Re: eth0 does not start during boot, but can be started manually"
- Maybe reply: Steven Jones: "RE: eth0 does not start during boot, but can be started manually"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 Sep 2005 19:52:59 -0700 To: debian-user@lists.debian.org
this is probably a simple error but I'm stuck.
System: IBM ThinkPad 570E, Debian Sarge, KDE, w/ most current updates
(I
think). Kernel version 2.4.27-2-386. NB. on this machine, networking
is
via a plugin PCMCIA card.
After some upgrades:-
(kernel 2.4.27-1-386 to 2.4.27-2-386, but many other package upgrades
as well, via aptitude), networking behavior has changed.
Now, networking no longer starts at boot time, but can be started
(and runs
normally) after system is up (via /etc/init.d/networking start, or via
the kde network admin panel). (this behavior is now the same with
either
kernel version)
Since I can start networking manually, I'm guessing that
configurations are correct (see 'interfaces' content below), though I
don't
understand 2 aspects of the file :-
1) the split 'auto' statement (tried replacing with a single 'auto lo
eth0'
at top of file, but made no difference
2) the hotplug reference to eth0 (is this related to pcmcia?)
polyphony:/etc/network# cat interfaces
--------------start of interfaces---------------
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map eth0
# The primary network interface
iface eth0 inet static
# dns-* options are implemented by the resolvconf package, if
installed
dns-nameservers 207.217.126.81 207.69.188.85
name Ethernet LAN card
address 192.168.2.101
netmask 255.255.255.0
broadcast 192.168.2.255
network 192.168.2.0
gateway 192.168.2.1
auto eth0
----------end of interfaces-------------
So might it be a runlevel script problem?
I'd much appreciate some help in diagnosing and repairing this.
Thanks!
Richard
-- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
- Previous message: Filipus Klutiero: "[RESOLVED] Re: Re: upgrade problem"
- Next in thread: Steven Jones: "RE: eth0 does not start during boot, but can be started manually"
- Maybe reply: Steven Jones: "RE: eth0 does not start during boot, but can be started manually"
- Maybe reply: richard: "Re: eth0 does not start during boot, but can be started manually"
- Maybe reply: Steven Jones: "RE: eth0 does not start during boot, but can be started manually"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Signal Strength 0
... Have Intel 2200BG Pro Wireless card and am sitting right next to Netgear router. ...
Kwifimanager is telling me correct connection speed 55MBits, correclty connected to network,
access pont and frequency channel. ... # This is a list of hotpluggable network interfaces.
... (Ubuntu) - Re: network interface not showing up in network device control app
... > When I run the network device control app under the systems tools menu, ...
> the window that pops up that normally shows network interfaces, ... (Fedora) - Re: Secure desktop idea?
... stealth IDS systems (attach them to network interfaces with no IP addresses,
... If you assume the model that all network interaction is driven by the ... interface
down or changed the IP address in addition to the route. ... (Security-Basics) - pesky network connectivity on Dell PowerEdge 1850
... PowerEdge 1850 with two Xeon processors and two onboard Intel PRO/1000 ... network
interfaces. ... periodically lose connectivity to network services on that host.
... (Debian-User) - Re: Newbie --Admin access problem on KDE... HELP!!
... On 9/10/05, Kent West wrote: ... >>So I need network connection,
... >>#This is a list of hotpluggable network interfaces. ... >># They
will be activated automatically by the hotplug subsystem. ... (Debian-User)