RoboRIO DNS server malfunctioning?

[jalozinski]

First off, thank you for reading.

roboRIO-4787-FRC.local doesn't point to the RIO for some reason. We're still able to connect to the RIO through 10.47.87.2. Pings to roboRIO-4787-FRC.local give "Destination host unreachable". Pings to 10.47.87.2 give reply as expected.

We're able to simply build code to 10.47.87.2, but the driver station is a different story. We can't configure it to look for particular IPs. So as a result we can build successfully, but the "Robot Code" on the DS is red. You would think the Comms light on the DS would be red but it's green. The COMMS LED on the RoboRIO is red.

So our DS won't let us enable the robot because it doesn't think there's robot code. When I FTP into the robot, there is certainly robot code. (There is an FRCUserProgram.jar with a file modified date from the last time I built the code.)

The wireless adapter on the DS computer is currently set to use DHCP. It's a Windows 7 computer.

This might be a meaningless detail but it's possibly related. We discovered these issues when we were demoing two different robots. We turned on our T-Shirt cannon robot and this problematic robot simultaneously. The T-Shirt robot uses a cRIO and a D-Link, it's 2014 or 2013 hardware. But they both had the same SSID when they were both turned on. I realized they would conflict so I turned one off and I configured the bridge of the RIO to use 7874 as the team number, so that the two robots would have different SSIDs. I didn't realize that it wouldn't work since the roboRIO is imaged with our actual team number already. So after that I configured the RIO bridge back to 4787, we turned off the t-shirt robot and kept working on getting this problematic robot working. During this whole affair, the IP of our roboRIO was 10.47.87.59, which might be indicative of something that occurred during the SSID conflict.

Things I've tried:

• A static DHCP lease for roboRIO-4787-FRC.local pointing to 10.47.87.2 on the OM5P config
• Checked the firewall on the DS laptop (everything related to NI and driver station seems to be allowed through)
• Disabled all the NICs except the wireless adapter
• Made sure the NI mDNS Responder Service is running (it is and has been)
• Disabled the firewall in accordance to these instructions
• Reimaged the RIO to v19 (it was already on this image but I figured a clean slate might help
• Configured the bridge with the Bridge Config Utility a few times

I have a feeling that this could be fixed by adding something to the hosts file on the robot, but I have no idea how to access that file. It doesn't seem like I can FTP into the router itself (lies at 10.47.87.1, I used root as the password and username)

If any of this is confusing or anything needs to be clarified please don't hesitate to ask. We could really use some help, we want our robots demo-able soon. Thank you.