Here's a few samples from tcpdump:
14:36:06.308917 (NOV-ETHII) IPX 00000000.00:00:74:64:91:ee.4100 > 00000000.ff:ff:ff:ff:ff:ff.0452: ipx-sap-nearest-req FileServer
14:36:06.883130 (NOV-ETHII) IPX 00000000.00:00:74:64:91:ee.4100 > 00000000.ff:ff:ff:ff:ff:ff.0452: ipx-sap-nearest-req FileServer
14:36:07.123994 802.1d config 8000.02:ff:ee:67:3d:bd.8001 root 8000.02:ff:ee:67:3d:bd pathcost 0 age 0 max 8 hello 2 fdelay 5
14:36:07.445022 (NOV-ETHII) IPX 00000000.00:00:74:64:91:ee.4100 > 00000000.ff:ff:ff:ff:ff:ff.0452: ipx-sap-nearest-req FileServer
14:36:09.123996 802.1d config 8000.02:ff:ee:67:3d:bd.8001 root 8000.02:ff:ee:67:3d:bd pathcost 0 age 0 max 8 hello 2 fdelay 5
14:36:11.123968 802.1d config 8000.02:ff:ee:67:3d:bd.8001 root 8000.02:ff:ee:67:3d:bd pathcost 0 age 0 max 8 hello 2 fdelay 5
14:36:11.878039 IP 192.168.1.50.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
14:36:11.878270 IP 192.168.1.133.32768 > 192.168.1.1.domain: 41817+[|domain]
14:36:11.890160 IP 192.168.1.1.domain > 192.168.1.133.32768: 41817 NXDomain[|domain]
14:36:13.123912 802.1d config 8000.02:ff:ee:67:3d:bd.8001 root 8000.02:ff:ee:67:3d:bd pathcost 0 age 0 max 8 hello 2 fdelay 5
14:36:15.123915 802.1d config 8000.02:ff:ee:67:3d:bd.8001 root 8000.02:ff:ee:67:3d:bd pathcost 0 age 0 max 8 hello 2 fdelay 5
14:36:16.877573 arp who-has 192.168.1.1 tell 192.168.1.133
14:36:16.878623 arp reply 192.168.1.1 is-at 00:20:ed:20:35:ce (oui Unknown)
14:36:16.987026 arp who-has 192.168.1.50 tell 192.168.1.12
The OpenVZ test machine has the addresses 192.168.1.9 and .133 on a /24 network. The "NBT UDP PACKET" looks to be broadcast traffic. Seeing as there's IPX and ARP traffic getting through, there shouldn't be any problems otherwise either.
Those "802.1d config" are coming in once every two seconds. I'm not sure what that is about. I'll look into that as well as what overhead there is tomorrow.
OpenVZ Forum
Members
Search
Help
Register
Login
Home
