This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Domain with openvpn-server-bridge to Dom0-bridge problem
From: Tegger <xen@xxxxxxxxx>
Date: Mon, 21 Jun 2010 22:11:15 +0200
Cc: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Delivery-date: Mon, 21 Jun 2010 13:12:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTimFwSSt0iOON0MBex1Dl3ghzngibxwzPzycuQ6f@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4C1DF1AE.6060002@xxxxxxxxx> <AANLkTimc517jG6znJ66U5r2o40Pu9JEP5mkKOV-x_kYj@xxxxxxxxxxxxxx> <4C1F639E.5000203@xxxxxxxxx> <AANLkTimFwSSt0iOON0MBex1Dl3ghzngibxwzPzycuQ6f@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv: Gecko/20100512 Thunderbird/3.0.5
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 and, but not, this is a physical PC in network
start with tcpdump on dom0's eth0 then. Something like "tcpdump -n -i
eth0 host". What happens if:
- from openvpn domain, you ping to ->  you should see
packets going through both ways
- from openvpn client, ping to ->  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
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 tell
22:04:19.796300 arp who-has tell
22:04:20.796303 arp who-has tell
22:04:22.797323 arp who-has tell
22:04:23.797228 arp who-has tell
22:04:24.797207 arp who-has tell
22:04:44.051085 arp who-has tell
22:04:44.863426 arp who-has tell
22:04:45.863227 arp who-has tell

Xen-users mailing list