this post was submitted on 07 Sep 2023
17 points (90.5% liked)

Selfhosted

39256 readers
235 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

Hello again,

Ah I did not realise your ISP router had a modem mode, this gives us another avenue to approach the problem, as far as I see it there are three options

  1. Have a look at your ISP routers settings there may be a way to disable just the wireless radios without putting it in modem mode, depends on the router though and without the model I am unsure if its doable on your router. This would mean you still use your ISP router for routing, DHCP, DNS etc. but the WiFi connection comes from the decos.

  2. Depending on your model of deco you probably have a spare ethernet port or two on the main deco (that's plugged into the ISP router) if that's the case you could buy a cheap unmanaged switch, something along the lines of this: https://amzn.eu/d/dJ3tq1P this will plug into one of the spare ethernet ports on the Deco and act as an 'extender' so you can plug multiple devices into the switch and then the switch into the deco. Then you would reverse what you did on the first post, by gong to the deco app More -> Advanced -> operation mode and selecting WiFi router, after this go to your ISP router unplug all the ethernet devices apart from the deco (and make sure the deco is in port 1) and enable modem mode. This means your ISP router is now a dumb modem and all routing, DHCP, DNS etc is handled by the deco (so if you ever want to port forward it will all be handled by the decos via the deco app and you no longer use your ISP routers admin page). This will still have all your devices on one flat network as it is now and will avoid the double NAT issue.

  3. You do nothing, as long as your not noticing WiFi degradation when your near the ISP router in theory it should cause no issues. If you do choose this option I recommend you go to on the deco app More -> Network Optimisation and run through that, this will make the decos try and find a wifi channel that is not busy, meaning it will in theory put your decos on a different chanel to the ISP router and attempt to avoid clashing.

Let me know if you have anymore questions but if you not, hope that helps!