Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Upvote for the idea of disabling the ISP DHCP and setting it up on the Pi instead. However, I think putting in some static routes on the main router should be easy (once it is fully understood - I am still investigating.). Commented Aug 17, 2022 at 16:53
  • @bomben I agree with you, and I would set up a route on a router, if it would have allowed. it. Unfortanetly, my ISP provider is some small local provider with very basic and outdated router. So my only option was to install ISC DHCP. On another site where I have better router, I have used its function to set up a route there. No need for ISCP DHCP on another site. Commented Aug 18, 2022 at 18:33
  • Would you mind sharing your route for the router? Did you also have to set a static route for the router on the other side, where the wireguard server is located? Commented Aug 19, 2022 at 5:28
  • 1
    There is not much to share. Router/modem on one side allows to enter a routing rule. In that rule it is specified that all traffic for the addresses on the other side of the VPN shall be routed to the local computer establishing a VPN to the other side. On the other side that rule cannot be entered. Therefore, DHCP publishes the route. I had to report a bug to the route manufacturer and wait for a long time until I got it working at least on one side. It does not matter which one is the server. Routing has to be established on both sides. Commented Aug 19, 2022 at 11:55
  • Did you enable ipv4.forward on computers establishing VPN? linuxconfig.org/how-to-turn-on-off-ip-forwarding-in-linux Commented Aug 19, 2022 at 19:54