https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162023-01-30T07:30:27ZpfSense bugtrackerpfSense - Bug #13916: Interface config doesn't allow colliding IP addresses even if a wireguard interface is usedhttps://redmine.pfsense.org/issues/13916?journal_id=654302023-01-30T07:30:27ZJim Pingle
<ul></ul><p>While it may happen to work in some cases it's not valid in the underlying OS and can have unintended side effects. If the addresses were not on actual OS-level interfaces, I'd agree with you, but in this case you're asking for trouble trying to make the OS attempt to route that way reliably. It may happen to work for you by chance, but that isn't a universal guarantee.</p> pfSense - Bug #13916: Interface config doesn't allow colliding IP addresses even if a wireguard interface is usedhttps://redmine.pfsense.org/issues/13916?journal_id=654312023-01-30T07:30:33ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul> pfSense - Bug #13916: Interface config doesn't allow colliding IP addresses even if a wireguard interface is usedhttps://redmine.pfsense.org/issues/13916?journal_id=654402023-01-30T12:16:57ZFlole Systems
<ul></ul><p>I'm not really sure if I understand what you mean. In my case I have the slightly odd config of having a Wireguard VPN with the IP 10.2.0.2/24. It doesn't matter which IP I use as gateway. Maybe if we limit it even more and say that having Wireguard and a /32 IP the behaviour is no longer undefined? In that case the only host reachable is the gateway and it does work perfectly fine.</p>