I just installed a mesh WiFi network in addition to my ISP-provided router that could barely reach upstairs. I had some locally hosted services set up as per Mediabox. All containers were set up with my machine IP(?) 192.xxx.x.xx and were working great inside my network, which is all I wanted to do while I’m learning. I noticed today that if I connect via the other, mesh WiFi network that this IP can’t be accessed, despite it being the same machine. What’s going on?

All advice much appreciated as I am (obviously) a self hosting novice!

  • railsdev@programming.dev
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    1 year ago

    I’m guessing that both routers are running DHCP and/or running NAT at the same time. You need only one to do all that (the one attached to the WAN/Internet) and the other needs to act as a switch only (usually called access point mode).

    Not sure about all the mesh stuff, but traditionally you’d switch off all the routing functions of the second router and connect it to the other router via the LAN ports. Again, DHCP and actual routing would need to be turned off on the “secondary” routers.

    If all these “routers” (really we should be calling them access points to distinguish which function we’re referencing) are part of the same mesh networking system I’d imagine they’d take care of these issues on their own though, so more details about the network topology would be necessary to be helpful.

    • 1111@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Yo! Based on some of the other answers this seems spot on. I guess the problem is that I was kinda running two routers, when really I wanted the mesh system to act as a series of access points for the original network. I don’t know - but I can confirm that turning the mesh system into ‘Access Point Mode’ fixed this issue for me