Re: [Xen-users] Domain with openvpn-server-bridge to Dom0-bridge problem

[Tegger <xen@xxxxxxxxx>]

Am 22.06.2010 02:40, schrieb Fajar A. Nugraha:
> On Tue, Jun 22, 2010 at 3:11 AM, Tegger<xen@xxxxxxxxx>  wrote:
>    
> > > start with tcpdump on dom0's eth0 then. Something like "tcpdump -n -i
> > > eth0 host 192.168.100.1". What happens if:
> > > - from openvpn domain, you ping to 192.168.100.1 ->    you should see
> > > packets going through both ways
> > > - from openvpn client, ping to 192.168.100.1 ->    you might see packets
> > > going both ways, one way, or none at all
> > >
> > > That would help you determine where the problem is.
> > >
> > >
> > >        
> > hmm, seems to be working with tcpdump.....so it should work, but it doesn't
> >
> > DOM0:~# tcpdump -n -i eth0 host 192.168.100.1
> > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> > listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
> > 22:04:18.796413 arp who-has 192.168.100.1 tell 192.168.100.205
> >      
> I'm assuming ping from dom0's IP address correctly show up on tcpdump,
> and that you're not having the config mistake that Felix suggested?
>
> So packets arp packets go out of eth0, but no reply came back? Try
> doing tcpdump on destination host (192.168.100.1), see if it gets the
> arp queries.
>
>    
so i tried tcpdump on the Windows Host 192.168.100.1 with ping from 
Windows Openvpn Client 192.168.100.211
and the is a request


tcpdump: listening on \Device\{29B14D72-................}
23:02:16.406250 ARP, Request who-has 192.168.100.1 tell 192.168.100.211, 
length 46
23:02:16.406250 ARP, Reply 192.168.100.1 is-at 00:15:f2:xx:xx:xx, length 28

but nothing more



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users