[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Domain with openvpn-server-bridge to Dom0-bridge problem
eth0, the real card, is online for connection to internet so i need only a bridge between tap0 and eth1, the XEN Card.so 192.168.100.x are used for real network and internal XEN network, but not for the connection to vpn. So the virtual tap0 has 192.168.100.210-220 the eth1, XEN Card has 192.168.100.205 and Dom0 has 192.168.100.201 a Windows Domain has 192.168.100.19and the rest is the real network....... i didn't understand how i must change the routings.... Openvpn Dom xen205:~# route Kernel IP routing tableDestination Gateway Genmask Flags Metric Ref Use Iface 192.168.100.0 * 255.255.255.0 U 0 0 0 br0 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0 default fritz.box 0.0.0.0 UG 0 0 0 eth0 DOM0 DOM0:~# route Kernel-IP-RoutentabelleZiel Router Genmask Flags Metric Ref Use Iface 192.168.100.0 * 255.255.255.0 U 0 0 0 eth0 default 20710 0.0.0.0 UG 0 0 0 eth0 Am 21.06.2010 15:33, schrieb Felix Kuperjans: 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. Regards, Felix Kuperjans _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |