From: Jan J. K. <ja...@ni...> - 2008-05-22 08:17:09
|
Hi Thomas, I am gettting a bit confused here ;-) after openvpn connects, you can reach the openvpn server (using ping) but you cannot reach anything but the openvpn server? Is that right? if so, then you've got a routing issue at the openvpn *server* side, not the client side. cheers, JJK Thomas Novin wrote: > That route i specified because it's the route of a connected interface > (the clients interface) > > 172.30.11.0 0.0.0.0 255.255.255.0 U 0 0 0 > wlan0 > > So the 172.30.11-address is the client. > > I tried without my update-resolv script and also tried adding > redirect-gateway def1 on the client. > > When I try to send traffic from the client to some random external IP I > can see traffic on tun0 from 10.0.1.6 to the random IP. I can also see > my client IP > openVPN server IP port 443. I can also se openvpn server > >> my client IP. The only place I cannot see the traffic is on tun0 of >> > the client. > > If I ping the servers "openvpn address" 10.0.1.1 that works and I can > see it on tun0 on both directions (still sniffing on the client). > > I can see now that the error message on the server has nothing to do > with my problem! I have always had that problem (looking at old > logfiles). > > Something must be wrong on my client that stops the traffic between the > outgoing interface and the openvpn process/tun0-interface. > > |