networking hosed after upgrading to 10.04

[scar]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Tom H @ 05/31/2011 01:23 PM:
> On Tue, May 31, 2011 at 2:30 PM, scar <scar at drigon.com> wrote:
>> now ifconfig is not listing an IP address for eth0 but it still has one
>> for br0 which seems strange to me.
> 
> That's good and normal.

really?  it gives me the impression that my bridge connection is somehow
'preferred' over eth0.  but i don't think i quite understand the network
topology and how all these pieces fit together....  i guess as long as
everything is working there's nothing to worry about!


>> also, upon rebooting the system, networking doesn't seem to work until i
>> restart it with the init.d script.  i noticed that, before i restarted
>> networking, both eth0 and br0 had an IP address of 192.168.1.139.
> 
> That's not good and not normal.

no, not it's not... :-)


>> my VM grabs an IP address but i noticed it is something like
>> 192.168.122.X which seems to correspond to the vibr0 interface
> 
> Re vibr0:
> 
> Do you have
> <interface type='bridge'>
> ...
> <source bridge='br0'>
> ...
> </interface>
> in "/etc/libvirt/qemu/<your_vm>.xml"?

no it had been set to virbr0 somehow.  changing it back to br0 solved that.

so all that's left is figuring out why i need to restart the networking
init.d script upon boot in order to get a functioning connection...

there seems to be a 'Network is unreachable' error involved when i
manually run the init script for the first time after a boot:

$ sudo /etc/init.d/networking restart
 * Reconfiguring network interfaces...
        There is already a pid file /var/run/dhclient.br0.pid with pid 1332
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/br0/00:24:8c:66:d9:b5
Sending on   LPF/br0/00:24:8c:66:d9:b5
Sending on   Socket/fallback
DHCPRELEASE on br0 to 192.168.1.1 port 67
RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 1325
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:24:8c:66:d9:b5
Sending on   LPF/eth0/00:24:8c:66:d9:b5
Sending on   Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:24:8c:66:d9:b5
Sending on   LPF/eth0/00:24:8c:66:d9:b5
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.1.139 from 192.168.1.1
DHCPREQUEST of 192.168.1.139 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.139 from 192.168.1.1
bound to 192.168.1.139 -- renewal in 2147483648 seconds.
ssh stop/waiting
ssh start/running, process 3160
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/br0/00:24:8c:66:d9:b5
Sending on   LPF/br0/00:24:8c:66:d9:b5
Sending on   Socket/fallback
DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 6
DHCPOFFER of 192.168.1.139 from 192.168.1.1
DHCPREQUEST of 192.168.1.139 on br0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.139 from 192.168.1.1
bound to 192.168.1.139 -- renewal in 2147483648 seconds.
ssh stop/waiting
ssh start/running, process 3277
$

-----BEGIN PGP SIGNATURE-----

iEYEAREIAAYFAk3lh/gACgkQXhfCJNu98qB2kwCgj+Tc0uwAJ9v5yrns7vlxw6uJ
62wAn3SgsQ046kIO2KC+tB16unKinQvs
=pZo3
-----END PGP SIGNATURE-----