Eljas Alakulppi
2008-Jan-26 10:02 UTC
[Xen-users] Windows XP guest: Tap device isn''t passing the traffic to linux
Hello.
I have installed Windows XP as HVM guest and I cannot get the network
working. I want Xen to use vlan 15 (10.3.0.1/24) as the base interface on
which bridge will be based on. Problem is, the tap0 device isn''t
passing
the traffic to the bridge.
Pinging from Windows guest to Dom0:
nanoha scripts # tcpdump -vvv -i tap0
tcpdump: WARNING: tap0: no IPv4 address assigned
tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size 96
bytes
12:48:58.319374 arp who-has 10.3.0.1 tell 10.3.0.2
12:49:03.782449 arp who-has 10.3.0.1 tell 10.3.0.2
12:49:09.290650 arp who-has 10.3.0.1 tell 10.3.0.2
Pinging from Dom0 to Windows guest:
12:51:00.666439 arp who-has 10.3.0.2 tell 10.3.0.1
12:51:00.666799 arp reply 10.3.0.2 is-at ff:61:34:00:00:01 (oui Unknown)
12:51:01.666504 arp who-has 10.3.0.2 tell 10.3.0.1
12:51:01.666864 arp reply 10.3.0.2 is-at ff:61:34:00:00:01 (oui Unknown)
12:51:02.666571 arp who-has 10.3.0.2 tell 10.3.0.1
12:51:02.666929 arp reply 10.3.0.2 is-at ff:61:34:00:00:01 (oui Unknown)
I have modifed /etc/xen/xend-config.sxp to include following line:
(network-script ''network-bridge netdev=vlan15'')
And my /etc/xen/genxp1 is following:
###################################
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
name = "GenXP1"
builder = ''hvm''
kernel = "/usr/lib/xen/boot/hvmloader"
memory = 512
#vcpus=1
pae=0
acpi=0
apic=0
#cpus = ""
disk = [ ''file:/nanoha-md1/xen/genxp1/genxp1.img,ioemu:hda,w'',
''file:/nanoha-md1/xen/cdimages/enwinxpsp2.iso,hdc:cdrom,r'' ]
on_poweroff = ''destroy''
on_reboot = ''destroy''
on_crash= ''destroy''
device_model = ''/usr/lib/xen/bin/qemu-dm''
boot=''c''
sdl=0
vnc=1
vncviewer=0
stdvga=0
serial=''pty''
ne2000=0
vif = [ ''type=ioemu, mac=ff:61:34:00:00:01, bridge=xenbr0'' ]
#####################################
nanoha buzer # /etc/xen/scripts/network-bridge status
===========================================================12: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
link/ether 00:1d:60:60:74:18 brd ff:ff:ff:ff:ff:ff
inet 10.2.0.10/16 brd 10.2.255.255 scope global eth0
inet6 2001:5c0:9205:0:21d:60ff:fe60:7418/64 scope global dynamic
valid_lft 2591941sec preferred_lft 604741sec
inet6 fe80::21d:60ff:fe60:7418/64 scope link
valid_lft forever preferred_lft forever
16: xenbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/ether 42:f8:96:6a:44:ad brd ff:ff:ff:ff:ff:ff
inet 10.3.0.1/24 scope global xenbr0
bridge name bridge id STP enabled interfaces
xenbr0 8000.42f8966a44ad no vif0.0
pvlan15
tap0
vif3.0
10.3.0.0/24 dev xenbr0 proto kernel scope link src 10.3.0.1
10.3.2.0/24 dev vlan16 proto kernel scope link src 10.3.2.1
10.2.0.0/16 dev eth0 proto kernel scope link src 10.2.0.10
10.2.0.0/16 dev eth1 proto kernel scope link src 10.2.0.11
127.0.0.0/8 dev lo scope link
default via 10.2.0.1 dev eth0
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.3.0.0 0.0.0.0 255.255.255.0 U 0 0 0
xenbr0
10.3.2.0 0.0.0.0 255.255.255.0 U 0 0 0
vlan16
10.2.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth0
10.2.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 10.2.0.1 0.0.0.0 UG 0 0 0
eth0
===========================================================
nanoha buzer # ifconfig
eth0 Link encap:Ethernet HWaddr 00:1D:60:60:74:18
inet addr:10.2.0.10 Bcast:10.2.255.255 Mask:255.255.0.0
inet6 addr: 2001:5c0:9205:0:21d:60ff:fe60:7418/64 Scope:Global
inet6 addr: fe80::21d:60ff:fe60:7418/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7786 errors:0 dropped:0 overruns:0 frame:0
TX packets:10523 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:767315 (749.3 Kb) TX bytes:5104544 (4.8 Mb)
Interrupt:19
eth1 Link encap:Ethernet HWaddr 00:1D:60:60:6D:78
inet addr:10.2.0.11 Bcast:10.2.255.255 Mask:255.255.0.0
inet6 addr: 2001:5c0:9205:0:21d:60ff:fe60:6d78/64 Scope:Global
inet6 addr: fe80::21d:60ff:fe60:6d78/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:669 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:57185 (55.8 Kb) TX bytes:2028 (1.9 Kb)
Interrupt:16
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:11261 errors:0 dropped:0 overruns:0 frame:0
TX packets:11261 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4828397 (4.6 Mb) TX bytes:4828397 (4.6 Mb)
pvlan15 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:728 (728.0 b)
tap0 Link encap:Ethernet HWaddr 42:F8:96:6A:44:AD
inet6 addr: fe80::40f8:96ff:fe6a:44ad/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:85 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:13920 (13.5 Kb) TX bytes:594 (594.0 b)
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:336 (336.0 b)
vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:6 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vlan16 Link encap:Ethernet HWaddr 00:1D:60:60:6D:78
inet addr:10.3.2.1 Bcast:10.3.2.255 Mask:255.255.255.0
inet6 addr: fe80::21d:60ff:fe60:6d78/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 b) TX bytes:552 (552.0 b)
xenbr0 Link encap:Ethernet HWaddr 42:F8:96:6A:44:AD
inet addr:10.3.0.1 Bcast:0.0.0.0 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:216 (216.0 b)
-----------------------------------------
All hints are appreciated :)
-Eljas Alakulppi
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
James Harper
2008-Jan-26 11:26 UTC
RE: [Xen-users] Windows XP guest: Tap device isn''t passing the trafficto linux
> > I have installed Windows XP as HVM guest and I cannot get the network > working. I want Xen to use vlan 15 (10.3.0.1/24) as the base interfaceon> which bridge will be based on. Problem is, the tap0 device isn''tpassing> the traffic to the bridge. > Pinging from Windows guest to Dom0: > nanoha scripts # tcpdump -vvv -i tap0 > tcpdump: WARNING: tap0: no IPv4 address assigned > tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size96> bytes > 12:48:58.319374 arp who-has 10.3.0.1 tell 10.3.0.2 > 12:49:03.782449 arp who-has 10.3.0.1 tell 10.3.0.2 > 12:49:09.290650 arp who-has 10.3.0.1 tell 10.3.0.2 >Last time I checked, the xen network scripts added a firewall rule for vifX but not for tapX. Just for testing, try adding an allow rule for ''tap+'' (eg all interfaces starting with ''tap''). If you aren''t using iptables in dom0 then disregard this advice :) James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Eljas Alakulppi
2008-Jan-26 11:40 UTC
Re: [Xen-users] Windows XP guest: Tap device isn''t passing the trafficto linux
> Last time I checked, the xen network scripts added a firewall rule for > vifX but not for tapX. Just for testing, try adding an allow rule for > ''tap+'' (eg all interfaces starting with ''tap''). If you aren''t using > iptables in dom0 then disregard this advice :)Thanks for advice, but currently I have ACCEPT policy on all tables. I checked network-bridge script tho & it uses iptables only if you specify antispoof=1 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Eljas Alakulppi
2008-Jan-26 17:17 UTC
Re: [Xen-users] Windows XP guest: Tap device isn''t passing the traffic to linux
Okey, managed to solve the problem. The cause was the fact that I was using ''ff:61:34:00:00:01'' as my MAC adddress for Windows guest. I changed ''ff'' to ''22'' and traffic is passing properly. Eljas Alakulppi <Buzer@buzer.net> kirjoitti Sat, 26 Jan 2008 12:02:05 +0200:> Hello. > > I have installed Windows XP as HVM guest and I cannot get the network > working. I want Xen to use vlan 15 (10.3.0.1/24) as the base interface > on which bridge will be based on. Problem is, the tap0 device isn''t > passing the traffic to the bridge. > Pinging from Windows guest to Dom0: > ..._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Martin Leben
2008-Feb-02 23:50 UTC
[Xen-users] Re: Windows XP guest: Tap device isn''t passing the traffic to linux
Hi Eljas, Yes, ''ff:61:34:00:00:01'' didn''t work because it is a broadcast address. A broadcast address is specified by setting the least significant bit in the most significant byte to 1. (Example: ''01:xx:xx:xx:xx:xx'') That''s a big NO-NO. :-) See <http://en.wikipedia.org/wiki/MAC_address>. (And by the way, MAC address that begins with "x2", "x6", "xA" or "xE" are so called "locally administered addresses". Their first byte is binary "xxxxxx10".) Best regards, /Martin Leben Eljas Alakulppi wrote:> Okey, managed to solve the problem. The cause was the fact that I was > using ''ff:61:34:00:00:01'' as my MAC adddress for Windows guest. I > changed ''ff'' to ''22'' and traffic is passing properly. > > Eljas Alakulppi <Buzer@buzer.net> kirjoitti Sat, 26 Jan 2008 12:02:05 > +0200: > >> Hello. >> >> I have installed Windows XP as HVM guest and I cannot get the network >> working. I want Xen to use vlan 15 (10.3.0.1/24) as the base interface >> on which bridge will be based on. Problem is, the tap0 device isn''t >> passing the traffic to the bridge. >> Pinging from Windows guest to Dom0: >> ..._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users