Re: network not connected by default: bug or feature?
On Sun, Dec 11, 2005 at 11:31:12PM +0100, Geert Stappers wrote:
> On Sat, Dec 10, 2005 at 11:29:30AM -0800, Ross Boylan wrote:
> > I've noticed the ethernet connection is not on by default when I boot
> > my newly installed system. Somewhat oddly, it is at eth1. There are
> > a bunch of settings for it in /etc/network/interfaces, incuding a
> > comment just before a mapping directive for eth1 that "This is a list
> > of hotpluggable network interfaces. They will activated automatically
> > by the hotplug system."
> >
> > It's not getting activated automatically. The use of hotplug seems
> > peculiar for card that's inside the case, but I don't fully understand
> > what the hotplug system covers.
> >
> > I also think I recall messages during the initial setup about how
> > there is no general solution for when to bring up network devices.
> >
> > So, is this the way things are supposed to work?
>
> I think you are trying a development version.
Daily build of the installer, though later stages pulled packages from
testing.
It seems to me that for the final release it would be good to have
networking on after a "regular" install, though I can imagine a
security argument to the contrary.
>
> > Is changing to auto mapping eth1.... sufficient to bring the interface
> > up on system start?
>
> Only as temporary workaround.
After studying the man page, I tried
auto eth1
(i.e., separate from the mapping command).
That seems to have worked across reboots.
>
>
> >
> > Thanks.
>
>
> GSt
>
> P.S.
> Firewire hardware maybe detected as eth0
>
There really is an eth0 on the motherboard; it's just that nothing is
connected to it, and possibly it needs special drivers.
Ross
Reply to: