Well … I think it is a NS problem … or to be precise … problem of some settings I’ve changed when did the initial setup.
So probably it will be better to do a fresh install one more time, do only basic setup like DHCP and then try the VPN.
Hope I’ll have some time during the weekend to do that. Will let you know how it went.
As mentioned in on of my previous posts, I’ve checked this with two separate devices and 2 different certificates - notebook (windows 10) & mobile phone (android).
I have in both devices other connection to a different server running Zentyal and there are no issues to connect.
I am using OpenVPN 2.3.11 on the computer and 1.1.17 (build 76) core 3.0.12 on the android device.
When I did some tests yesterday, it is interesting that I can ping NS when on VPN. I can even login to the GUI on the green interface (administration on the red is not allowed)
I can as well ping 2 devices on red interfaces as well as login to them. However I cannot reach the devices on the LAN. So in some way I am allowed to reach the devices towards internet & NS as such, however I cannot reach devices on the LAN.
This is what I have when in VPN. I am on the 10.10.0.6
Jose, I was just wondering … why have you put all certificates to the configuration folder please? Because I’ve got there only the .ovpn file and it is not asking for anything else. When I’ve give there the .pem as well, nothing changed
sorry, I am quite new in Linux, so may I ask to to write it as for dummies please?
Should I connect to VPN, SSH to NS and write ip ro and then route print?
Or how should I do that please?
OK, so let’s see if I did it right.
I’ve connected to the NS via OpenVPN. Then via PuttySSH I’ve used the ip ro command. The same I did with the cmd in Windows. The results are below.
At the end I’ve disconnected the VPN.
I don’t see a default gateway in NS ip ro output.
On the windows output, I see 10.0.0.4, 10.0.0.6 and 10.0.0.7, but it can be normal on windows, I don’t have past experience.
Could you show the output of db networks show?
[root@firewall-rmg ~]# ip ro
10.0.0.2 dev tun0 proto kernel scope link src 10.0.0.1
10.0.0.0/24 via 10.0.0.2 dev tun0
192.168.3.0/24 dev eth0 proto kernel scope link src 192.168.3.14
201.209.192.0/19 dev eth1 proto kernel scope link src 201.209.207.169
169.254.0.0/16 dev eth0 scope link metric 1002
169.254.0.0/16 dev eth1 scope link metric 1003
default via 201.209.192.1 dev eth1
you might have some misconfiguration in NethServer @MarianH
Yes, thats what I think too. But I was not doing any changes, except those via GUI, because I am not really skilled with Linux yet. So it has to be only something I clicked (probably) and now it doesn’t work properly.