[jtrv]

We had a lot of issues with actually establishing comms as well. For example, we imaged the roboRIO, uploaded Java to it, then we used the Bridge Config tool, and got connected to the router via wifi. Upon plugging a lan cable into the router and roborio, everything seemed to go crazy. we couldn't find anything: the router IP was nowhere to be found, and we could only access the roboRIO by going to roboRIO-2791.local in Chrome. Even on that roboRIO site, we could not access the networking options without getting an error about a corrupted installation. we reset everything 3 times before the meeting ended, and we had established comms a couple times. We power cycled the bot to make sure everything was working, and upon powering on, it stopped working and we had to start over.

IPv4 was on auto retrieve IP.
I found the router settings to be often, NOT ALL THE TIME, at 10.27.91.1. If I tried switching the router to DHCP, Chrome would crash and then we could no longer access 10.27.91.1.

cmd>ipconfig /all did not give any results, and neither did netstat or pathping. When we did get comms, I did a pathping, and it went from my computer directly to the roboRIO IP. (10.27.91.23 -> 10.27.91.21), but then both IPs yielded nothing after power cycle. The RIO is on DHCP, the router is not, and the computer is on auto-retrieve IP/DNS. i don't know what is going on because i don't know much about networking, but if anyone could lend some insight, that would be incredibly appreciated...