[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Domain with openvpn-server-bridge to Dom0-bridge problem
Am 21.06.2010 15:16, schrieb Fajar A. Nugraha: On Mon, Jun 21, 2010 at 8:05 PM, Tegger<xen@xxxxxxxxx> wrote:Openvpnclient can connect 192.168.100.201 and 192.168.100.19, but not 192.168.100.1, this is a physical PC in networkstart 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 22:04:19.796300 arp who-has 192.168.100.1 tell 192.168.100.205 22:04:20.796303 arp who-has 192.168.100.1 tell 192.168.100.205 22:04:22.797323 arp who-has 192.168.100.1 tell 192.168.100.205 22:04:23.797228 arp who-has 192.168.100.1 tell 192.168.100.205 22:04:24.797207 arp who-has 192.168.100.1 tell 192.168.100.205 22:04:44.051085 arp who-has 192.168.100.1 tell 192.168.100.211 22:04:44.863426 arp who-has 192.168.100.1 tell 192.168.100.211 22:04:45.863227 arp who-has 192.168.100.1 tell 192.168.100.211 _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |