Hi Augustine, On 2/23/25 9:02 PM, A. F. Cano via Freedombox-discuss wrote:
I have a hard time believing that I'm the only one who has trouble with wireguard, or that I'm the only one who has tried to use it on a FreedomBox. Someone please tell me what I'm doing wrong. How does the FreedomBox differ from a standard wireguard implementation? How do I tell it to add 192.168.200.28 to the list of allowedIPs? In the server configuration page, "Allowed IPs" is read-only and only contains 10.84.0.2.
I am still trying to get Wireguard working myself, so I don't have a full answer for you.
But what you are trying to do seems strange. Why do you need to use this 192.168.x.y address?
Usually Wireguard has its own private IP range that starts with 10.x.y.z. Every client should choose an IP address in this range. Note that this is completely independent of any other IP address that the client may have on other network interfaces (for example, assigned by DHCP).
Regards, James
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ Freedombox-discuss mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss
