Home » forums » Imported debian.org Mailing Lists » Debian User

/etc/network/interfaces file ?

Tags:

For several installs over a period of time for Etch, using a net-install
cd. The ~/network/interfaces file uses the line "allow-hotplug eth0".
This has not worked on my boxes, I have to type 'dhclient eth0' to
connect. I use an Ipcop firewall, dhcp, hooked up to a switch. I comment
out the 'hotplug' line and use 'eth0 auto' the old way, and all is
well. Anyone else see this and what package is this associated with ?

TIA

--
Greg Madden

--

Bookmark/Search this post with:
  • Delicious
  • Digg
  • StumbleUpon
  • Propeller
  • Reddit
  • Magnoliacom
  • Newsvine
  • Furl
  • Google
  • Yahoo
  • Technorati
0
‹ Sending E-Mails via cellphone and iMode unscientific debian users world survey ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

/etc/network/interfaces file ?

Submitted by stevendemetrius on Sun, 2006-12-17 03:09.

I've noticed the same thing and I've done a similar change in the /etc/network/interfaces file.

change:
"allow-hotplug eth0"
to:
"auto eth0"

I'm not sure what is causing the problem and don't know which package to file a bug against.

I'm assuming that "allow-hotplug eth0" does a cable check on eth0's NIC and if found brings up eth0. Whether it is doing the dhclient I don't know.

Anyone, any ideas?

»

/etc/network/interfaces file ?

Submitted by user local on Sun, 2006-12-17 04:00.

2006/12/17, stevendemetrius <steven.demetrius@fiwwi.com>:
Anyone, any ideas?
PCMCIA optimisation?

»

/etc/network/interfaces file ?

Submitted by Andrei Popescu on Sun, 2006-12-17 04:00.

On Sat, Dec 16, 2006 at 05:17:39PM -0900, Greg Madden wrote:
> For several installs over a period of time for Etch, using a net-install
> cd. The ~/network/interfaces file uses the line "allow-hotplug eth0".
> This has not worked on my boxes, I have to type 'dhclient eth0' to
> connect. I use an Ipcop firewall, dhcp, hooked up to a switch. I comment
> out the 'hotplug' line and use 'eth0 auto' the old way, and all is
> well. Anyone else see this and what package is this associated with ?

AFAICT, these options are complementary. See 'man interfaces'.

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

--

»

/etc/network/interfaces file ?

Submitted by Greg Madden on Sun, 2006-12-17 16:00.

On Sun, 17 Dec 2006 10:56:23 +0200
(Andrei Popescu) wrote:

> On Sat, Dec 16, 2006 at 05:17:39PM -0900, Greg Madden wrote:
> > For several installs over a period of time for Etch, using a
> > net-install cd. The ~/network/interfaces file uses the line
> > "allow-hotplug eth0". This has not worked on my boxes, I have to
> > type 'dhclient eth0' to connect. I use an Ipcop firewall, dhcp,
> > hooked up to a switch. I comment out the 'hotplug' line and use
> > 'eth0 auto' the old way, and all is well. Anyone else see this and
> > what package is this associated with ?
>
> AFAICT, these options are complementary. See 'man interfaces'.
>
> Regards,
> Andrei

Can I infer from the failure of running '/etc/init.d/networking' script
that the --allow-hotplug eth0' is not being used to bring up the
interface?

What context is hotplug being used? I don't have hotplug installed, it
has been deprecated in Etch.
--
Greg Madden

--

»

/etc/network/interfaces file ?

Submitted by Andrei Popescu on Tue, 2006-12-19 15:00.

