Hello, is it possible that you can no longer use a Roadwarrior connection if there is a net-to-net connection?
That is not the case.
I have some vm’s set up with both a roadwarrior and n2n connection and I can and have had both working at the same time.
1 Like
Hmm, I created a client. The connection works, but there is no handshake. There is a net-to-net connection with another IPfire that is active. What could be the problem?
How did you create it.
You need to create a configuration at one end as a n2n connection, download the configuration file that it gives you and then import that connection configuration file into the other end.
So it’s not about the n2n connection. That works great; I can access different printers or drives from both locations.
Now that data backup is also working very well, I wanted to switch my clients from OPENVPN to Wireguard using rsync from one location to another. So I added the connection, downloaded the config, and imported it into the Wireguard client. I adjusted the dxndns in the config, and now it should actually work, but…
Have the following rules been followed?
Wireguard Client Pool must be different from the OpenVPN subnet address range , OpenVPN Static IP address pools , IPsec Host-to-Net Virtual Private Network (RoadWarrior).
If you encounter issues trying to use single profile on multiple devices you may need to create a new profile for each device.
edit
If you are migrating RoadWarrior clients from OpenVPN to Wireguard, the hosts in your internal network must accept connections from Wireguard client addresses.
Regards