We have been running IPCop 1.4.21 with Zerina for OpenVPN access and Tunnelblick on the client side successfully for some time.
We recently changed the subnet on the local LAN (Green interface) to be 192.168.64.0 to avoid conflicts when using OpenVPN with public WIFI points set up with subnet 192.168.1.0 (which is what we had on our local LAN before). All machines on Green interface changed numbers and we are successfully communicating out from the LAN and can reach inside and outside from the IPCop machine (Green, Red, Blue, Orange interfaces).
But when running Tunnelblick to access the LAN on the Green interface we get the following warning:
2009-12-01 08:48:55 WARNING: potential route subnet conflict between local LAN [192.168.1.0/255.255.255.0] and remote VPN [192.168.1.0/255.255.255.0]
The local LAN being the WIFI access point we are using on the outside and remote VPN should be our local LAN.
We can see that the VPN tunnel is set up correctly in the Zerina interface, which marks a particular tunnel connection with a particular certificate "Open". In the OpenVPN Connection statistics we can see that some amount of data is transferred, about 8KB.
IPCop and all the client machines have been restarted.
But we get the wrong IP subnet on the Green interface when trying to connect now from the outside.
Where does the 192.168.1.0 subnet setting come from for our Green interface when we have changed it to 192.168.64.0 ?
Are there settings for Zerina which are not changed automatically when changing the IP on the Green interface? Like a config file or something.
Full connect log from Tunnelblick is below.