Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

Please verify the Setup tab has your team number entered and describe what the Diagnostics tab looks like.

It would also be interesting to know what a command line "ping roboRIO-xxyy.local" does. You may also want to restart the computer, the roboRIO and/or the DS at this point.

Greg McKaskle

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

I would not expect the DS to work behind NAT by default (although I haven't tried it). You may be able to set up port forwarding.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

We spent multiple hours trying to get ours to work. Here's what we did:

Plug in router via ethernet, make sure RIO is unplugged.
Make sure your computer IP is set to auto-resolve IPs.
Launch config tool, use it.
Go to your router settings. Ours is 10.27.91.1, for example (team 2791).
Enable DHCP settings. I'm not 100% sure where it is. But you will find a non-marked checkbox with fields under it.
Make default IP range 10.TE.AM.20 to 10.TE.AM.199, subnet 255.255.255.0, default gateway 10.TE.AM.1.
Save changes.
Plug in roboRIO to router via ethernet. Unplug ethernet from computer.
Check to see if you can reach roboRIO-TEAM.local on browser (make sure you have Microsoft Silverlight installed). If not, try to configure via USB.
Find the IP under network settings. It should be 172.x.x.x or 10.TE.AM.x.
If it is 10.TE.AM.X, restart computer and robot. Comms should work.
If it is 172.x.x.x, then go to your router settings and check if the router detects the RIO. Ours was found on DHCP at 10.27.91.100, our computer 10.27.91.20.
If its not found, start over until it works and make sure to hold the reset button on the router.

It's a major pain because not many of us know much about networking, but we got it working.

If you can ping the RIO and it is 10.TE.AM.X, but driver station says no comms, restart computer and robot. It then worked for us.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

I agree with Joe on this. You generally do NOT want NAT. mDNS works using a broadcast and by default, without special configuration, broadcasts only work on a local subnet (e.g. 10.te.am.xx) and will not be forwarded across to another network, which is what NAT creates.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

Finally a question on here in something in my professional field :-)

We at Team 2992 were having the same problem and it was definitely related to IPv6 config on the DLink router. However, switching the config to Autoconfig SLAAC/DHCPv6 did seem to help but still had occasional failures on mDNS. Seems to be some race condition w/ the RoboRIO or W7 or radio on boot as to whether it works or not.

Doing a "ping roborio-xxxx.local" command from command prompt on W7 was producing a ping return showing IPv6 addresses instead of the expected IPv4 10.x.x.x. When this occurred neither Eclipse nor DS would connect.

After some playing around w/ radio config for a while -- we found that disabling IPv6 in Control Panel -> Network & Internet -> Change Adapter Settings -> Wireless Network Connection -> Properties seems to work reliably.

I haven't tested this on a Mac but I would image hard disabling IPv6 on the Mac or Mac VM would work.

When I have more time I will crank up Wireshark and do packet captures on what is happening.

Presumably one could also go into network config on the RoboRIO and turn off IPv6 in the linux config.

Regards
Mike

Mentor Team 2992

CCIE #4885
Cisco Systems, Inc.

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

I concur -- adding a NAT will assuredly only make this harder to get working.

Regards
Mike

Re: Trouble resolving mDNS via Wi-fi on Windows 7 VM
 

We had a similar problem. I found this thread searching for a solution while we were troubleshooting. We had a prototype robot running fine wirelessly, but something happened when we tried the same laptop on our build robot and then came back to the prototype. We could connect wirelessly to the prototype's router again, but couldn't communicate to its roborio. The situation was finally resolved when we re-ran the Bridge Configuration Utility via ethernet to the prototype's router. I'm still not sure what happened to cause the problem, but once we did that we could communicate to the roborio again.

Mark
Mentor-Team 3140