On Sun, Dec 17, 2006 at 11:51:40AM -0900, Greg Madden wrote:
> On Sun, 17 Dec 2006 10:56:23 +0200
> (Andrei Popescu) wrote:
>
> > On Sat, Dec 16, 2006 at 05:17:39PM -0900, Greg Madden wrote:
> > > For several installs over a period of time for Etch, using a
> > > net-install cd. The ~/network/interfaces file uses the line
> > > "allow-hotplug eth0". This has not worked on my boxes, I have to
> > > type 'dhclient eth0' to connect. I use an Ipcop firewall, dhcp,
> > > hooked up to a switch. I comment out the 'hotplug' line and use
> > > 'eth0 auto' the old way, and all is well. Anyone else see this and
> > > what package is this associated with ?
> >
> > AFAICT, these options are complementary. See 'man interfaces'.
> >
> > Regards,
> > Andrei
>
> Can I infer from the failure of running '/etc/init.d/networking' script
> that the --allow-hotplug eth0' is not being used to bring up the
> interface?
>
> What context is hotplug being used? I don't have hotplug installed, it
> has been deprecated in Etch.

If think it refers to the actual hot-plugging, not the hotplug package.

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

--

»

/etc/network/interfaces file ?

Submitted by Greg Madden on Mon, 2006-12-18 01:00.

On Sat, 16 Dec 2006 17:17:39 -0900
Greg Madden wrote:

> For several installs over a period of time for Etch, using a
> net-install cd. The ~/network/interfaces file uses the line
> "allow-hotplug eth0". This has not worked on my boxes, I have to type
> 'dhclient eth0' to connect. I use an Ipcop firewall, dhcp, hooked up
> to a switch. I comment out the 'hotplug' line and use 'eth0 auto' the
> old way, and all is well. Anyone else see this and what package is
> this associated with ?
>
> TIA
>
>

What has solved this for me, while leaving the default '--allow-hotplug'
statement is to put after this line, a line "auto eth0' which was
missing on my box.

--
Greg Madden

--

»

/etc/network/interfaces file ?

Submitted by stevendemetrius on Mon, 2006-12-18 03:49.

It seems the point is being missed here.

The issue is that "allow-hotplug eth0" does *not* work while "auto eth0" does work! If "allow-hotplug" is used then "dhclient" has to be run manually in order for eth0 to get its IP related settings.

This seems to be a bug. Greg since you started this thread then you can file a bug against "interfaces". Install and run "reportbug". Just follow the instructions.

»

/etc/network/interfaces file ?

Submitted by Nate Bargmann on Mon, 2006-12-18 08:00.

* stevendemetrius [2006 Dec 18 03:14 -0600]:
>
> It seems the point is being missed here.
>
> The issue is that "allow-hotplug eth0" does *not* work while "auto eth0"
> does work! If "allow-hotplug" is used then "dhclient" has to be run
> manually in order for eth0 to get its IP related settings.
>
> This seems to be a bug. Greg since you started this thread then you can
> file a bug against "interfaces". Install and run "reportbug". Just follow
> the instructions.

The bug would probably best be filed against ifupdown:

http://packages.debian.org/testing/admin/ifupdown

The interfaces(5) man page shows that it is a part of the ifupdown
package.

- Nate >>

--
Wireless | Amateur Radio Station N0NB | Successfully Microsoft
Amateur radio exams; ham radio; Linux info @ | free since January 1998.
http://www.qsl.net/n0nb/ | "Debian, the choice of
My Kawasaki KZ-650 SR @ | a GNU generation!"
http://www.networksplus.net/n0nb/ | http://www.debian.org

--

»

/etc/network/interfaces file ?

Submitted by Joey Hess on Thu, 2006-12-21 12:00.

stevendemetrius wrote:
> The issue is that "allow-hotplug eth0" does *not* work while "auto eth0"
> does work! If "allow-hotplug" is used then "dhclient" has to be run
> manually in order for eth0 to get its IP related settings.

I've investigated this for a few hours today, and if you have any
systems that fail to bring up the interface with "allow-hotplug eth0",
and no "auto eth0", I'm curious about what situations cause it to fail.

So far the only situations I've been able to find where allow-hotplug
fails are:
* Long (> 2 minutes) fscks of the root filesystem during boot.
* Hard powercycles / hard reboots.

I've filed bugs for both of those, and it seems that it should work in
other situations, but perhaps I've missed other failure modes.

--
see shy jo

»
Syndicate content