Maybe I’m misinterpreting, but if your gateway from your ISP is also routing and handing out IPs, this is known as a double NAT and can cause all sorts of weird issues. If you’re going from your ISPs gateway to your own router, their device should be bridged so it acts like a static modem.
Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
The box from my isp doesn't support bridge mode. Maybe I am having the double nat problems?
Depending on who you’re with, you can try calling their support and explaining what you’re looking for. I always tell them “I need to disable routing and have my gateway act like a modem. It should give a public IP directly to my router.” This should explain in layman’s to any technician what you’re looking for and they’ll be able to tell you if it can be done. If you’re with a cable or DSL provider, also ask about options to provide your own equipment. This can save you money in the long run, too, if you’re renting the hardware through them at the moment.
It sounds like your ubiquity and your ISP router are on the same LAN segment, which is not a good config.
You should never have multiple DHCP servers configured unless you're intentionally split braining your vlan (only ever done that for HA purposes and using half of the pool on each). Im pretty sure you need to have your ISP connected to your cloud gateway, and all of your gear connected to the ubiquity. Your ISP router should only see your ubiquity, and that's likely a good part of the reason you can't see all the DHCP leases on your ubiquity gear.
Were I in your position, I'd probably disconnect everything and slowly reconnect stuff one piece at a time until you trip over what's causing your issue. I doubt this is the case, but you could also have another DHCP server running on something you forgot about causing issues. Seen that many times before when doing small business network overhauls.
I'll need to check for this. I have the ISP box plugged into the wan port of the router. It shouldn't also be handing out IP, but it very well may be.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DHCP | Dynamic Host Configuration Protocol, automates assignment of IPs when connecting to a network |
| HA | Home Assistant automation software |
| ~ | High Availability |
| IP | Internet Protocol |
| NAT | Network Address Translation |
[Thread #994 for this comm, first seen 12th Jan 2026, 03:05] [FAQ] [Full list] [Contact] [Source code]
The best solution would be to remove the ISP's router from the equation. What ISP do you have? Where do you live? In places like Italy it's trivial to change the router, not so much in France/others
In the USA I am stuck with the router from the isp. I have the ISP router plugged into the wan port of the cloud gateway