Conceptually, it’s fairly easy to understand - nftables, relayd, likely some firewall application.

However, is it as simple as configuring the WAN port as the WiFi interface and leaving it at that? Note that I’m not bothered about double NAT since I won’t be opening any ports, and the main router cannot be touched.

I do want my own SSIDs, my VLANs, control over the firewall etc. Basically, my own network space. If anyone has done this/has an idea of the problems I might run into, please do comment!

Appreciate the help!

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    9 months ago

    Do you even need relayd? I think relayd is for extending the existing NAT, i.e. a wireless bridge operation. At least that’s how I utilized it in a previous setup. If you want to have your own NAT, I think it’s enough to just connect to the upstream wireless network as a client. Not sure if you have to designate the wireless interface as WAN or not.

    • The_Pete@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      Depends if you want to assign IP addresses or not. If you don’t, you just want your own section of the same lan, I.e.all your devices connected to your router but let dhcp pass through then you can just set itnup as an extender

      • ArbiterXero@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 months ago

        He mentioned that he wants to create Second level Nat, that will require new IP addresses and DHCP in the subnet

    • MigratingtoLemmy@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      Thank you! Could you explain a bit about what travelmate does under the hood? I’d like to know the basics of how it operates.