OpenVPN Issues setting static ip for clients
-
Hmm, I've not seen that happen before, personally.
There should be a snap out now that has the fixes in.
-
Ok well I edited the file that you updated by hand and your right when I checked the client overrides they showed disabled so I re-enabled them and all seemed fine till I woke up this morning and found the client overrides AGAIN disabled.
Is there still a bug ?
-
I'd wait until you get a snapshot that has the fixes in it before passing judgment, to avoid the possibility of an error in applying the fixes by hand.
-
ok I've applied the snapshot and will wait it out to see whats going to happen but I've run across a new issue now.
my vpn clients appear connected in but their common names show "UNDEF" and they don't show a virtual address, any reason this would happen?
-
Nothing I can see. It's possible the status format of openvpn changed recently, I believe the binary was updated to a new version in the last week or so.
-
Actually this seems to ONLY happen when the client tries to connect using the ip address of WAN2 but if they use the ip address of WAN1 it's fine.
So is this a bug ? -
Not sure on that one. Are you using a single OpenVPN instance on both WANs or two different ones?
-
One OpenVPN instance on both WAN's yes.
-
If you are using UDP, that won't work without some NAT trickery (run it on LAN, port forward OpenVPN from both WANs to LAN IP)
It should work with TCP, but I've never tried it. It's possible that OpenVPN's internal status format shows differently for that, but I'd need to see its raw output to know for sure. If you have someone on both WAN and WAN2, try this:
From a shell:
#telnet localhost <openvpn port="" #="">And once that connects, put in:
status 2And then copy/paste that output here.</openvpn>
-
Ok I switched from UDP to TCP and all seems to be working perfectly now.
Sorry I did the switch before I read this post so I was unable to get the status like you wanted.
