[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] VLAN guest networking: near 100% packet loss



Hello all,

I am new to the mailing list and have come here to request assistance
with a networking issue. My setup consists of Debian 8 on both dom0
and domU, and the machine is connected to a VLAN tagged port on the
switch meaning that the host must be VLAN-aware.

Dom0 has internet reachability but domU is only able to establish
connections to hosts on the LAN; pings sent to external machines come
back with virtually 100% packet loss but it is unlikely a routing
issue because sometimes one or two packets get through.

Dom0 network configuration is:

auto xenbr0
iface xenbr0 inet manual
    bridge_ports eth1
    bridge_stp off
    bridge_waitport 0
    bridge_fd 0

auto xenbr0.4
iface xenbr0.4 inet static
    address 192.168.4.13
    broadcast 192.168.4.255
    netmask 255.255.255.0
    gateway 192.168.4.1
    vlan-raw-device xenbr0

The configuration file in /etc/xen/ contains the line:

vif = ['bridge=xenbr0,mac=00:16:3e:40:27:fa,ip=192.168.4.21']

Now here is the domU network configuration.

auto eth0
iface eth0 inet static
    address 192.168.4.21
    broadcast 192.168.4.255
    netmask 255.255.255.0
    gateway 192.168.4.1

After restarting networking we can see the default routes and ARP tables.

On dom0:

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.4.1     0.0.0.0         UG    0      0        0 xenbr0.4
192.168.4.0     0.0.0.0         255.255.255.0   U     0      0        0 xenbr0.4

# arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.4.21                     (incomplete)
    xenbr0.4
192.168.4.21             ether   00:16:3e:40:27:fa   C
    xenbr0
192.168.4.1              ether   00:00:5e:00:01:05   C
    xenbr0.4
192.168.4.2              ether   00:17:7c:41:7c:ce   C
    xenbr0.4

DomU:

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.4.1     0.0.0.0         UG    0      0        0 eth0
192.168.4.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

# arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.4.1              ether   20:47:47:8c:d0:4c   C                     eth0

So what happens if I ping 192.168.4.1 from domU and run tcpdump on dom0?

On dom0:

# tcpdump -vv host 192.168.4.21
tcpdump: listening on xenbr0, link-type EN10MB (Ethernet), capture
size 262144 bytes
11:14:57.603076 IP (tos 0x0, ttl 64, id 55216, offset 0, flags [DF],
proto ICMP (1), length 84)
    domU > 192.168.4.1: ICMP echo request, id 725, seq 1, length 64
11:14:57.603086 IP (tos 0x0, ttl 63, id 55216, offset 0, flags [DF],
proto ICMP (1), length 84)
    domU > 192.168.4.1: ICMP echo request, id 725, seq 1, length 64
11:14:57.621871 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
domU tell 192.168.4.1, length 46
...
8 packets captured
11 packets received by filter
0 packets dropped by kernel

DomU:

# ping 192.168.4.1
PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.
^C
--- 192.168.4.1 ping statistics ---
148 packets transmitted, 0 received, 100% packet loss, time 147000ms

Does anyone have experience configuring VLANs with the bridge interface?
-- 
cant [kant]: hypocritical and sanctimonious talk, typically of a
moral, religious, or political nature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.