Thread: Router Resolving mDNS with nonsensical addressses
View Single Post
  #3   Spotlight this post!  
Unread 13-01-2016, 18:30
Arhowk's Avatar
Arhowk Arhowk is offline
FiM CSA
AKA: Jake Niman
FRC #1684 (The Chimeras) (5460 Mentor)
  
Join Date: Jan 2013
Rookie Year: 2013
Location: Lapeer
Posts: 542
Arhowk is a splendid one to beholdArhowk is a splendid one to beholdArhowk is a splendid one to beholdArhowk is a splendid one to beholdArhowk is a splendid one to beholdArhowk is a splendid one to behold
Re: Router Resolving mDNS with nonsensical addressses
Quote:
Originally Posted by rzoeller View Post
While I can't attest to this specifically, we had an overall very... weird experience using the new router for RI3D. So this would not surprise me, and validates the issues we had.
Okay, I've also had other rather quirky issues with the new router. For one, whenever I tried to deploy the team number to the router, the router would turn off whenever it was pinged. That problem was fixed after I switched ethernet ports. Not sure what happened there.

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!!!"
__________________
FRC Team 1684 - Head Programmer (2013-2016)
FRC Team 5460 - Programming Mentor (2015-2016)

FIRST in Michigan - Technical Crew (2015-continuing)