If I'm reading your information correctly, the bridge (br0) of your
Openvpn domain only connects to eth1 (XEN-Dom0) and to tap0 (Openvpn's
virtual interface), but not to eth0 (pass-through real nic). If that was
true, your problem lies there.
Another point could be, that your routes are messed up. You seem to be
using 192.168.100.x as the real external network *and* the internal XEN
network. But by assigning two ip addresses to eth0 and eth1 in Openvpn
domain, you get two routes for 192.168.100.0/24, leaving the choice to
the operating system. There should be only one address assigned to the
bridge, I think.
I hope one of those points helps you.
Am 21.06.2010 15:05, schrieb Tegger:
> I think i have a working openvpn, i can connect to openvpn without
> I have at the moment 2 Domains and Dom0. After succesful vpn
> connection, i can connect to the other Domain and Dom0, with SSH and RDP.
> So the Bridge from eth0(real Card,internet connection) to eth1 (XEN)
> seem to be working. But i can't connect to real Network thats
> connected to the Network Card at Dom0. All Domains and Dom0 can ping
> and connect to the PC's in the network.
> The real Network is 192.168.100.x
> Dom0 192.168.100.201
> WindowsDomain 192.168.100.19
> OpenvpnDomain 192.168.100.205 eth1 -- br0 -- tap0
> 192.168.0.10 eth0
> Router 192.168.0.1
> Openvpnclient 192.168.100.210
> Openvpnclient can connect 192.168.100.201 and 192.168.100.19, but not
> 192.168.100.1, this is a physical PC in network
> Am 21.06.2010 03:36, schrieb Fajar A. Nugraha:
>> On Sun, Jun 20, 2010 at 5:47 PM, Tegger<xen@xxxxxxxxx> wrote:
>>> i have a problem with bridging. I have a Openvpn Domain, with server
>> I can't read your ASCI art, so the information there does not make
>> sense to me. Sorry.
>>> with this constellation i can't connect/ping to the real Network
>>> with an
>>> external VPN Connection. The Openvpn Domain itself can ping
>>> and connect to services in real network. An external VPN User can
>>> only ping
>>> and use Dom0 and other Domains Services.
>>> I can't find the error.....
>> Usually the errors are caused by openvpn-specific setup. I'd make sure
>> that you have a working openvpn setup first, possibly using a phisical
>> machine. A common pitfall it that you're using openvpn bridge, with
>> tap interface on domU, but you forgot to create a bridge connecting
>> the tap interface to domU's eth0 interface.
>> Another possible pitfall is that you want to make the domU act as
>> router, but you forgot to setup iptables on domU.
> Xen-users mailing list
Xen-users mailing list