I have a DAC cable cable attached from my Route 10’s LAN and to my 10G port on my TrendNETs switch. All devices are connected to the 2.5G ports on my switch.
Are the devices not showing an ip statically assigned? For some reason they still havent fixed this.
Some are, some arent.
I was told the following on Jan 15th
We currently only track IP addresses of:
DHCP-provided addresses from Route10, IP traffic through an Alta Labs AP, IP traffic through an Alta Labs switch (not including Route10)
Looks like they only want you to buy their stuff…
It’s a matter of cross-vendor communication and compatibility, which is of course lower-priority than our own gear that doesn’t require special workarounds.
You’ll find that the other providers only want you to buy their stuff, I’m certain.
Does tracking static ips require special work arounds? Ive never had a router not show static devices until gettting the route10.
Can the IP not be pulled from the ARP adjacency entry, at least on Route10?
I would really like to know this as well. I have never owned a router before from any other brand that has such a hard time names and IPs of the devices on the network.
And what’s odd is that if I connect the 2 2.5Gb ports from my Qnap NAS to the router directly, the activity shows up for both ports as well as the name of the device, MACs but not IP addresses. I might add that theres also a 10G card installed in my NAS thats connected to a separate switch, and all 3 ports are installed into a virtual switch in the NAS. The 10G port isnt listed anywhere in the router though. Also noticed that if i set the port speeds in the router to 2.5g, or auto, the led shuts off, and the ports stop working. Ports have to be set to default for them to detect and operate normally.
The device list is a front and center pain point on the product and I really hope they get it prioritized. When i migrated in early January over mac oui wasn’t working so everything just said no name, and then about a dozen devices had no ip so im chasing things around trying to find what they are by mac address and get them labeled so I know whats what. But devices with a dhcp lease show up under connected devices even if they arent connected still so you can have ghost devices that your chasing for no reason.
Once you understand the quirks its easy to work around them but man this product could make such a better first impression.
This particular outlier is something we intend to support.
Can you confirm if you see the same issue for DHCP devices, and client devices connected through our switches instead of the Route10 directly?
Honestly it drove me so nuts I ended up pulling the stack for now.
