I'm having a bit of a problem with setting up my network.
I'm trying to learn stuff by setting up some xen VMs bridged to VLANs, going through bonded interfaces into a switch that eventually distributes them to different ports on a router. So far I've learned that this simply won't work as advertised.
Strange things start to happen after I've played with the network for a while, specifically VLANs stop to work, ie. no tagged traffic can go out of the server (tcpdump shows ip lookups going through, like who-is 192.168.16.8, reply is-at shows up, but doesn't go anywhere) and also LACP auto configuration didn't work (made me worry something was wrong with my switch ). Yet I can ping bond0 interface if I give it a IP addr, I can't do anything with bond0.## vlan interfaces.
I don't know what triggers this. I may do some testing but right now I wonder if there are some leads as to what might be responsible for fixing it. All I need to do is restart the box, then the interfaces file goes through without any problems and even the LACP trunk got negotiated properly.
Code: Select all
root@bobeus:~# uname -a
Linux bobeus 3.2.0-2-amd64 #1 SMP Sun Mar 4 22:48:17 UTC 2012 x86_64 GNU/Linux
ifconfig: http://codepad.org/wyBDUrZy
interfaces file, /proc/net/vlan, /proc/net/bonding dumps: http://codepad.org/YaSdpJVn
lspci: http://codepad.org/00qlmBaS
LACP ststus on the switch: http://codepad.org/cc1wDmET
The switch is a Dell PowerConnect 5324
Router is pfSense 2.0.1 running on a watchguard firebox x700
None of this worked before I restarted the box. vlan## bridges didn't get their IP addresses from the router, LACP ports didn't get their partners set.
Before that I thought the works-after-restart thing was only vlan-specific, since I could get the interfaces to work (bridged or not) otherwise. reloading the 8021q and bonding modules didn't help.