|
||||||||
Thank you all for your response. I got it to work after rebooting the client computer. Apparently an instance of the tun0 interface was still left on even after disconnecting the TunnelBlick client. When I went to reconnect I then had two instances of the tunnel (i.e. tun0 and tun1). This was causing mayhem on my computer. A simple reboot cancelled the tun0 instance and I was able to connect with no problem. I wonder if it were possible to kill the interface from the term window? Jose On Feb 9, 2007, at 4:31 AM, Sven Brill wrote: > Jose Antonio Diaz wrote: >> Has any one had any luck using an openvpn client through m0n0wall >> to connect to an openvpn server? > yes >> >> Specifically I can get the vpn client to connect to the server but >> I cannot see any of the machines across the vpn. > sounds like the openvpn server isn't set up to route anything on > the other end. can you give more details, like address space on the > local end, address space on the remote end, static routes set, if > any, etc? >> >> The problem seems to be point to m0n0wall as I can see the >> machines if I disconnect m0n0wall. > I don't get this sentence. I understand it that you have a local > network behind m0n0wall, on the LAN you have a client that connects > to an openVPN server on some remote network. if not, please clarify. > > Sven > > |