Does WireGuard server listen on 0.0.0.0?

Technical Support for Routers
1

I have two public IPs.
WireGuard could only be connected with one IP but not the other.
I suspect WireGuard listen on a specific interface or a specific IP.

Does WireGuard server listen on 0.0.0.0?

Thanks.

2

Yes, but the route rule may not let the incoming traffic go out by the same interface.

So you need a policy route. example when eth0 as the second interface not being a default route interface, adding rules to make reply on same interface as incoming:

iptables -t mangle -A PREROUTING -i eth0 -p tcp -j CONNMARK --set-xmark 0x80000/0x80000
iptables -t mangle -A PREROUTING -i eth0 -p udp  -j CONNMARK --set-xmark 0x80000/0x80000
iptables -t mangle -A OUTPUT -p tcp -m connmark --mark 0x80000/0x80000 -j CONNMARK --restore-mark --nfmask 0xffffffff --ctmask 0xffffffff
iptables -t mangle -A OUTPUT -p udp -m connmark --mark 0x80000/0x80000 -j CONNMARK --restore-mark --nfmask 0xffffffff --ctmask 0xffffffff
ip rule add fwmark 0x80000 lookup 55
ip route add default dev eth0 via 192.168.10.1 table 55
3

As I see from the default setings, 0x80000 is looking up table 52.
Should I change 0x80000 to something else?
What are the use of table 51, 52 and 53?

Thanks.

4

Preconfigured route table and fwmark:
51 - 0x100000 for DNS
52 - 0x80000 not use VPN traffic
53 - 0x60000 not used

If 0x80000 and table 52 can fit your needs, then change table 55 in the example to table 52.
If not, use fwmark other than preconfigured and may add more routes to table 55.