问题原文
原帖链接 · Coxer · CC BY-SA 4.0
I have a Wireguard VPN setup that basically looks like this:
P1 ---- S ---- P2 --- Internet
IP addreses:
P1 = 10.200.1.5
S = 10.200.1.1
P2 = 10.200.1.3
I am redirecting all traffic of P1 to S by specifying allowedIps = 0.0.0.0/0 in P1's client config.
Now I want that S routes that traffic to P2. I tried the following on S:
ip rule add from 10.200.1.5 lookup 200
ip route add default via 10.200.1.3 dev wg0 table 200
sysctl -w net.ipv4.ip_forward=1
However, when I run tcpdump on P2 I cannot see any traffic coming in. Also P1 is not experiencing any internet connectivity.
Edit: Testing the custom routing table on S via
ip route get 8.8.8.8 from 10.200.1.5 iif wg0
gives the following response
8.8.8.8 from 10.200.1.5 via 10.200.1.3 dev wg0 table 200
cache iif wg0
which seems fine, however
tcpdump -nn -i wg0
on S shows unreachable as below
09:58:22.207251 IP 10.200.1.5.9134 > 8.8.8.8.53: 36555+ A? play.googleapis.com. (37)
09:58:22.207270 IP 10.200.1.1 > 10.200.1.5: ICMP host 8.8.8.8 unreachable, length 73
已采纳解答
原帖链接 · A.B · CC BY-SA 4.0
WireGuard is a layer 3 interface, as such stating via 10.200.1.3 has no effect, since it would be used for the link layer protocol (typically ARP) to resolve the layer 2 address which doesn't exist here.
So
ip route add default via 10.200.1.3 dev wg0 table 200
can be rewritten:
ip route add default dev wg0 table 200
This helps keep in mind that this part isn't the part selecting a packet to go to P1 or to P2: WireGuard too has its own internal routing: cryptokey-routing, which is done by setting correctly AllowedIPs in each peer's configuration. There's one important limitation: contrary to standard routing, AllowedIPs doesn't support any overlapping address. If this is attempted (like setting on server S AllowedIPs = 0.0.0.0/0 for Peer P2) this will automatically erase the conflicting address(es) on (the) other peer(s) (like erasing AllowedIPs = 10.200.1.5 from Peer P1, because 0.0.0.0/0 overlaps anything else) and connectivity will suffer (S doesn't crypto-route anything to P1: no connectivity anymore).
There are two ways to solve this:
use two different WireGuard interfaces
The previous limitation is per WireGuard interface. Using a second interface avoids such clashes, but will make routing more complex. Probably multiple entries are now needed in the routing table 200 and/or main table: one for the left side interface and one (default) for the right side interface.
do a set substraction of the conflicting ranges
There might be tools actually able to compute the difference between the set 0.0.0.0/0 and the set 10.200.1.5 but I don't know them. There's still a handy tool called
netmask(homepage: https://github.com/tlby/netmask) that will help by converting ranges to the smallest set of netmasks:$ netmask 0.0.0.0:9.255.255.255 10.200.1.3 11.0.0.0:255.255.255.255 0.0.0.0/5 8.0.0.0/7 10.200.1.3/32 11.0.0.0/8 12.0.0.0/6 16.0.0.0/4 32.0.0.0/3 64.0.0.0/2 128.0.0.0/1These are the values (to separate with commas) that should be used on server S for Peer P2's
AllowedIPsso the crypto-key routing will route anything there, except 10.0.0.0/8 of which only 10.200.1.3 will be defined on P2's side, leaving intact the already defined 10.200.1.5 on P1's side: no overlap anymore. Packets sent by P1 to Internet should now proceed to P2 for further routing.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
