View Single Post
  #1   Spotlight this post!  
Unread 26-02-2016, 08:06
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: PC restart required every time bot is restarted

I haven't seen it this year, but one of the bugs that we weren't able to make much progress on was when the multicast group was not up to date. So the mDNS calls return normally, but return cached results. I was watching the TCP traffic and could tell that the discovery was not going over the wire.

I believe that if you fiddle with the laptop networking enough, it will connect without requiring a reboot. Specifically, when Windows decides it needs to update the multicast group, the mDNS call will suddenly find the device that was connected the whole time. I was never able to find a way to flush or rebuild that info.

If anyone has amazing Windows networking ninja skills and knows how to force this, please chime in.

Greg McKaskle