|
|
Will Schroeder wrote:
I have a default gw and an IP until I run the bridge-start script. The
output below is from post execution of the bridge... I have a feeling
something not working correctly during the bridge setup as I do not
remember losing network connectivity under 2.0.4/ 9.2.
I think I will roll back ti 9.2.
On Mon, 2005-11-07 at 20:17 +0100, Klaus Thielking-Riechert wrote:
Will,
On Mon, Nov 07, 2005 at 11:21:42AM -0600, Will Schroeder wrote:
mummer:~/openvpn-2.0.5/sample-scripts # netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.31.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
Hm ... as you got a 'no route to destination' message it seems
to me as you are at leat missing a gateway in order to reach your
remote openvpn partner (probably you are missing your default gateway).
Otherwise you are only able to build a tunnel between boxes on your
own LAN segment.
Regards,
Klaus
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users
Adding
route add default gw 192.168.1.1 to the bridge start script solves the
problem. I still do not see how this install is any differant than the
SuSE 9.2 install.....
____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users
|