David Bruce wrote:
> shawn wilson wrote:
> >> allow-hotplug eth0
> >> iface eth0 inet static
> >> ...
> >
> > Add 'auto eth0'
>
> Sorry to be dense about this, but is "auto eth0" applicable to
> automatically do a static ip assignment to an interface on boot, as
> well as being applicable to invo
> Here's my old interfaces file where I statically brought up eth0:
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The prim
Hi Shawn,
> what did your old interfaces file look like? might look at resolv.conf as
> well. i'm not sure what trouble shooting you went through, so it might be
> useful to post your iptables config.
Here's my old interfaces file where I statically brought up eth0:
# This file describes the net
On Sb, 12 feb 11, 03:23:16, David Bruce wrote:
>
> With a aptitude safe-upgrade and reboot today, my setup broke. I'm no
> network expert, but it appears that eth0 is no longer getting an IPv4
> address on boot:
Purge network-manager?
Could you post the relevant part of /var/log/aptitude ?
Reg
On Sat, Feb 12, 2011 at 4:55 AM, Boyd Stephen Smith Jr.
wrote:
> In , David Bruce
> wrote:
>>>From /etc/network/interfaces: ---
>>
>># The primary network interface
>>allow-hotplug eth0
>>iface eth0 inet dhcp
>>
>>So now, on bootup my web browser won't connect.
>
> Normally, if you w
In , David Bruce
wrote:
>>From /etc/network/interfaces: ---
>
># The primary network interface
>allow-hotplug eth0
>iface eth0 inet dhcp
>
>So now, on bootup my web browser won't connect.
Normally, if you want an interface started on boot, you should use:
auto eth0
instead of:
allow-h
6 matches
Mail list logo
