Thom Paine wrote: > Further to this I have open vpn installed and working. I am able to > vpn to the server. > > I made the openvon network the same as the PLC devices, but I'm unable > to ping them from the server or from my laptop with the vpn active. > > Should I be able to ping 192.168.0.11 from the server (192.168.0.1) > or from a remote client my laptop (192.168.0.6)? > > Do I need to add a route statement or tweak my configuration somehow? > If this isn't supported, should I renumber my vpn subnet and then > allow bridging or something? > > Thanks > Let me make sure I understand this correctly. 1. When you do not have the VPN active, you can ping the PLCs from the server. 2. When you do have the VPN active, you can no longer ping the PLCs from the server. 3. You can not ping the PLCs from a remote computer over the VPN. If all three are true, then I think what is happening is when you bring up the VPN, it creates a route on the server, over the VPN, for the entire 192.168.0.0/24 network. If so, then you need to tweek the VPN setup so that only a route to to the remote client IP address is created. This should let you still ping the PLCs from the server when the VPN is up. You will then need to make sure that a route on the remote client points to the VPN as the route to the 192.168.0.0/24 network. I believe that if you have the VPN on the server side set up correctly, it will route between the VPN connection and the rest of the 192.168.0.0/24 network without problems, but I have not set one up that way. It may require some extra work on the server. But lets take things one step at a time... Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
