View Single Post
  #4   Spotlight this post!  
Unread 05-02-2017, 22:33
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,926
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Multiple problems connecting to the robot using WiFi. No problems using wired eth

The radio does not have a web server for this year, so browsing to 10.12.77.1 won't work for now.

This particular pinging/hosts file oddity is due to an unexpected extra .frc-robot. in the DNS name for the roboRIO. If you look on the roboRIO web page you will see the DNS name listed as: roboRIO-1277-FRC.frc-robot.local

Pinging roboRIO-1277-FRC works because if you look at an ipconfig /all on your PC from a command prompt you will see a DNS suffix listed of frc-robot.local
Pinging will take the DNS name you give it (roboRIO-1277-FRC) and try that, then add the DNS suffix(s) (.local or in this case .frc-robot.local)and try those as well. So, both roboRIO-1277-FRC and roboRIO-1277-FRC.frc-robot.local will work even before adding them to the hosts file.

Eclipse has a problem with that .frc-robot. DNS name because it only tests an explicit set of hardcoded DNS names, e.g., roboRIO-1277-FRC.local & roboRIO-1277-FRC.lan, as well as the static IP address of 10.12.77.2
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 05-02-2017 at 22:43.
Reply With Quote