8.8.8.8 and 8.8.4.4 are DNS servers at Google, not Gateways.


yes i realize this. I meant set the gateways to use these dns servers. Then at each device I just set the dns to 192.168.1.x (whatever gateway ip is) this way and saves typing.

Well i know what reservations do... but you said assign the reservation of your router to whatever ip dhcp assigned it. so says 192.168.1.101 so now the mac address is locked to 101 but then you said to then set the router itself to a static of 192.168.1.2 so if that was the case you wouldn't set a reservation at all because the reservation for that make is saying set to 101 but the static on the router itself is saying .2

Basically you wouldn't set a static on the router at all. You'd set the reservation for that mac address to .2



Anyways i always set my networks up with statics not reservations. For this install the verizon router is .1, my router .2 and number static devices on up from there. I always set .100-.254 for dhcp but .1-.100 are reserved for statics. I'll set the subnet on everything for 255.255.255.0 unless joel writes back with good reason on why i would want to use diff subnets as he mentioned. Appreciate the info people.

When you go into setting DHCP reservations (in this case Fios Router) it will automatically assign a "static" IP address from its pool of addresses. You can leave this address, using your example, 192.168.1.101, or change it. So, yes what I was saying was that if you wanted the address to be 192.168.1.2, you then change the DHCP reservation of your router, in the Fios router to this new IP address. Renew the lease or power cycle your router and it will now be at that IP address.



"Your router's" Lan would need to be different then that of the Fios router. So if Fios is 192.168.1.2 you need to do something different like 192.168.100.X

Now manually setting your router's WAN IP to static can have pitffalls.
Now I don't foresee Fios changing their subnet of 192.168.1.x, but... if they did, through a software update, equipment change or they decide to change the IP address range of their cable boxes, you can end up with a conflict. Worse, your router and all connected devices loose internet connectivity since the WAN gateway address of your router is no longer valid. By letting your router pull its address via DHCP, the worst that will happen in the same situation is anything that relies on the DMZ would be affected, like your port forwarding set on "Your router" or VPN if any. However, devices still would maintain internet access since your router is always pulling a valid address and has a valid path to the internet.

Ok so I cant just go 192.168.1.1 and on up for rest of devices... i'll have to change everything on my router lan to 192.168.100.x like u mention. But how come you have to do this?



maybe this is what joel was referring to when he said put it on a diff subnet. possible he just meant a diff ip range.


UPDATE- I can't seem to set my router (ubiquiti usb) ip to 192.168.1.2 and have its range of ip's be 192.168.100.x as recommended. Thing is its under Network|Lan in settings where the gateway grabs its ip. But then it auto sets the range for the pool of ip's. It doesn't seem to allow for me to set a WAN IP then a seperate range for lan.

I would have to set my router ip to be 192.168.100.x to allow for that range. So would that work? 192.168.1.1 for the verizon router, my router at 192.168.100.1 and all my internal devices 192.168.100.x?


Config info:
Gateway/Subnet 192.168.1.2/24

Gateway IP
192.168.1.2
Network Broadcast IP
192.168.1.255
Network IP Count
254
Network IP Range
192.168.1.1 - 192.168.1.254
Network Subnet Mask
255.255.255.0

Below this in config you can enter dhcp range. If i stray from 192.168.1.x it won't accept values.

If you are manually setting static addresses for the Fios router......

