• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle


  • Normally this is bad advice, but if you already have CGNAT you’d be going from double NAT to triple NAT and it probably won’t make anything worse. At least it shouldn’t make things worse for IPv4. If you have 5G internet with CGNAT there’s no excuse for your ISP not giving you proper IPv6. Putting a second router between will complicate your IPv6 setup.

    There are some tricks you can do for IPv4 in the precense of hostile DHCP servers. Serious OSes should allow you to configure a second IP address on the same physical interface, so you could have a dynamic 192.168.0.x assigned by the ISP’s DHCP server and a static 192.168.1.y assigned statically by you, and then you should be able to set up an additional route table entry to access 192.168.1.0/24 using the source address 192.168.1.y. As long as the ethernet/wifi switching between devices doesn’t filter ARP packets based on IP subnet, you should be able to communicate between your machines using fixed IPs on the second subnet.







  • Openwrt/ddwrt are used for routers.

    In the US you usually need to use your ISP’s modem. Even if you buy the modem, it needs to be one that the ISP supports and the ISP will have more control of the device than you do. Even if it were running openwrt or ddwrt, you would not have access to use it.

    I have an Arris modem and it works fine now, but for months there was a bug where it would randomly crash. I don’t know when the bug was fixed, but firmware updates are controlled by the ISP so I had to just reboot it when it would crash. In other words, even if you have good modem hardware, whether it works correctly is up to your ISP.










  • Is it the server telling the server that the client’s port is unreachable or is it the client telling the server that the port is unreachable? Do you see the packets traveling over the Wireguard interface? Do you see the response if you use Wireguard from the client?

    The request traced out is incorrect. WG Client IP initiates a DNS request to Server IP, and then WG Client Addr receives a response from WG Server Addr. The DNS response should come from the same IP that the request was sent to. The client may be rejecting a response coming from an unexpected source. If you’re doing masquerading instead of plain routing, you need to make sure that you’re doing NAT in both directions.