Dashboard-> VPN section : wrong virtual address assigned
The VPN section in the dashboard shows many parameters for all active vpns, one of these, the Virtual Address, is often wrong when the client is another gateway server (e.g. another Nethserver doing a net to net vpn ).
The showed Virtual address can be (random) the point to point of the tun/tap interface, or the remote lan address(in CIDR format), or something (not very clear) like the remote lan address where the last octet and netmask are wrong (e.g. 192.168.0.45C).
Please see the attached file
#1 Updated by Davide Marini about 5 years ago
The values showed by the interface are extracted from the command openvpn status, this is the section (where XXXX stands for the public IP address).
ROUTING TABLE 10.10.17.10,vpn1,XXXX:58458,Fri Nov 7 11:47:40 2014 192.168.38.0/24,vpn2,XXXX:46049,Fri Nov 7 10:13:40 2014 192.168.28.0/24,vpn1,XXXX:58458,Fri Nov 7 10:13:39 2014 10.10.17.6,vpn3,XXXX:24287,Fri Nov 7 11:44:51 2014 192.168.28.1C,vpn1,XXXX:58458,Fri Nov 7 11:47:44 2014 10.10.17.14,vpn2,XXXX:46049,Fri Nov 7 11:47:39 2014 192.168.70.56C,vpn3,XXXX:24287,Fri Nov 7 11:47:44 2014 192.168.28.144C,vpn1,XXXX:58458,Fri Nov 7 11:47:17 2014 192.168.38.1C,vpn2,XXXX:46049,Fri Nov 7 11:47:41 2014 192.168.28.101C,vpn1,XXXX:58458,Fri Nov 7 11:47:00 2014 192.168.70.0/24,vpn3,XXXX:24287,Fri Nov 7 10:13:38 2014 192.168.28.143C,vpn1,XXXX:58458,Fri Nov 7 11:47:17 2014
I noticed that some vpn had more occurrences than others, so I looked at the traffic on the vpn interface and I found that the virtual address ip like 192.168.28.143C are referred to the remote clients of the net-to-net which are doing actually traffic on the vpn.
My suggestion to separate in 2 tables simple host-to-net clients from Net-to-Net clients and show also the clients doing traffic actually , it would be very useful.