172.30.0.X/32 instead of 172.30.0.X/24 and setting AllowedIPs to 0.0.0.0/0 for mobile peers (phones, etc) and X.X.X.X/24, Y.Y.Y.Y/24 for more static peers (remote VMs) where X and Y are the LAN and Wireguard subnets.
172.30.0.X/32 instead of 172.30.0.X/24 and setting AllowedIPs to 0.0.0.0/0 for mobile peers (phones, etc) and X.X.X.X/24, Y.Y.Y.Y/24 for more static peers (remote VMs) where X and Y are the LAN and Wireguard subnets.
172.30.0.X/32 instead of 172.30.0.X/24 and setting AllowedIPs to 0.0.0.0/0 for mobile peers (phones, etc) and X.X.X.X/24, Y.Y.Y.Y/24 for more static peers (remote VMs) where X and Y are the LAN and Wireguard subnets.
> In other words, when sending packets, the list of allowed IPs behaves as a sort of routing table, and when > receiving packets, the list of allowed IPs behaves as a sort of access control list.
>
> This is what we call a Cryptokey Routing Table: the simple association of public keys and allowed IPs.
> In other words, when sending packets, the list of allowed IPs behaves as a sort of routing table, and when > receiving packets, the list of allowed IPs behaves as a sort of access control list.
>
> This is what we call a Cryptokey Routing Table: the simple association of public keys and allowed IPs.
> In other words, when sending packets, the list of allowed IPs behaves as a sort of routing table, and when > receiving packets, the list of allowed IPs behaves as a sort of access control list.
>
> This is what we call a Cryptokey Routing Table: the simple association of public keys and allowed IPs.
https://wiki.archlinux.org/title/WireGuard#Usage
Which operating system(s) are you using?
https://wiki.archlinux.org/title/WireGuard#Usage
Which operating system(s) are you using?
https://wiki.archlinux.org/title/WireGuard#Usage
Which operating system(s) are you using?
/32(s) as Tunnel IP(s) for Peers and being a bit more thoughtful about the AllowedIPs 🤞 I'm only playing around with 3 devices right now, my core router (RouterOS), an Ubuntu 22.04 VM over at Vultr and my iPhone.
/32(s) as Tunnel IP(s) for Peers and being a bit more thoughtful about the AllowedIPs 🤞 I'm only playing around with 3 devices right now, my core router (RouterOS), an Ubuntu 22.04 VM over at Vultr and my iPhone.
/32(s) as Tunnel IP(s) for Peers and being a bit more thoughtful about the AllowedIPs 🤞 I'm only playing around with 3 devices right now, my core router (RouterOS), an Ubuntu 22.04 VM over at Vultr and my iPhone.
I have had more success using point-to-point connections where there are only two ends to each interface. It means you have a ton of interfaces and udp ports. but you can share the host IP across the interfaces. Add to that a simple router proto ala OSPF or RIP and you can navigate around not having a full meshnet.
I have dozens of localnet wireguard connections and many more connections to others that use bgp for route propagation.
I have had more success using point-to-point connections where there are only two ends to each interface. It means you have a ton of interfaces and udp ports. but you can share the host IP across the interfaces. Add to that a simple router proto ala OSPF or RIP and you can navigate around not having a full meshnet.
I have dozens of localnet wireguard connections and many more connections to others that use bgp for route propagation.