Re: network card bridging failing on wheezy
Am 09.11.2014 21:13, schrieb Gary Dale:
> You're right. Here's my default.xml (I only changed the addresses):
>
> root@TheLibrarian:/home/garydale# cat /etc/libvirt/qemu/networks/default.xml
> <network>
> <name>default</name>
> <bridge name="br0" />
> <forward/>
> <ip address="192.168.1.14" netmask="255.255.255.0">
> <dhcp>
> <range start="192.168.1.32" end="192.168.1.38" />
> </dhcp>
> </ip>
> </network>
>
> However when I removed the link to default.xml, I ended up with no
> network starting. Nor could I bring up br0. lo and eth0 could still be
> brought up manually and a gateway added.
Then it appears to be the case that Debian's networking scripts are not
started at boot. (Then it's also no wonder why you can't bring up br0,
because it doesn't exist yet, you'd have to create it with 'brctl addbr
br0' first, if you really wanted to use 'br0'.)
Could you post the contents of your /etc/default/networking?
Specifically, it should have either no explicit settings (everything
commented out) or the following settings (which are default):
CONFIGURE_INTERFACES=yes
EXCLUDE_INTERFACES= # (empty)
You're under Wheezy, so I'm assuming sysvinit + LSB, could you also
check whether the networking script is started at boot?
ls -l /etc/rc*.d/S??networking
(should turn up a single link in /etc/rcS.d)
If both is the way it should be, could you perhaps set VERBOSE=yes in
/etc/default/networking and look for any relevant boot messages? Not
dmesg/syslog, but on the console.[1]
Also, might be relevant: did you install any software that might take
over network configuration? Such as NetworkManager or wicd or the such?
> But what is the underlying problem? It looks like the networking isn't
> being brought up during boot, but I'm seeing dmesg output like:
>
> [ 199.542096] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> [ 199.542153] r8169 0000:02:00.0: setting latency timer to 64
> [ 199.542198] r8169 0000:02:00.0: irq 41 for MSI/MSI-X
> [ 199.542594] r8169 0000:02:00.0: eth0: RTL8168c/8111c at
> 0xffffc90000c0e000, 00:24:1d:14:d8:42, XID 1c4000c0 IRQ 41
> [ 199.542596] r8169 0000:02:00.0: eth0: jumbo features [frames: 6128
> bytes, tx checksumming: ko]
That just seems to load the corresponding driver, probably once udev is
loaded at boot,[*] but doesn't appear to actually bring it up (no 'link
is up' or similar message).
[*] Although 200s seems a bit late for that, udev should load
immediately after the root filesystem is mounted, could you check when
that happened? If it's just a couple of seconds before the 199.54s,
that's fine (then the kernel just takes a long time to initialize, maybe
because of RAID/SCSI/SAS/... controller?) but if there's quite a gap
between the mounting of the root filesystem and the loading of the
network driver (with no additional drivers that take a long time probing
in between), that would also be strange, and a potential source of problem.
> and
> [ 226.160653] tun: Universal TUN/TAP device driver, 1.6
> [ 226.160660] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
That indicates that the tun driver is loaded, probably once libvirt is
started. That has no bearing on your host's network configuration.
- Christian
[1] If boot goes to fast for you, you could add the following script to
/etc/network/if-up.d/zz-wait (make it executable):
#!/bin/sh
[ x"$IFACE" = x"lo" ] && return
echo
echo $IFACE should be configured now...
echo (sleeping for a while)
echo
sleep 20
(Replace the 20 with however many seconds you might need to see the
messages.)
Reply to: