I have run into a truly baffling issue, we run a nethserver openvpn basic roadwarrior setup, all was working swimmingly until just recently i am having trouble connecting to anything on the network like the vpn server for example or our crm system.
we use open vpn client with the standard vpn config file with only the remote ip adjusted.
now when i run the client on my laptop right click connect i log in icon goes green and all looks connected fine but i keep getting really intermittent issues continuous pings run but i can’t connect to the device then pings drop then i can connect to the web interfaces.
i have at least 2 other users who are working fine without problems but have now started to get other people experience the same.
as a sanity check and here is where is gets really weird, i built a new server and put it on an isolated network, so that is new server, new router, new switch, new user new config file,
and guess what same issue, has something changed for road warrior set up?
my ip range is 192.168.30.x/23 subnet 255.255.254.0
Do you using same user/password for every Roadwarrior client?
I had issues like yours (with a very old Nethsercurity 1.5.x products) when some users connected at the same time utilizing same credentials.
Tbh no preference on my part. This is the set up I inherited.
You think I should change this? Happy to look at that. Just throwing me
slightly that it has been working fine up until now and weirder still is I
still have people working with thus set up without issues.
Has anything changed on nethserver recently that makes thus set up
redundant currently running on v6.8
I moved to a 6.9 build and same issue just finishing off 7.4 build this
morning will test an confirm.
How would I change to run set up what are the advantages of this over tap?
Will go over the documentation of course just interested from someone that
has experience.
I used TAP into a different linux network appliance.
It was “fast and fun”, because in 2-3 steps i was member of the green network, laying on a bridge. It was easier, because i could access to resources on GREEN without routing problems,internet access issues, routing thinking of what i were looking for. But if TAP segment has the same subnetting of the network i am member (192.168.1.0, for instance, and this is the same subnet of the network used by the VPN client) it can not work.
TUN has quite more headaches, but a bit more of control about network access, firewalling (even user-based rules) and also can achieve hub-and-spoke architecture, therefore you can access from your OpenVPN connection to IPSEC/OpenVPN/DMZ/BLUE network resources.
At the end of the line, i think you should take a chance to try and verify if the TUN setup could solve the issue you are experiencing.
Also: do not forget that NAT could help you to ground to zero the network addressing issue.
@pike is right, you have to choose a different network, 10.0.1.0 should be ok. I have just another 192.168.x.0 network for instance. I recommend to use a network you usually don’t use to avoid problems like having same networks on local/remote and vpn side.
It should work at this point, NethServer does the routing. I actually use an Android openvpn client, which client do you use? Maybe I can reproduce the problem…
How did you setup your client? Easiest way is to download the config and import it in the client.
