View Single Post
  #10   Spotlight this post!  
Unread 14-01-2016, 06:41
rich2202 rich2202 is offline
Registered User
FRC #2202 (BEAST Robotics)
Team Role: Mentor
 
Join Date: Jan 2012
Rookie Year: 2012
Location: Wisconsin
Posts: 1,156
rich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond reputerich2202 has a reputation beyond repute
Re: Router Resolving mDNS with nonsensical addressses

Quote:
Originally Posted by Arhowk View Post
I started investigating this issue after python deploy times went from 2s to ~30s with a huge hang on "finding robot". At this point I'd just go back to my 2015 mindset of "You get a static IP! You get a static IP! Everyone gets a static IP!!!"
I remember in a prior year the Subnet mask causing delays. For competition, you need 255.0.0.0, which means the deploy program will search all possible team numbers. However, if you limit it to 255.255.255.0, then it will only search your team number for the robo rio.