Yes, but unfortunately you can’t assign a specific router to a static IP address other than the default one because not all DHCP servers allow it! So that could cause me problems if I want to route the Yarbo server through a router that filters outgoing data much less! I also work with a UniFi DHCP server, but it’s limited!
I’m using two Wi-Fi connections on a UniFi Dream Pro, and unfortunately, you can’t do much with UniFi’s DHCP server. For example, a machine receiving an IP address can be routed to a different router than the one used by all the other devices on that DHCP server!
Unfortunately, this gateway is filtered!
I don’t want to create special rules for these devices; I’m redirecting them directly to another gateway with different security settings.
So, no, it’s not possible to do this on the UniFi, and I’ve already tried the options, but unfortunately, it doesn’t work. ;-(
Thanks for your help, but I have several VLANs at home and different security levels for users. You can use those options on pfSense, but I find it easier to restore settings using UniFi.
I guess I don’t fully understand what you are trying to do. I’m not trying to give you a hard time. I really wanted to understand the issue. It sounds like we have similiar setups. I have 8 VLANS, 6 WiFi networks with multiple APs and two WANs. I block and filter everything by default. I would have thought a policy based or static route would accomplish what you’re trying to do. It may require some firewall rules but if you dont want to set them up that’s a different story. Again, I just wanted to understand in case I ever run into a similiar issue.
There’s no problem
I have 10 VLANs, one dynamic IP and one static external IP, so 2 internet connections directly to my UniFi router, and I have 10 indoor access points and 4 outdoor ones
Yes, I know, the faster your Wi-Fi connection, the more access points you need because you quickly lose signal due to glass or walls ;-(
The outdoor access points are mainly for 2.4 GHz long range.
So for my dynamic connection, I go directly through the UniFi gateway, but for my static connection, I go through another gateway that connects back to the UniFi via a VLAN.
So it would be really great if we could simply switch to manual IP gateway settings, and maybe even the proxy settings, but we can only dream about that
Also, it might be time it supported WPA3.
One last thing: the Wi-Fi is quite unstable in the router and super slow to connect to the DHCP server. ;-( And it doesn’t often reconnect to a Wi-Fi network, even when it’s within range! If I go into the robot’s network settings and manually restart the connection, it switches from 4G to the selected Wi-Fi network. If I don’t, it takes a very long time to do so.
Anyway, I don’t understand the problem with wanting to assign a static IP address to a Wi-Fi network? For VLANs, there are rules in UniFi to assign a VLAN directly to a MAC address.
One last little thing: it handles 802.11ac very poorly and therefore doesn’t easily switch from one access point to another. ;-( So, these are some of the problems I have with the robot’s Wi-Fi! I have the same problem with a Mammotion, but the connection is super stable, though it also doesn’t support WPA3, manual IP addresses, or IPv6.
There you go, I hope this gives you a better understanding of my network.
And the pfSense is… Much more powerful than UniFi for security.
But I’m keeping UniFi for its ease of use for my family.
If you need more information, you can also contact me directly I’d be happy to chat with you
FYI, the UniFi security package works relatively well and is really very transparent.
These are a few of many reasons using WiFi on the rover isn’t recommended. HaLow and 4G for failover if HaLow is weak is all that is generally recommended.
Yea, I was trying to figure out why you’re using Yarbo with WiFi to begin with. Use HaLow and your problems will go away.
That said, I 100% agree with your assessment of Mammotion’s WiFi implementation. The lack of roaming is a big pinpoint for me. Fixing it doesn’t seem to be a priority for them though.
Well, under normal and ideal circumstances, you hard wire your Data Center to Ethernet, and the DC communicates with Yarbo via the HaLow wireless link which also includes your internet connection.
Using WiFi directly to Yarbo is possible, but because now you’re reliant on the strength of your outdoor WiFi signal, it tends to introduce problems during real world use.
You only want WiFi if working with support. Otherwise don’t use it. Even if support says connect to WiFi, they typically mean make sure it’s connected to the DC.
I see that there are many people who understand me I have no choice but to put this device on a VLAN and assign it a DHCP server for that VLAN! Because I don’t understand why a device like this, which has an integrated computer, can access our network! Whether it’s a company or an individual! Besides, it’s Chinese! I’m not paranoid, it’s just that in China, companies have to obey the state! So, by default, when I have a device on my network that can be connected directly to via 4G, I isolate it and put it on a separate router that is restricted and monitored precisely for the return connection! That’s my reason for manually assigning a static IP address, but I’m probably asking for too much! Thank you all for your comments, and have a good day everyone, and happy Cadana Day Take care
So yes, you should hardwire the DC to your network switch. Create an isolated VLAN and assign that switch port to the VLAN. And disconnect the rover from WiFi.
This will resolve network reliability issues while also addressing your security related concerns.