A lemm.ee refugee ;)

  • 7 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2025

help-circle
  • Are you sure L2 is 192.168.1.0/24 and not something larger that includes 192.168.30.0, e.g.: 192.168.0.0/16?

    Bro/Mam/Sir! Bravo!

    You absolutely fixed it in one line. My friend stupidly set the netmask as /16 even though he doesn’t need such a large IP pool. I changed it and now WG is working.

    There is only one issue remaining, that is my local DNS queries are not being answered on my laptop (On phone + WG, it’s working). But it’s working when I direct my dig queries.

    dig server.lan = not working

    dig @dns.lan server.lan = working

    But ping dns.lan is working. I suspect my DNS IP has not properly percolated to my laptop.

    Thanks a lot!!


  • I’m terribly sorry. I have fixed the case numbers with the item numbers.

    I suspect at least part of the problem is that Android does not tunnel hotspot client traffic.

    On android, it works fine in all scenarios. The Linux laptop is causing issues. I checked another case (Case 5). If the client is Windows, everything works fine. I’ll try to replicate this on another linux machine and check.

    WG running on the Firestick

    I had to search a lot but I found a client which works on the first gen Firestick. Check https://airvpn.org/. They still release a compatible WG client on the ancient android/Amazon device.



  • Hello there. I perfectly understand the risks of my setup. Since it’s a commercial off-the-shelf router, i can’t run a reverse proxy on it, so this is the best that i can do (other than VLANs). It’s also a private network, so I guess it’s fine.

    I used a bit of AI which said that such embedded devices don’t work with reverse proxies. Finding which exact parameters as respected by the router will be time-consuming and the end result is not that great.