Re: Interface lo Not Coming Up
On Tue, 27 May 2003, Jeff wrote: > > This ran fine. However, eth0 is not plugged in and I have to wait for > the DHCP process to timeout. That's why I had initially removed the > 'dhcp' part from the /etc/network/intefaces file, to speed things up. > And, once eth0 times out, it gets configured anyway with a recorded > lease, which is not what I want. I want the interface to remain down, so > as not to confuse the system. > > Is there a good way to do accomplish this? That is, if no dhcp > response is recieved to have the interface remain down? Not exactly what you're asking for, but how about removing the "auto" option from eth0, so you have to bring it up and down manually? That way you won't have to wait for the DHCP timeout before continuing. ap -- Andrew J Perrin - http://www.unc.edu/~aperrin Assistant Professor of Sociology, U of North Carolina, Chapel Hill [EMAIL PROTECTED] * andrew_perrin (at) unc.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Interface lo Not Coming Up
Thomas Krennwallner, 2003-May-27 16:43 +0200: > Hi! > > On Tue May 27, 2003 at 07:23:41AM -0700, Jeff wrote: > > When I boot my PC, the local loopback interface, "lo", does not come > > up. Running 'ifconfig -a' is see it there, but it has not IP > > configuration. > > What's the output of: > # ifdown lo > # ifup lo $ sudo ifdown lo /etc/network/interfaces:9: too few parameters for iface line ifdown: couldn't read interfaces file "/etc/network/interfaces" $ sudo emacs /etc/network/interfaces & [2] 4547 Hmmm, I compared the interfaces file to another system that works fine and made a few changes. After a few tries, both ifup and ifdown work now. I orginally had 'auto lo eth0 eth1', but changed that to have two different 'auto' lines, one for lo and one for eth0 and eth1. That didn't fix it though. On my eth0 iface line I had 'iface eth0 inet'. This is what was causing the problem. I added 'dhcp' to the end of the line and that fixed it. My final version is # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) auto lo iface lo inet loopback auto eth0 eth1 iface eth0 inet dhcp iface eth1 inet dhcp > Does > # /etc/init.d/networking restart > work properly? This ran fine. However, eth0 is not plugged in and I have to wait for the DHCP process to timeout. That's why I had initially removed the 'dhcp' part from the /etc/network/intefaces file, to speed things up. And, once eth0 times out, it gets configured anyway with a recorded lease, which is not what I want. I want the interface to remain down, so as not to confuse the system. Is there a good way to do accomplish this? That is, if no dhcp response is recieved to have the interface remain down? thanks, jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lo not coming up
on Mon, Jun 17, 2002, Dr. Sharukh K. R. Pavri. ([EMAIL PROTECTED]) wrote: > I am running woody. On boot up, ifconfig does not show the lo interface. > Only the tap0 interface is up. why is this so ? I thought having lo was > essential to quite a few programs. > > How do I start it up by default at boot up ? In /etc/network/interfaces: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface # automatically added when upgrading auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 network 127.0.0.0 broadcast 127.0.0.255 gateway 127.0.0.1 ...if you have the ifupdown package installed, that should have been configured for you. ...then /etc/init.d/networking will bring this up for you automatically. Peace. -- Karsten M. Self http://kmself.home.netcom.com/ What Part of "Gestalt" don't you understand? This sig for rent: a Signify v1.07 production from http://www.debian.org/ pgpT54N4MDi8D.pgp Description: PGP signature
lo not coming up
I am running woody. On boot up, ifconfig does not show the lo interface. Only the tap0 interface is up. why is this so ? I thought having lo was essential to quite a few programs. How do I start it up by default at boot up ? regards, Sharukh. -- Dr. Sharukh K. R. Pavri Homeopath and Linux Enthusiast. Mumbai, India. http://www.pavri.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
