|
|
well, i did try downgrading the server to 2.0.9. the behavior didn't change, but i eventually noticed that even though OpenVPN thought it was successfully adding the route 10.8.0.0/24 gw 10.8.0.2, that route never showed up in ROUTE PRINT. i added "route-method exe" to my server config and everything works now, though i have no idea why the ipapi route add wasn't working. maybe a result of windows small business server handicaps. i'm considering whether to go back to 2.1rc and use subnet topology.. you said subnet topology was a lot harder to debug.. why? what are the drawbacks? regards -tavin Tavin Cole wrote: > Jan Just Keijser wrote: > >> Hi, >> >> looked at the log files and everything looks fine but all the way at >> the end it dies: The client gets an interrupt system call (don't know >> why) and decides to break the connection: >> us=396496 event_wait : Interrupted system call (code=4) >> > > that was probably when i hit ^C. > > >> don't know what caused this and I must add that I have never seen this >> myself. >> I did notice that your openvpn server is running a) windows and b) >> routing&remote access. Try disabling the routing&remote access service. >> > > i can't do that, unfortunately. they need the built-in windows pptp vpn. > > >> Other than that, I am clueless (you could try long-shots such as >> downgrading the server to 2.0.9).______________________ OpenVPN mailing lists https://lists.sourceforge.net/lists/listinfo/openvpn-users |