Unifi USG dhcp issues and not connected

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Unifi USG dhcp issues and not connected

davidcole

6099 posts

Uber Geek
+1 received by user: 1465

Trusted

#239434 17-Jul-2018 14:45

Seems updates for the controller software has started duplicating some of the functions that are now offered in the gui so, because I had static name/up assignments in config.gateway.json the network name definition changed to include eth1. So it stopped working, and then with a firmware upgrade dns wouldn’t start. I managed to fix the network name issue and get dhcp going but I looked today at my clients and only the wireless items were shown, no wired.

I did a reboot of the controller and now the USG is not connected.

I assume I can set inform on it. But I also have lost the UniFi dns entry. It was in the config.boot, how can I get that back so that it can provision the device. I could add it to the config.gateway, but feel I just need a temporary method so that I can force provision.

or should I just start using dnsmasq for static dns assignments of clients?

Previously known as psycik

Home Assistant: Gigabyte AMD A8 Brix, Home Assistant with Aeotech ZWave Controller, Raspberry PI, Wemos D1 Mini, Zwave, Shelly Humidity and Temperature sensors
Media:Chromecast v2, ATV4 4k, ATV4, HDHomeRun Dual
Server Host Plex Server 3x3TB, 4x4TB using MergerFS, Samsung 850 evo 512 GB SSD, Proxmox Server with 1xW10, 2xUbuntu 22.04 LTS, Backblaze Backups, usenetprime.com fastmail.com Sharesies Trakt.TV Sharesight

muppet

2642 posts

Uber Geek
+1 received by user: 1660

Trusted

#2057811 17-Jul-2018 15:24

For something this specific you'd be way, way better posting in the Unifi forums.

davidcole

6099 posts

Uber Geek
+1 received by user: 1465

Trusted

#2057825 17-Jul-2018 15:40

muppet:

For something this specific you'd be way, way better posting in the Unifi forums.

been there done that...you beat them in the fact that you actually replied...and it's normally faster to get resolution here than there.

michaelmurfy

meow
13579 posts

Uber Geek
+1 received by user: 10910

Moderator

ID Verified

Trusted

Lifetime subscriber

#2057967 17-Jul-2018 18:30

Where is your UniFi server running? If it isn't showing up on the controller as online it is a factory reset / reprovision jobbie I'm afraid.

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

davidcole

6099 posts

Uber Geek
+1 received by user: 1465

Trusted

#2057986 17-Jul-2018 19:33

I did a reboot on the USG then it did show up online. The controller is local.

And with that seems to be serving dhcp

delebru

16 posts

Geek
+1 received by user: 1

#2058195 18-Jul-2018 10:13

I would suggest to always clear the config.gateway.json before updating the controller but unfortunately you're past that point :P

You could try removing the gateway.json, doing a factory reset to the USG and adopting it again in the controller. Then add all the DHCP reservations on the controller, not the gateway.json. If you still need some other manual configs in the gateway.json, it may be a good idea to check if the config structure didn't change before adding it to the controller again.

As far as I know the only DHCP provider on a UniFi network is the USG (or USG-P4, USG-XG), not the controller. You may need to manually set the IPs on the controller and USG config after doing the USG factory reset.

What controller version are you using? Did it recommended a specific USG firmware version? What other settings do you have in the gateway.json?

davidcole

6099 posts

Uber Geek
+1 received by user: 1465

Trusted

#2058204 18-Jul-2018 10:22

delebru:

I would suggest to always clear the config.gateway.json before updating the controller but unfortunately you're past that point :P

You could try removing the gateway.json, doing a factory reset to the USG and adopting it again in the controller. Then add all the DHCP reservations on the controller, not the gateway.json. If you still need some other manual configs in the gateway.json, it may be a good idea to check if the config structure didn't change before adding it to the controller again.

As far as I know the only DHCP provider on a UniFi network is the USG (or USG-P4, USG-XG), not the controller. You may need to manually set the IPs on the controller and USG config after doing the USG factory reset.

What controller version are you using? Did it recommended a specific USG firmware version? What other settings do you have in the gateway.json?

Yeah I think that's what I might need to do going forward. I think they're adding more into the controller, so things like static machine ips/names look like they're starting to conflict by being in the config.json.

Also looks like they're using dnsmasq more....so I might be better to start using that for static names (I prefer to have it in a file to hidden int he controller db/settings).

Dell

Shop now for Dell laptops and other devices (affiliate link).

delebru

16 posts

Geek
+1 received by user: 1

#2058242 18-Jul-2018 10:37

Ah yup, if you want to have it all in the config.gateway.json (CGJ :P) you will probably need to:

remove the CGJ
factory reset the USG
adopt the USG
ssh into the USG and manually add one entry of each config you will want in the CGJ for reference
download the full USG configuration into a file
check if the structure changed for your custom settings
remake your CGJ

Not sure if there's an easier way but that would be my approach.