[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: network not connected by default: bug or feature?



On Sun, Dec 11, 2005 at 10:59:25PM -0800, Ross Boylan wrote:
> 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:
  <snip/>
> > > 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.

It is indeed /etc/network/interfaces where that happens.

> > > 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.

I think you have also encountered bug #342498

> Ross

GSt

Attachment: signature.asc
Description: Digital signature


Reply to: