no auto for network interface?

[Zach]

actually, ifplugd is not installed.  The reason the interface isn't
configured if the cable isn't plugged in is because it's setup to use
dhcp:
iface eth0 inet dhcp
So no cable, no dhcp, no configuration.

As far as wireless not working with auto, why not? it's got everything
it needs.  And in fact I can testify to the fact that it doesn't work.

What is confusing however is why eth0 works even without auto?

can anyone demystify the hotplug lines?

What does this mean:
mapping hotplug
script grep

On 11/16/05, Derek Broughton <news at pointerstop.ca> wrote:
> Sandip Bhattacharya wrote:
>
> > Zach wrote:
> >>
> >> ------------------BEGIN /etc/network/interfaces-------------
> >> auto lo
> >> iface lo inet loopback
> >>
> >> mapping hotplug
> >> script grep
> >> map eth1
> >> iface eth1 inet dhcp
> >> wireless-essid XXXXX
> >> wireless-key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >> wireless-txpower 25mw
> >> iface eth0 inet dhcp
> >> auto eth1
> >
> > This is weird. You have the "auto" directive used twice. I remember
> > seeing an error somewhere which said that I shouldn't use auto twice.
> > So now I use "auto lo eth0" myself.
>
> I don't _think_ it's wrong, but I can't see "auto" working on a wireless
> interface.
>
> Is ifplugd installed?  OP suggests that unplugging the cable prevents the
> interface from being configured, which implies ifplugd is monitoring it.
> dpkg-reconfigure ifplugd, and change the monitored interfaces from "all" or
> "eth0 eth1" to "eth1".
> --
> derek
>
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


--
If you reply to a message I posted to a mailing list,
and you want me to see your reply, be sure to put my
address in the 'To:', or I might not see the message.