|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] Domain with openvpn-server-bridge to Dom0-bridge problem
I think i have a working openvpn, i can connect to openvpn without errors.
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:
Hi,
i have a problem with bridging. I have a Openvpn Domain, with server bridge.
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|