truncated mDNS name

[wireties]

Our robot is occasionally coming up as roboRIO-1296-FRC (as shown on radio status summary page) instead of roboRIO-1296-FRC.local, anyone else experienced this? We are using the new radio and a Windoze 10 development environment, C++ if that matters.

TIA

[RufflesRidge]

I haven't looked, but I would expect that it would always come up like that. That's the actual host name. ".local" is a shortcut that indicates to use mDNS for the resolution.

[wireties]

I haven't looked, but I would expect that it would always come up like that. That's the actual host name. ".local" is a shortcut that indicates to use mDNS for the resolution.

That is what I thought but I could ping one and not the other. It finally worked itself out, frustrating to wait for though.

[wt200999]

We are seeing the same issue on our side. We can ping 'roboRIO-3005-FRC' and 'roboRIO-3005-FRC.lan' but not 'roboRIO-3005-FRC.local' which means we cannot connect to the driver station. We can send code over LabVIEW, but only by changing the address.

We are using Windows 7 and LabVIEW with the new radio.

To fix, the only thing I have found that works is to reboot the system.

We tried updating the roboRIO firmware as well as disabling other network devices. None of this seemed to help.

Anyone have any ideas?

[euhlmann]

The OM5P-AN uses .lan, while the d-link uses .local.

We just assigned the rio to 10.te.am.2 and used that. mDNS has always been problematic.

[wt200999]

The OM5P-AN uses .lan, while the d-link uses .local.


This can't be it, when I reboot I can see the .local address just fine using the OM5P-AN.


We just assigned the rio to 10.te.am.2 and used that. mDNS has always been problematic.

What do you do for competition?