196
23.7 Legacy Series / Re: [Solved] Wireguard - Mullvad setup cannot be completed anymore
« on: October 13, 2023, 10:24:48 am »
Hi Franco,
I was reading the evolving thread on GH, and while I cannot say or sure if there ever was a limitation on wireguard-go, I'm 99% sure I created most of he Mullvad GWs on the kmod - while I installed the moment it became available and never looked back.
Now I have two comments on this issue if you don't mind.
- First, Ad's (?) suggestion of using a /24 may be fine for someone in control of both ends of WG, but I'm not terribly fond of the idea...should I have to set up such a thing. I also tried with a /31 before modifying config.xml and didn't work. Both GWs are running fine for more than a year on /32.
- Secondly, while I understand the reasoning of having those tunnel settings in the VIP section I would argue that is the less fortunate from a user experience and even logical point of view.
===================
I would propose amending the Interface GUI with a hidden by default VIP section. This would allow all Interface related settings to be present on a single page - which would be great for usability.
Also, for consistency, all VIP information added on an interface would be presented as an entry in the Virtual IP section as well.
===================
- Lastly, I did a quick search for WG tutorials from other VPN providers here and on the internet - trying to asses whether the VIP thing will be required for more than only Mullvad, and so far I haven' found another. Best written one I found is from iVPN and they don't even go anywhere near a GW in Interfaces...
https://www.ivpn.net/setup/router/opnsense-wireguard/
My proposal may hold some value from a user experience point of view, but if we're only talking Mullvad AND Wireguard - whose lack of updates are a growing concern - Virtual IP section will have to do.
Thanks again
I was reading the evolving thread on GH, and while I cannot say or sure if there ever was a limitation on wireguard-go, I'm 99% sure I created most of he Mullvad GWs on the kmod - while I installed the moment it became available and never looked back.
Now I have two comments on this issue if you don't mind.
- First, Ad's (?) suggestion of using a /24 may be fine for someone in control of both ends of WG, but I'm not terribly fond of the idea...should I have to set up such a thing. I also tried with a /31 before modifying config.xml and didn't work. Both GWs are running fine for more than a year on /32.
- Secondly, while I understand the reasoning of having those tunnel settings in the VIP section I would argue that is the less fortunate from a user experience and even logical point of view.
===================
I would propose amending the Interface GUI with a hidden by default VIP section. This would allow all Interface related settings to be present on a single page - which would be great for usability.
Also, for consistency, all VIP information added on an interface would be presented as an entry in the Virtual IP section as well.
===================
- Lastly, I did a quick search for WG tutorials from other VPN providers here and on the internet - trying to asses whether the VIP thing will be required for more than only Mullvad, and so far I haven' found another. Best written one I found is from iVPN and they don't even go anywhere near a GW in Interfaces...
https://www.ivpn.net/setup/router/opnsense-wireguard/
My proposal may hold some value from a user experience point of view, but if we're only talking Mullvad AND Wireguard - whose lack of updates are a growing concern - Virtual IP section will have to do.
Thanks again