Re: Networking trouble after recent upgrade in Sid
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 invoking dhcp for an interface on boot? Yes. The old default was 'auto' (aka allow-auto). The new default is 'allow-hotplug'. But both can be specified and having both are useful. You you Osamu Aoki for this fine documentation here: http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#list-of-stanzas-in-eni The 'auto' configures /etc/init.d/networking to use it when the networking subsystem is started or restarted. The 'allow-hotplug' starts the interface when the device becomes available to the kernel. You may want to review the mailing list archive thread starting here: http://lists.debian.org/debian-user/2011/01/msg00974.html Bob signature.asc Description: Digital signature
Fwd: Networking trouble after recent upgrade in Sid
-- Forwarded message -- From: David Bruce Date: Sat, Feb 12, 2011 at 4:18 PM Subject: Re: Networking trouble after recent upgrade in Sid To: shawn wilson Hi, On Sat, Feb 12, 2011 at 8:13 PM, shawn wilson wrote: > >> Here's my old interfaces file where I statically brought up eth0: >> # The primary network interface >> allow-hotplug eth0 >> #iface eth0 inet dhcp >> iface eth0 inet static >> address 192.168.0.100 >> netmask 255.255.255.0 >> broadcast 192.168.0.255 >> gateway 192.168.0.1 >> dns-domain gnu-orleans.org >> > > 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 invoking dhcp for an interface on boot? try it or read: http://wiki.debian.org/NetworkConfiguration or, i'll refer you to a thread i started: http://lists.debian.org/debian-user/2011/01/msg00905.html
Re: Networking trouble after recent upgrade in Sid
> 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 primary network interface > allow-hotplug eth0 > #iface eth0 inet dhcp > iface eth0 inet static > address 192.168.0.100 > netmask 255.255.255.0 > broadcast 192.168.0.255 > gateway 192.168.0.1 > dns-domain gnu-orleans.org > Add 'auto eth0'
Re: Networking trouble after recent upgrade in Sid
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 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 primary network interface allow-hotplug eth0 #iface eth0 inet dhcp iface eth0 inet static address 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.1 dns-domain gnu-orleans.org After the upgrade, eth0 no longer wound up with 192.168.0.100. Also, even after I went back to the default DHCP-using settings, I still don't get a working address after reboot until I run dhclient by hand. The netgear router is back to its default DHCP behavior, and the iMac attached to the same router gets its address just fine. Should my interfaces entry for eth0 start with "auto eth0" rather than "allow-hotplug eth0"? From googling, I've found statements that the way to get dhclient to run on every boot is with the "auto" keyword. Thanks, David -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=7zs-l164saxpy9jgdmysd9eynh1m8mdxro...@mail.gmail.com
Re: Networking trouble after recent upgrade in Sid
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 ? Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Networking trouble after recent upgrade in Sid
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 want an interface started on boot, you should use: > auto eth0 > instead of: > allow-hotplug eth0 Both allow-hotplug and allow-auto should bring up eth0 at boot unless it's managed by network manager as you say below (I'm not familiar with wicd or ifplugd). > Do you ifplugd, network-manager, or wicd? Those are the main things I can > think of that would start an allow-hotplug interface. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikgyy0xz6nhxedzaocmxbhhgp3apemxju2fj...@mail.gmail.com
Re: Networking trouble after recent upgrade in Sid
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-hotplug eth0 Do you ifplugd, network-manager, or wicd? Those are the main things I can think of that would start an allow-hotplug interface, and I'm not sure about that. I use auto on my desktop and do not list devices on my laptop so they are exclusively controlled by network-manager. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Networking trouble after recent upgrade in Sid
Hi, I'm running Sid on my amd64 home desktop, and I had been using it as DHCP server and DNS server for my home network. I had my eth0 statically set to 192.168.0.100 in /etc/network/interfaces. I have a basic consumer Netgear router, and had a couple of other machines as clients. 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: dbruce@emperor:~/Documents$ sudo ifconfig -a [sudo] password for dbruce: eth0 Link encap:Ethernet HWaddr aa:00:04:00:0a:04 inet6 addr: fe80::250:8dff:fe98:3d20/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:58 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3384 (3.3 KiB) TX bytes:14730 (14.3 KiB) Interrupt:23 Base address:0x8000 To simplify things (and to ease the wrath of my wife, who couldn't use her computer because the network relied on my machine as DHCP server), I put the Netgear router back to its default role as DHCP server and just use the ISP DNS servers. So my desktop's eth0 is now supposed to use DHCP with the plain vanilla settings: >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. If I run "sudo dhclient eth0" I get a IPv4 address assigned to the interface, and everything seems to work. Of course, I'd like to understand what's going on, and at some point would like to do my own DNS again (mainly so I can use a human-friendly name for my Ampache music server). So what's changed recently with networking? Am I being dragged into the IPv6 world? Thanks for any help, David Bruce -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTikOUziWdo6LUhfejJJ+g-ZnkHPmza8=esjv7...@mail.gmail.com