-Fios LAN is already set to 192.168.1.x
-Change Fios Lan Range so that it starts above 192.168.1.2 (if you want your routers WAN to be 192.168.1.2.
-Set 192.168.1.2 in the Fios DMZ.

Your router...

WAN Settings:
Ip Address 192.168.1.2
Gateway 192.168.1.1
Subnet mask 255.255.255.0


LAN settings
Gateway = 192.168.1.2 (if it even asks)
Lan Subnet IP = 192.168.100.1
IP Rage = what you want it to be. For example, 192.168.100.50 - 192.168.100.150, which would leave you room to set either DHCP reservations or Static addresses outside the range.
Subnet mask 255.255.255.0

ya thats what I'm trying to accomplish. But as stated in above post the ubiquiti usg gateway will not allow this setup it doesn't seem. I cannot set it to have an ip of 192.168.1.2 and then a range of 100.x It will not accept that. The pool has to be 1.x if the ip is set to 1.x




Update think I got it figured out thanks to ubiquiti forums on how to configure this damn gateway on wan and lan side.

It seems you were trying to set up both on the Lan side. hopefully u got it straightened out.

You also need to make sure the DHCP range on the FIOS router covers .1.100 thru however many cable boxes you have. The FIOS boxes will lose their guide and the FIOS mobile app will not work if they cant pull an address from .1.100 on up. Dont know why. Also make sure the DMZ address you assign is out of the DHCP range. I always set the FIOS router DHCP range from .1.100 thru .1.200. Then I always use 192.168.1.222 as the DMZ address and make sure you disable wifi on the FIOS router. WORKS EVERY TIME !

Ok i'll make the changes over the next day or two and see what happens. I just hope the ubiquiti cloud key will work and let me manage it remotely behind the other router. Right now with everything on the 192.168.1.x address range the only way i can get the ubiquiti stuff to work and show online status thru cloud key is to just connect the verizon router ethernet directly to the switch and the usg gateway to the switch thru its ethernet port. The second I plug the usg gateway from verizon router ethernet to usg wan, then from usg lan to switch the entire ubiquiti suite of products loss all internet access and the cloud key goes offline.

hopefully simply switching to .100 fixes this issue.


I gotta say using a full suite of ubiquiti products for the first time ever has been nothing but a major pain in the ass. The entire process has been a complicated cluster F and wizardry to try to get it all setup. Using one of their poe switches, 3 access points, a cloud key and their usg gateway. To get all this stuff online and adopted and working was seriously like a 3 day process. It just kept messing up. Hell even holding the reset to bring them back to default settings didn't even work at one point yet worked at other points. I am really having second thoughts about their hardware. Never in my life have I had such complications and lengthy process just to bring some network equipment online.


-update, tried to change lan side to .100.x send the changes it fails and now my gateway is no longer adopted and will not adopt at all period now, even after i changed it back. this is exactly why ubiquiti stuff is really getting on my nerves. Now i'll have 4 hours trying to get the pos back online. Plus i'll need to change the cloud key IP as well which you can't do thru the management portal only locally via the device's ip. But then i worry if i set that to .100.x and the rest of the devices don't take the new ip ranges i'll lose access to the cloud key management portal and the whole damn network will be down. Making changes like this is a massive pain in the a$$ with ubiquiti.


I am about to just take the ubiquiti router right out the equation and say f it. This is becoming a cluster f that isn't worth my time just for deep packet inspection and some bandwidth usage info that the unit provides.

What do you mean regards .100.x?

This is what I have done:

Set the WAN IP address of the new router to 192.168.1.2

Set the LAN of the new router to 192.168.2.0/24 - doesn't have to be that - it can be anything that does not conflict with the Verizon LAN of 192.168.1.0/24.

Enable the DMZ on the Verizon router to use 192.168.1.2

At this point the new router is effectively sitting out on the internet and should be accessible (in my case via HTTPS) using the WAN IP of the Verizon router.

Frederick

Yes. I realize this. Totally get the addressing scheme. However getting the ubiquiti stuff to accept these changes now is a nightmare. As has been the entire setup of the gear. I seriously spent 10 hours a couple of days ago trying to bring this stuff back online after some changes. It’s so temperamental it’s ridiculous. Doubt I’ll ever use it again.

Never tried that brand of router.

I have only used SonicWall for the last 20 years or so.

Haven't had any issues - they just seem to work.

Frederick

MoCA is for the times when you can't run cables from one place to another. If you can run Cat6, you can run coax, right?

I feel your pain about UBNT.

That's kind of why I never used their routers. Have only used Unifi waps/ 1 Unifi switch and those are still a PITA and flakey. How about not being able to upgrade an old wap on a newer controller version? Ridiculous.

I tried to use an Edge switch for a large AV system I installed in a school. Setting the switch to the proper VLAN I was using, brought the whole school network down.

Couldn't explain why it happened at all. Tried using Tagged/Untagged, didn't matter. After that fiasco, I had to source an unmanaged 48 Port Switch with POE. Better luck finding a unicorn than that switch.

Ya it was a nightmare today getting it all to take the ip changes. Took hours as I expected and magic, wizardry and beating head against wall. Almost done. Gotta reset to default two access points then adopt them. Rest is online on the new ip’s. Takes a mix of the app, the unifi.ubnt.com cloud portal, direct ip address web logins locally. Dancing around six times. Plus up down left right left right ba ba select start. Then I’d finally almost have it and the wattbox would auto reboot my outlets cuz of no internet connectivity during this lol. Plus I couldn’t get at the portal for it to change the ip to get it online lol.


Problems so far:

My wattbox web portal no longer works remotely now. It worked behind the first router. Upnp is enabled on both routers. Idk why it’s not passing it along.

Ubiquiti has an smtp setup where it can email on issues. It now fails and won't send although mail settings are correct.

I wonder what else isn't going to work... like remote programming with rti, remote alerts from overc watt box, etc. ugghhhhhh!!!