mleku on Nostr: today i learned how to allow specific IP addresses to bypass wireguard tunnels this ...

today i learned how to allow specific IP addresses to bypass wireguard tunnels

this is a set of 4 addresses that are what resolve from ctt.pt and appserver.ctt.pt and appserver2.ctt.pt - essential websites for anyone living in portugal, and irritatingly geofenced so that accessing it via my bulgarian VPS address over wireguard causes the thing to not work.

you add this to the [Interface] block of your wireguard.conf

PreUp = ip route add 3.33.211.116/32 via 192.168.1.254 dev enp7s0
PostDown = ip route del 3.33.211.116/32 via 192.168.1.254 dev enp7s0
PreUp = ip route add 15.197.240.141/32 via 192.168.1.254 dev enp7s0
PostDown = ip route del 15.197.240.141/32 via 192.168.1.254 dev enp7s0
PreUp = ip route add 52.50.235.136/32 via 192.168.1.254 dev enp7s0
PostDown = ip route del 52.50.235.136/32 via 192.168.1.254 dev enp7s0
PreUp = ip route add 54.76.6.35/32 via 192.168.1.254 dev enp7s0
PostDown = ip route del 54.76.6.35/32 via 192.168.1.254 dev enp7s0
PreUp = ip route add 62.28.56.1/32 via 192.168.1.254 dev enp7s0
PostDown = ip route del 62.28.56.1/32 via 192.168.1.254 dev enp7s0

where 192.168.1.254 is the default gateway provided by your router

the CIDR suffix of 32 means "precisely this address" as it is 32 bits which is a full 4 octets address for IPv4

#wireguard #portugal #halp #geofencing #amazon

and yes, their shit is running on AWS

#fuckbezos