Hi,
I''m doing some tests with 2 laptops, both equipped whith an Ubiquity
wireless card (chipset Athereos 5212) and driver madwifi 0.9.4.
The first one is configured in station mode, the second, with Xen 3.3, in
managed mode.
My problem is that if I try to do a ping from a virtual machine to the AP I
don''t get response.
I use a bridge configuration on Dom0 and all hosts (AP, interface in station
mode on Dom0, DomU) are on the same subnet.
Communication between AP and dom0 goes well, as well as between dom0 and
domU.
The only way to get an answer from the AP is to use ebtable on both hosts as
follows:
Dom0 -> rewrite the source mac address in the outgoing frame (arp who-has)
from the virtuale to the real one;
From tcpdump on real interface, if I don''t rewrite the
source address:
18:40:46.976378 arp who-has 192.168.0.20 tell 192.168.0.2
18:40:47.007720 IP 192.168.0.20 > 224.0.0.22: igmp v3
report, 1 group record(s)
18:40:47.244722 IP 192.168.0.20.mdns > 224.0.0.251.mdns: 0
[1n] ANY (QU)? suse-pcl.local. (48)
18:40:47.496814 IP 192.168.0.20.mdns > 224.0.0.251.mdns: 0
[1n] ANY (QM)? suse-pcl.local. (48)
18:40:47.748766 IP 192.168.0.20.mdns > 224.0.0.251.mdns: 0
[1n] ANY (QM)? suse-pcl.local. (48)
18:40:48.001223 IP 192.168.0.20.mdns > 224.0.0.251.mdns: 0*-
[0q] 2/0/0 (Cache flush) A 192.168.0.20, (81)
AP : 192.168.0.20
DomU : 192.168.0.2
AP -> rewrite the destination mac address in the outgoing frame (arp
reply) from the virtuale to the real one. If
I don''t use ebtable outgoing frames destinated to the
virtual
machine are dropped from the driver.
Obviously, doing so will not solve anything because the bridge on dom0 not
properly route received frame.
It could be a problem because the virtual interface has not asked to be
associated with the AP?
I hope that I have been clear. Could you help me, please?
Thank you,
Alessandro
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel