Router Resolving mDNS with nonsensical addressses

[Arhowk]

Originally Posted by rzoeller

We experienced issues where a computer would disconnect, and refuse to re-establish robot communication upon reconnection unless the wireless card was taken down entirely (e.g. not just turning off wireless, the adapter had to be disabled and re-enabled or rebooted). This issue persisted across both tested computers (different wireless cards), although both were running Windows 10, so it is possible that the issue does not lie entirely with the router.

Hm, that is strange, this laptop is running windows 10 and I haven't encountered any issues like that.

[rzoeller]

Originally Posted by Arhowk

Hm, that is strange, this laptop is running windows 10 and I haven't encountered any issues like that.

I want to note that we had to manually flash the firmware, as RI3D teams don't get an official KOP. It's possible that the firmware posted is slightly different than what shipped on the KOP router.

[Arhowk]

It's a possibility... we're testing right now but I'll reflash the router when we get back to building and see if that resolves anything

[rzoeller]

Originally Posted by Arhowk

It's a possibility... we're testing right now but I'll reflash the router when we get back to building and see if that resolves anything

The utility installed with the FRC update kit only works with router's that come preinstalled with the KOP system I believe. We followed the directions that came on the box for our router, see here.

[Scott L.]

IPv6 fe80::/64 are link local addresses.
In IPv4 169.254.0.0/16 are the link local addresses