Re: persistent interface
> Is there good documentation somewhere about mapping stanzas in the > interfaces file? I've read the `interfaces' man page, and the stuff in > /usr/share/doc/ifupdown. They're both very helpful, but a bit cryptic. You might also want to read the Networking chapter of the Debian Reference. -- Thomas Hood
Re: persistent interface
> Is there good documentation somewhere about mapping stanzas in the > interfaces file? I've read the `interfaces' man page, and the stuff in > /usr/share/doc/ifupdown. They're both very helpful, but a bit cryptic. You might also want to read the Networking chapter of the Debian Reference. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: persistent interface
This was really clarifying; thank you. [EMAIL PROTECTED] (Thomas Hood) wrote: |> It looks as if you are under the impression that "mapping" is an |> option for "iface eth1 inet dhcp". Actually it should be a |> separate stanza. You're absolutely right; I was. |> Strictly speaking, this means that only the loopback interface "lo" |> is brought up by /etc/rcS.d/S40networking. |> |> Other interfaces can be brought up while the system is booting |> via the hotplug mechanism. Your stanza |> |> mapping hotplug |> script echo |> |> enables this mechanism. I believe that this was (at least a good part of) my problem. When I replaced this with your suggested: |> mapping hotplug |> script grep |> map eth1 the boot process did not hang as it did before. There are other things that I still have to understand here, but this is definite progress. More importantly, I've learned a lot from the two threads I've been involved in here, and I'm grateful to everyone who contributed. Is there good documentation somewhere about mapping stanzas in the interfaces file? I've read the `interfaces' man page, and the stuff in /usr/share/doc/ifupdown. They're both very helpful, but a bit cryptic. Cheers and thanks, Jim
Re: persistent interface
This was really clarifying; thank you. [EMAIL PROTECTED] (Thomas Hood) wrote: |> It looks as if you are under the impression that "mapping" is an |> option for "iface eth1 inet dhcp". Actually it should be a |> separate stanza. You're absolutely right; I was. |> Strictly speaking, this means that only the loopback interface "lo" |> is brought up by /etc/rcS.d/S40networking. |> |> Other interfaces can be brought up while the system is booting |> via the hotplug mechanism. Your stanza |> |> mapping hotplug |> script echo |> |> enables this mechanism. I believe that this was (at least a good part of) my problem. When I replaced this with your suggested: |> mapping hotplug |> script grep |> map eth1 the boot process did not hang as it did before. There are other things that I still have to understand here, but this is definite progress. More importantly, I've learned a lot from the two threads I've been involved in here, and I'm grateful to everyone who contributed. Is there good documentation somewhere about mapping stanzas in the interfaces file? I've read the `interfaces' man page, and the stuff in /usr/share/doc/ifupdown. They're both very helpful, but a bit cryptic. Cheers and thanks, Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: persistent interface
> My problem has to do with the network interfaces. My > /etc/network/interfaces file looks like this: > ># The loopback interface ># automatically added when upgrading >auto lo >iface lo inet loopback > ># For the built-in NIC: >iface eth0 inet dhcp > ># For the wireless card ># >iface eth1 inet dhcp >mapping hotplug >script echo It looks as if you are under the impression that "mapping" is an option for "iface eth1 inet dhcp". Actually it should be a separate stanza. Here is your file reformatted to show the effective structure better: # Physical interfaces to bring up at boot time auto lo # Mappings # Bring up hot plugged interfaces with logical interface name # the same as their physical interface name mapping hotplug script echo # Logical interface lo # The logical interface as which the loopback interface is brought up iface lo inet loopback # Logical interface eth0 # The logical interface as which the built-in NIC eth0 is brought up iface eth0 inet dhcp # Logical interface eth1 # The logical interface as which the Wi-Fi card is brought up iface eth1 inet dhcp > I think that this should bring up only the loopback interface at > boot-time. Strictly speaking, this means that only the loopback interface "lo" is brought up by /etc/rcS.d/S40networking. Other interfaces can be brought up while the system is booting via the hotplug mechanism. Your stanza mapping hotplug script echo enables this mechanism. > Eth1 (pcmcia wireless card) should be brought up when the > hotplug system detects an insertion, and eth0 (associated with the > built-in NIC) should be brought up only when ifup is executed. > And indeed when I do: > >/etc/init.d/networking stop >/etc/init.d/networking start > > after the boot process, this is exactly what happens. Right. > The problem, though, is that at boot-time, the system always tries to > bring up eth0 (which corresponds to the built-in NIC). The kernel detects the interface and calls hotplug to notify user space that the interface is available. [...] > suggests that the attempt to bring up eth0 is triggered by loading of > the driver module (8139too), and indeed lsmod reports that this module > is loaded by the end of the boot process. Correct. > What I *cannot* for the life of me figure out is why this is > happening. I've been all through the directory /etc/modprobe.d/ and > there's no reference there to either 8139too or eth0. I've run > update-modules to make sure that there was no ancient module > configuration haunting the system. There is no reference to either > 8139too or to eth0 in /lib/modules/modprobe.conf. > > Can anyone tell me where else I could look to pin this down and figure > out why it is happening? I don't know who is loading the module, sorry. However, you can prevent eth0 from being ifup'ped via the hotplug mechanism by changing the mapping stanza to this: mapping hotplug script grep map eth1 Then only eth1 will be brought up on hotplug. -- Thomas Hood A man does not show his greatness by being at one extremity, but rather by touching both at once.-- Pascal
Re: persistent interface
> My problem has to do with the network interfaces. My > /etc/network/interfaces file looks like this: > ># The loopback interface ># automatically added when upgrading >auto lo >iface lo inet loopback > ># For the built-in NIC: >iface eth0 inet dhcp > ># For the wireless card ># >iface eth1 inet dhcp >mapping hotplug >script echo It looks as if you are under the impression that "mapping" is an option for "iface eth1 inet dhcp". Actually it should be a separate stanza. Here is your file reformatted to show the effective structure better: # Physical interfaces to bring up at boot time auto lo # Mappings # Bring up hot plugged interfaces with logical interface name # the same as their physical interface name mapping hotplug script echo # Logical interface lo # The logical interface as which the loopback interface is brought up iface lo inet loopback # Logical interface eth0 # The logical interface as which the built-in NIC eth0 is brought up iface eth0 inet dhcp # Logical interface eth1 # The logical interface as which the Wi-Fi card is brought up iface eth1 inet dhcp > I think that this should bring up only the loopback interface at > boot-time. Strictly speaking, this means that only the loopback interface "lo" is brought up by /etc/rcS.d/S40networking. Other interfaces can be brought up while the system is booting via the hotplug mechanism. Your stanza mapping hotplug script echo enables this mechanism. > Eth1 (pcmcia wireless card) should be brought up when the > hotplug system detects an insertion, and eth0 (associated with the > built-in NIC) should be brought up only when ifup is executed. > And indeed when I do: > >/etc/init.d/networking stop >/etc/init.d/networking start > > after the boot process, this is exactly what happens. Right. > The problem, though, is that at boot-time, the system always tries to > bring up eth0 (which corresponds to the built-in NIC). The kernel detects the interface and calls hotplug to notify user space that the interface is available. [...] > suggests that the attempt to bring up eth0 is triggered by loading of > the driver module (8139too), and indeed lsmod reports that this module > is loaded by the end of the boot process. Correct. > What I *cannot* for the life of me figure out is why this is > happening. I've been all through the directory /etc/modprobe.d/ and > there's no reference there to either 8139too or eth0. I've run > update-modules to make sure that there was no ancient module > configuration haunting the system. There is no reference to either > 8139too or to eth0 in /lib/modules/modprobe.conf. > > Can anyone tell me where else I could look to pin this down and figure > out why it is happening? I don't know who is loading the module, sorry. However, you can prevent eth0 from being ifup'ped via the hotplug mechanism by changing the mapping stanza to this: mapping hotplug script grep map eth1 Then only eth1 will be brought up on hotplug. -- Thomas Hood A man does not show his greatness by being at one extremity, but rather by touching both at once.-- Pascal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: persistent interface
* Frans Pop ([EMAIL PROTECTED]) wrote: |> On Friday 11 June 2004 20:08, Jim McCloskey wrote: |> > I've since tried putting: |> > |> >install eth0 /bin/true |> > |> > in /etc/modprobe.conf, but that didn't solve the problem either, |> |> You should never directly edit /etc/modprobe.conf (2.5 & 2.6 kernels) or |> /etc/modules.conf (2.4 kernels) on a Debian system. Both are managed by |> update-modules and generated from the contents of the /etc/modprobe.d/ and |> /etc/modutils/ directories respectively. Sorry, I was speaking loosely. I in fact added the line to /etc/modprobe.d/aliases and then ran update-modules. I should have been more accurate. Thank you for your help, Jim
Re: persistent interface
* Frans Pop ([EMAIL PROTECTED]) wrote: |> On Friday 11 June 2004 20:08, Jim McCloskey wrote: |> > I've since tried putting: |> > |> >install eth0 /bin/true |> > |> > in /etc/modprobe.conf, but that didn't solve the problem either, |> |> You should never directly edit /etc/modprobe.conf (2.5 & 2.6 kernels) or |> /etc/modules.conf (2.4 kernels) on a Debian system. Both are managed by |> update-modules and generated from the contents of the /etc/modprobe.d/ and |> /etc/modutils/ directories respectively. Sorry, I was speaking loosely. I in fact added the line to /etc/modprobe.d/aliases and then ran update-modules. I should have been more accurate. Thank you for your help, Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: persistent interface
Oh duh. I completely misread Ross' post. nm me :) Jim McCloskey wrote: Arjen Verweij <[EMAIL PROTECTED]> wrote: |> Yeah, so install it? Or can't you install programs on that systems? |> |> apt-get install discover |> |> as root. Oh I could install it OK, but Ross' suggestion was that the presence of discover on the system might be *the source* of the problem I described (an un-wanted attempt at boot-time to always bring up the eth0 network interface) ... so I hardly want to. I've since tried putting: install eth0 /bin/true in /etc/modprobe.conf, but that didn't solve the problem either, Jim
Re: persistent interface
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 11 June 2004 20:08, Jim McCloskey wrote: > I've since tried putting: > >install eth0 /bin/true > > in /etc/modprobe.conf, but that didn't solve the problem either, You should never directly edit /etc/modprobe.conf (2.5 & 2.6 kernels) or /etc/modules.conf (2.4 kernels) on a Debian system. Both are managed by update-modules and generated from the contents of the /etc/modprobe.d/ and /etc/modutils/ directories respectively. See the manpages for more information. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAygm7gm/Kwh6ICoQRAmyaAJ9OgBP7FOp8+V1eKj3Y5eU4xtPXTgCfRWjj RMD7vfLE8hHoPo51lmVQbdg= =qzez -END PGP SIGNATURE-
Re: Re: persistent interface
Arjen Verweij <[EMAIL PROTECTED]> wrote: |> Yeah, so install it? Or can't you install programs on that systems? |> |> apt-get install discover |> |> as root. Oh I could install it OK, but Ross' suggestion was that the presence of discover on the system might be *the source* of the problem I described (an un-wanted attempt at boot-time to always bring up the eth0 network interface) ... so I hardly want to. I've since tried putting: install eth0 /bin/true in /etc/modprobe.conf, but that didn't solve the problem either, Jim
Re: persistent interface
Oh duh. I completely misread Ross' post. nm me :) Jim McCloskey wrote: Arjen Verweij <[EMAIL PROTECTED]> wrote: |> Yeah, so install it? Or can't you install programs on that systems? |> |> apt-get install discover |> |> as root. Oh I could install it OK, but Ross' suggestion was that the presence of discover on the system might be *the source* of the problem I described (an un-wanted attempt at boot-time to always bring up the eth0 network interface) ... so I hardly want to. I've since tried putting: install eth0 /bin/true in /etc/modprobe.conf, but that didn't solve the problem either, Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: persistent interface
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 11 June 2004 20:08, Jim McCloskey wrote: > I've since tried putting: > >install eth0 /bin/true > > in /etc/modprobe.conf, but that didn't solve the problem either, You should never directly edit /etc/modprobe.conf (2.5 & 2.6 kernels) or /etc/modules.conf (2.4 kernels) on a Debian system. Both are managed by update-modules and generated from the contents of the /etc/modprobe.d/ and /etc/modutils/ directories respectively. See the manpages for more information. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAygm7gm/Kwh6ICoQRAmyaAJ9OgBP7FOp8+V1eKj3Y5eU4xtPXTgCfRWjj RMD7vfLE8hHoPo51lmVQbdg= =qzez -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: persistent interface
Yeah, so install it? Or can't you install programs on that systems? apt-get install discover as root. Jim McCloskey wrote: * Ross Burton ([EMAIL PROTECTED]) wrote: |> Do you have discover installed? I found that discover likes |> bringing up any interfaces it finds on boot. Thanks a lot for the suggestion. `Discover' is not on the system, however. Back to the drawing-board Jim
Re: Re: persistent interface
Arjen Verweij <[EMAIL PROTECTED]> wrote: |> Yeah, so install it? Or can't you install programs on that systems? |> |> apt-get install discover |> |> as root. Oh I could install it OK, but Ross' suggestion was that the presence of discover on the system might be *the source* of the problem I described (an un-wanted attempt at boot-time to always bring up the eth0 network interface) ... so I hardly want to. I've since tried putting: install eth0 /bin/true in /etc/modprobe.conf, but that didn't solve the problem either, Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: persistent interface
* Ross Burton ([EMAIL PROTECTED]) wrote: |> Do you have discover installed? I found that discover likes |> bringing up any interfaces it finds on boot. Thanks a lot for the suggestion. `Discover' is not on the system, however. Back to the drawing-board Jim
Re: persistent interface
Yeah, so install it? Or can't you install programs on that systems? apt-get install discover as root. Jim McCloskey wrote: * Ross Burton ([EMAIL PROTECTED]) wrote: |> Do you have discover installed? I found that discover likes |> bringing up any interfaces it finds on boot. Thanks a lot for the suggestion. `Discover' is not on the system, however. Back to the drawing-board Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: persistent interface
* Ross Burton ([EMAIL PROTECTED]) wrote: |> Do you have discover installed? I found that discover likes |> bringing up any interfaces it finds on boot. Thanks a lot for the suggestion. `Discover' is not on the system, however. Back to the drawing-board Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: persistent interface
On Fri, 2004-06-11 at 03:23, Jim McCloskey wrote: > The problem, though, is that at boot-time, the system always tries to > bring up eth0 (which corresponds to the built-in NIC). But of course > it can't typically, because the ethernet port is not usually connected > to anything. So the boot process hangs for several minutes and then > the interface is brought up in a confused state---ifconfig thinks that > the interface is up, but no IP address is associated with it. Using > ifdown eth0 produces the error message that eth0 is not configured. It > can be brought down, though, with: ifconfig eth0 down. Do you have discover installed? I found that discover likes bringing up any interfaces it finds on boot. Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF signature.asc Description: This is a digitally signed message part
Re: persistent interface
On Fri, 2004-06-11 at 03:23, Jim McCloskey wrote: > The problem, though, is that at boot-time, the system always tries to > bring up eth0 (which corresponds to the built-in NIC). But of course > it can't typically, because the ethernet port is not usually connected > to anything. So the boot process hangs for several minutes and then > the interface is brought up in a confused state---ifconfig thinks that > the interface is up, but no IP address is associated with it. Using > ifdown eth0 produces the error message that eth0 is not configured. It > can be brought down, though, with: ifconfig eth0 down. Do you have discover installed? I found that discover likes bringing up any interfaces it finds on boot. Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF signature.asc Description: This is a digitally signed message part
