[LeadU2Fun]

We tried to connect as in previous years with a static 10.TE.AM.61 ip address on the laptop and ethernet cable hooked directly to roboRIO. Uploading code through Eclipse would fail. We found out:

1) roboRio had a 172.22.11.2 address only, no 10.TE.AM.# address. Pinging roboRIO-TEAM.local would NOT return ipv4 appropriate ip of 10.TE.AM.#
2) Discovered that the new networking is all DHCP which is being done by the wireless bridge.
3) There is a wireless bridge utility in the labview folder on the laptop after installing the 2015 NI update.
4) Once you hook up laptop to bridge you will get an appropriate 10.TE.AM.# ip address that is DHCP assigned.
5) Once the roboRIO is hooked up to bridge it gets an appropriate 10.TE.AM.# as well.
6) The mDNS will ping back an appropriate ipv4 ip address of 10.TE.AM.# for roboRIO-TEAM.local.
7) Code will upload through Eclipse.

Just an FYI for any Java teams starting to program late in the build season. I hope this saves you some time troubleshooting.