My first entry into the Ubiquiti ecosystem...now what?
- Thread starter kosymodo
- Start date
The switch isn't getting an IP as it's very much dumb
I'd already done that...
It seems that I've solved the problem by employing a virtual sledgehammer to crack the virtual nut - I reset the network settings on each of the devices, which has enabled them all to pick up 192.168.10.x addresses. However, in doing so, I've created a new problem. Since my Sky Q box in the living room is now on the 192.168.10.x subnet and the mini box in the bedroom is on the 192.168.1.x subnet, I've broken connectivity between them :/ Is there a networking way around this? If not, simple solution will be to abandon my experiment, and revert everything back to how it was
Yes, if you made a backup of the controller setting before you changed everything. You can just roll back to that point.
Ir you could just allocate fixed IP addresses (with reservations) to your Sky devices so they are all on the same subnet.
Ir you could just allocate fixed IP addresses (with reservations) to your Sky devices so they are all on the same subnet.
I don't think I need to roll the controller back, I can simply not use the LAN2 port, right?
As for allocating fixed IP addresses to all the Sky devices, can I assign a 192.168.1.x address to a device physically attached to a (dumb) switch attached to the LAN2 port, therefore on the 192.168.10.x subnet?
By the way, thanks for your continued help!
Yes, you can just stop using LAN2.
And yes, you can give a device on the 192.168.10.x subnet an IP address of 192.168.1.x and it will show up on the other subnet. The router only sends traffic out to the clients. If it sees your client it will happily deliver and receive traffic from it. If not, it won’t.
Great, I'll have a bash later!
Next question - I have 4 dumb switches on my network. All of which are bog standard 10/100/1000 switches. I have some birthday money to spend. Would I see any real benefit in spending out to swap these switches with USW Flex Minis? My alternative idea is to buy a Cloud Key Plus, to start me off on the road to integrating UniFi Protect with a couple of G3 Bullets. I know there are mixed opinions about UniFi Protect, but, after watching some Crosstalk Solutions and Lawrence Systems reviews, I'm getting swayed towards the idea. I've seen advice about other, more capable, CCTV builds, but I prefer going down the UniFi route. I just like ecosystems...like how I'm engrained into my Apple ecosystem
If Crosstalk Solutions and Lawrence Systems have changed their tune on Protect I’d be very surprised. They both got badly burned when UBNT switched off Unifi Video and the last video I saw from both suggested doing something other than Protect. Lawrence especially have several videos featuring both Dahua NVRs and Synology NVRs.
Ubiquiti have a very nasty habit of just stopping entire product ranges and dropping support for them. I know people who bought USG-XG-8’s on Monday and they were EoL’d on Tuesday. They obviously sent them back but if you were not within the return window you’re absolutely screwed. And that’s precisely what UBNT did the their camera users. The old UNVR products are now basically paperweights.
And on the switches, no. You wouldn’t see any real benefit.
Ubiquiti have a very nasty habit of just stopping entire product ranges and dropping support for them. I know people who bought USG-XG-8’s on Monday and they were EoL’d on Tuesday. They obviously sent them back but if you were not within the return window you’re absolutely screwed. And that’s precisely what UBNT did the their camera users. The old UNVR products are now basically paperweights.
And on the switches, no. You wouldn’t see any real benefit.
Thanks, as always, for your advice!
I set the Sky devices to have fixed IP addresses, and all is working well.
However, I'm now noticing that many of my wireless devices have received IP addresses in the 192.168.10.x range. Surely this isn't right? The wireless network is set to Network: LAN (rather than LAN2), so I don't understand why the devices are getting addresses in the LAN2 range. Any ideas? It doesn't matter as such, more an understanding of why it's happening.
There are a number of issues with the controller at the moment -most prominently the fact that disabling or changing a feature in one interface doesn’t necessarily mean it’s turned off in the other so it stays on. This can be seen in the disable WiFi optimisation setting where you have to turn it off twice to keep it turned off. I suspect you’ve fallen foul of one of these issues and something is sneakily reasserting itself in the other interface.
Had a scan through all settings, and I can't for the life of me find anything set to LAN2 relating to WiFi networks. Very odd. I'll keep an eye on it though, there must be some explanation somewhere