The DHCP server and GUI are basic at best. Great for a new fresh setup. I found it fustrationibg and time consuming porting over a 40-50 device network. Still the static assignment is problematic.
Just wish, i could have just added the mac to ip mappings, had multiple route10 resets and switch reset about 4 times. painful experience was.
Still have a few devices i cant move to static on the fear the dhcp will cause issue.
the internal performance is what i want to see. its only qualitative , things are snappier, apps that had lag connecting to services across vlans (3-6 seconds) now spring spring to life in (1-2 seconds).
@Axon The DHCP reservations can be configured with the “Reserved IPs” and “pool size” settings. We definitely do have the ability to set those up! For example, if you want to start at 192.168.1.100 and end at 192.168.1.200, you would set Reserved IPs to 100 and Pool Size to 100.
Or, if you’re referring to “sticky IP” addressing, which a an IP is bound to a MAC guaranteeing that device always gets the specified IP, that’s available under the Devices tab.
A few things, is there a tutorial or guide to walk though this? I appreciate the take on making things simple, but working in far more complex (and poorly thought through) interfaces, I was bashing my head trying to figure out how to create a simple subnet. Meraki is an example of a simple, but very well laid out GUI that makes it easy to guide people through by sight alone, even if thy’re used to something else or are novices.
As I understand it, you are unable to manage interoperable VLAN traffic at this time? Big goal is to make sure that IoT devices are isolated on their own network far away from internal devices, but still be able to communicate with specified devices, seems like kind of a miss to not have this day one.
Once I got this set up, though, and being able to more or less plug and play with my 10gb WAN connection, I’ve been mostly impressed with it. Please, though, is there any way to reduce the brightness or turn off all the LEDs on this thing? They’re insanely bright. That’s great in a MDF environment, but at home, oof.
The link lights stay enabled regardless of setting, but that other cable is unplugged from its host at the moment. Still, you couldn’t have used LEDs that aren’t capable of signalling the ISS? I’ve never seen LEDs this bright on any network device before.
So you’re seeing the blue link lights on the Route10? They’re not shown in the picture on either Ethernet interface, I suppose it’s possible the picture was taken while both were blinking with traffic, apologies if I made an inaccurate assumption.
Ah, you’re 100% correct, that is not implemented yet as the Route10 is obviously not a switch or AP. I’ll check on when that’s getting implemented and reply here.
Wild. I’m afraid to make any changes in Alta because just changing the icon for the WAP I have directly connected to the Route10 (the white cable in the first image I posted) knocked it offline entirely.
I reset that port through the Alta interface, no change. I power cyled by unplugging, wait 10 seconds, and plugging it back in. No change. I switched to a different PoE port on the Route10, no change. I’m going to power cycle the Route10 I guess.
We definitely want to take a deeper look into this. However, continuing on this thread isn’t quite appropriate. We can continue on the community if you like (in a new thread), switch to email, whatever you want to do.
