Dream Machine Pro

mmerry

Active Member
Reaction score
113
Location
Minnesota
OK, I may be overthinking this so I need to bounce this off some people. Going to be setting up a UDM Pro for a client, currently running a different firewall/router. My idea is to prep the UDM Pro offsite and deliver it to make the switchover much faster. When I plug it into my network, the WAN will be DHCP and I should be able to do all the initial setup. That part seems fine. The issue I am stumbling over is when I take it to the client site, it will replace the router there so I will need to assign the static IP from the ISP. I am worried I will be unable to reach the machine when I deliver it.

My thought is it I will connect it to the client network, it will pull dhcp. I can then go in and assign the static and move the cable. All should start up then or at the least, after a reboot.

What am I missing?
 
Usually what I do in this scenario is

1.) Record existing router relevant information including
- Network Scope (Is it a 192.168.0.1 network? 192.168.1.1)
- DHCP Scope
- SSID & Password
- Static IP

At my office I have my Network configured to 10.10.0.1 so that it doesn't interfere with the default IP of the UDM Pro which is 192.168.1.1

Plug my network in the WAN on the UDM Pro so it gets a WAN IP of my 10.10.0 network - this will get it online.

Next plug in the UDM Pro. Once it boots up, fire up the Unifi App on my phone and it will detect the UDM Pro via Bluetooth. Add the UDM Pro to my account and complete the initial setup process just to get it attached to my account and to be able to get to the UI via

Next I head over to my PC And login to the Unifi dashboard. Update whatever Applications I plan on using (Network etc.) Update the UDM Pro to the latest console OS.

Configure the UDM exactly as their previous router was except the static IP.

Once all that is done, the absolute very last thing you do is configure the static IP. You get disconnected from the UDM then take it onsite and hope you didn't mess up entering the static IP and it fires up the first time.

If it doesn't fire up the first time then reboot the UDM. If it still doesn't fire up, reboot the modem and the UDM.

If it still doesn't fire up then GG you are SoL. Factory reset the UDM and re-do it onsite.

I'm 100% successful on this method.

NOTE: as a bonus if you go full Ubiquiti you can Adopt everything offsite as well, then bring it onsite and it will all just work.
 
Thanks. I have the current network info so this should be simple. Like I said, i am probably overthinking.
 
We prep network equipment at our office all the time, before delivery.

The Dream Machine Pro has the cloud key "built in". Doesn't matter what the WAN info is, doesn't even matter if it does not connect to the internet.
Log into the LAN IP of the UDM...into the Unifi app...boom, go in and edit the WAN settings as needed.

Another method...prep it all at your office ahead of time...updates, pre configure LAN, wireless, etc etc...and then at the last minute, set the WAN to the static for your clients network..and shut her down. Bring onsite, plug in..sit back and enjoy.

I use my laptop, stick it on the LAN side..log into the gateway IP and there ya go.

Even with the UXG gateways...that do not have a built in Unifi controller, their LAN IP gets you to a basic config for WAN and LAN...so even when adopted, you can quickly change it there.
 
We prep network equipment at our office all the time, before delivery.

The Dream Machine Pro has the cloud key "built in". Doesn't matter what the WAN info is, doesn't even matter if it does not connect to the internet.
Log into the LAN IP of the UDM...into the Unifi app...boom, go in and edit the WAN settings as needed.

Another method...prep it all at your office ahead of time...updates, pre configure LAN, wireless, etc etc...and then at the last minute, set the WAN to the static for your clients network..and shut her down. Bring onsite, plug in..sit back and enjoy.

I use my laptop, stick it on the LAN side..log into the gateway IP and there ya go.

Even with the UXG gateways...that do not have a built in Unifi controller, their LAN IP gets you to a basic config for WAN and LAN...so even when adopted, you can quickly change it there.
^^^^. What he said. If you can get on the LAN on any Ubnt device, at least all the ones I've had, you can at least IP the WAN and LAN. Obvious all the other stuff, forwarding, firewall rules, etc etc comes later.
 
Another option I do...the DM Pro, and the UXG..they have those SFP ports...one of which by default is set to WAN (Internet)...as a second port.
We always slide in a 1 gig SFP adapter....and just leave that port to DHCP.
So now you can connect the gateway both ways...you have flexibility...you can carry it in...one of the ports on DHCP...connect it...log in..provision the other WAN port for static...swap the cable, etc.
 
Another option I do...the DM Pro, and the UXG..they have those SFP ports...one of which by default is set to WAN (Internet)...as a second port.
We always slide in a 1 gig SFP adapter....and just leave that port to DHCP.
So now you can connect the gateway both ways...you have flexibility...you can carry it in...one of the ports on DHCP...connect it...log in..provision the other WAN port for static...swap the cable, etc.

VERY GOOD IDEA!

So simple but it completely didn't cross my mind!
 
Have to rush out another setup this morning, staging the setup at our office here...client had a gen1 USG3p and US24 POE.....been acting up past week...so shipping this out to replace 'em.
We ship out every DMP/UXG with this UI SFP+ transceiver in it...this one happens to be going to a dual WAN customer anyways, old school DSL in port 1, and Starlink in port 3.

But without dual WAN, I'd leave port 3 for DHCP anyways just to have that option.

Inside our network, I have 2x different networks coming out of the switch on top of our rack, one is a 192.168.69.0/24 network and another is a 10.50.1.0/24 network...so you can finish off dual WAN setups.

1693235444206.png
 
Last edited:
Back
Top