I am wondering if it is possible to have two wireguard "client" running at the same time on the same router?
Here is what I would like to do :
My phone would be connected to one Wireguard client to have an IP in one country and my computer would be connected to an other Wireguard client to have an IP in a different country. Both devices would be connected to the Wifi of the router.
I am asking this because in my situation, it doesn't work if I install a VPN app on the computer nor the phone. The VPNs have to be on the router.
Yes, I do it myself. You have to be very careful with your routing configuration, to ensure that the traffic goes down the tunnel you want it to go down.
If you want to direct your traffic based on where it's going (i.e., the destination) then it's very simple: just stick the appropriate AllowedIPs directives into your WireGuard configurations.
If you want to direct your traffic based on where it's from (i.e. the source) then it's a bit tricker, and involves, as @powtrix indicated, getting to grips with PBR.
Gotta wonder, why? If both devices are intended to go to separate VPN endpoints, then why doesn't running the VPN client directly on the device work for you? What is the obstacle which prevents you from doing so?
On the phone, I want to be able to do Wifi Calling and it doesn't work if the VPN is on the phone.
And for the computer, I am simply not allowed to install app on it.
In which case, trying to circumvent the policy might not end well for you. While it's certainly possible to achieve what you say your stated goal is, and it's not difficult to achieve either (see my earlier link to PBR documentation), are you sure that a sneaky end-run around the organisation's policy is in your best interests?
I asked them beforehand and it doesn't seems to bother them. Mainly they don't want their computers to be "customized" but the network itself is no problem.
In which case, knock yourself out. If you've got the blessing of your sysadmins then go ahead.
As mentioned previously, if you want to route traffic based on source device, rather than destination, then PBR is the way to go. Start with the documentation linked and see how you get on.
Interesting. My own phones (Android for work, iPhone for personal use) both use Wi-Fi calling because I live in an area with awful mobile reception, and both phones have VPNs enabled (local VPNs for ad-blocking applications, but still the VPN stack is active). In both cases Wi-Fi calling works.
I've even taken both phones to other countries and had Wi-Fi calling back to home work successfully, so it didn't appear that I was roaming.
Obviously, every mobile network carrier's capabilities and policies are different.
You might find that, if Wi-Fi calling doesn't work because you're "in another country" when using a VPN client on your phone, then you might face the same challenge when using the router to redirect traffic from your phone. But that's between you and your mobile network provider.
It is actually the opposite : indeed my carrier blocks Wifi Calling when I travel to a different country but even if I use a VPN app on my phone to connect to my home country it still doesn't work. From what I understand, the traffic of Wifi Calling doesn't go throw the VPN app, it's handled by the operating system directly. But it works fine if the VPN is directly on the router
