dell2650-01:~/media# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:11:43:32:68:ab
inet6 addr: fe80::211:43ff:fe32:68ab/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:360247 errors:0 dropped:0 overruns:0 frame:0
TX packets:194789 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:139293160 (132.8 MiB) TX bytes:28126921 (26.8 MiB)
bond0.2 Link encap:Ethernet HWaddr 00:11:43:32:68:ab
inet6 addr: fe80::211:43ff:fe32:68ab/64 Scope:Link
UP BROADCAST RUNNING PROMISC MASTER MULTICAST MTU:1500 Metric:1
RX packets:187223 errors:0 dropped:0 overruns:0 frame:0
TX packets:56357 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:115269968 (109.9 MiB) TX bytes:9955227 (9.4 MiB)
eth0 Link encap:Ethernet HWaddr 00:11:43:32:68:ab
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:155494 errors:0 dropped:0 overruns:0 frame:0
TX packets:114980 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:69486941 (66.2 MiB) TX bytes:16889868 (16.1 MiB)
Interrupt:28
eth1 Link encap:Ethernet HWaddr 00:11:43:32:68:ab
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:204753 errors:0 dropped:0 overruns:0 frame:0
TX packets:79809 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:69806219 (66.5 MiB) TX bytes:11237053 (10.7 MiB)
Interrupt:29
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
veth2070.2 Link encap:Ethernet HWaddr 00:0c:29:cf:51:9f
inet6 addr: fe80::20c:29ff:fecf:519f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36810 errors:0 dropped:0 overruns:0 frame:0
TX packets:151735 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3099693 (2.9 MiB) TX bytes:106816981 (101.8 MiB)
vlan2 Link encap:Ethernet HWaddr 00:0c:29:cf:51:9f
inet addr:10.107.208.131 Bcast:10.107.208.255 Mask:255.255.255.0
inet6 addr: 2001:470:e067:2:20c:29ff:fecf:519f/64 Scope:Global
inet6 addr: 2001:470:e067:2:211:43ff:fe32:68ab/64 Scope:Global
inet6 addr: fe80::211:43ff:fe32:68ab/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:127087 errors:0 dropped:0 overruns:0 frame:0
TX packets:18801 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:39821589 (37.9 MiB) TX bytes:5847464 (5.5 MiB)
dell2650-01:~/media# brctl show
bridge name bridge id STP enabled interfaces
vlan2 8000.000c29cf519f no bond0.2
veth2070.2
All is working for the most part with this arrangement except for a few issues:
1. There are some issues when I attempt to bring down the networking service where there are some network interfaces left hanging around that I expect should not be left hanging around. Below is the output of stopping the networking (/etc/init.d/networking stop) and the interfaces that are left hanging around:
Deconfiguring network interfaces...There is already a pid file /var/run/dhclient.vlan2.pid with pid 18891
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
Listening on LPF/vlan2/00:00:00:00:00:00
Sending on LPF/vlan2/00:00:00:00:00:00
Sending on Socket/fallback
DHCPRELEASE on vlan2 to 10.107.208.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
SIOCSIFFLAGS: Cannot assign requested address
done.
# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
bond0.2 Link encap:Ethernet HWaddr 00:11:43:32:68:ab
BROADCAST PROMISC MASTER MULTICAST MTU:1500 Metric:1
RX packets:187644 errors:0 dropped:0 overruns:0 frame:0
TX packets:56466 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:115389061 (110.0 MiB) TX bytes:9975413 (9.5 MiB)
eth0 Link encap:Ethernet HWaddr 00:11:43:32:68:ab
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:28
eth1 Link encap:Ethernet HWaddr 00:11:43:32:68:ac
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:29
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
veth2070.2 Link encap:Ethernet HWaddr 00:0c:29:cf:51:9f
inet6 addr: fe80::20c:29ff:fecf:519f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36810 errors:0 dropped:0 overruns:0 frame:0
TX packets:151883 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3099693 (2.9 MiB) TX bytes:106868121 (101.9 MiB)
2. The second issue is a flurry of messages when networking is started (/etc/init.d/networking start):
dell2650-01:~# cat networing_start.txt
Configuring network interfaces...if-up.d/mountnfs[eth0]: waiting for interface eth1 before doing NFS mounts (warning).
if-up.d/mountnfs[eth0]: waiting for interface bond0 before doing NFS mounts (warning).
if-up.d/mountnfs[eth0]: waiting for interface bond0.2 before doing NFS mounts (warning).
if-up.d/mountnfs[eth0]: waiting for interface vlan2 before doing NFS mounts (warning).
if-up.d/mountnfs[eth1]: waiting for interface bond0 before doing NFS mounts (warning).
if-up.d/mountnfs[eth1]: waiting for interface bond0.2 before doing NFS mounts (warning).
if-up.d/mountnfs[eth1]: waiting for interface vlan2 before doing NFS mounts (warning).
if-up.d/mountnfs[bond0]: waiting for interface bond0.2 before doing NFS mounts (warning).
if-up.d/mountnfs[bond0]: waiting for interface vlan2 before doing NFS mounts (warning).
ERROR: trying to add VLAN #2 to IF -:bond0:- error: File exists
Failed to bring up bond0.2.
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
Listening on LPF/vlan2/00:11:43:32:68:ab
Sending on LPF/vlan2/00:11:43:32:68:ab
Sending on Socket/fallback
DHCPDISCOVER on vlan2 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on vlan2 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on vlan2 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on vlan2 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on vlan2 to 255.255.255.255 port 67 interval 9
DHCPOFFER from 10.107.208.1
DHCPREQUEST on vlan2 to 255.255.255.255 port 67
DHCPACK from 10.107.208.1
bound to 10.107.208.131 -- renewal in 21524 seconds.
if-up.d/mountnfs[vlan2]: waiting for interface bond0.2 before doing NFS mounts (warning).
done.
3. The third issue are the IPv6 addresses that are assigned to some interfaces. I expect ipv6 addresses on 'vlan2' and 'lo', but not any of the other interfaces. I'm no kind of IPv6 expert, but what is the need for addresses on these interfaces when most software doesn't even know how to talk to them?
Any help getting /etc/network/interfaces set up properly is greatly appreciated. It was a headache getting it this far, but it is working, as far as sending/receiving packets and stopping/starting/restarting networking and being able to send packets, but it's sloppy.
The idea behind the network configuration is to be able to create openvz VPS's and add veth interfaces to those hosts (multiple ips, broadcasts, etc.). The network the server is on has several subnets and I would like to be able to connect different VPS's to different networks, depending on its needs. This is done by bridging the veth interface (which feeds traffic to the VPS) to an interface that is bound to a single VLAN. I do not want VPSs to connect to untagged interfaces as this would allow a VPS to connect to whatever network it wants to; I instead want that controlled by the VPS configuration on the physical host (CT0).
Thanks,
Axton Grams