View Single Post
  #4   Spotlight this post!  
Unread 26-01-2016, 01:28
virtuald's Avatar
virtuald virtuald is offline
RobotPy Guy
AKA: Dustin Spicuzza
FRC #1418 (), FRC #1973, FRC #4796, FRC #6367 ()
Team Role: Mentor
 
Join Date: Dec 2008
Rookie Year: 2003
Location: Boston, MA
Posts: 1,043
virtuald has a brilliant futurevirtuald has a brilliant futurevirtuald has a brilliant futurevirtuald has a brilliant futurevirtuald has a brilliant futurevirtuald has a brilliant futurevirtuald has a brilliant futurevirtuald has a brilliant futurevirtuald has a brilliant futurevirtuald has a brilliant futurevirtuald has a brilliant future
Re: Why does RobotPy take longer to deploy?

4480, were you able to resolve your issue?

I'm sitting down with a roborio and the router finally, and I'm having a similar issue. I did reflash the router, and I can confirm that it's definitely a DNS issue (at least, on my mac it is):

Examining the tcpdump output, it looks like this is happening:
  • t=0, query to multicast 5353
  • t=0.1 response from roborio on IPv6
  • t=0.2 cache flush AAAA from roborio?
  • OSX sends 6 ICMP6 neighbor solicitations trying to find IPv6 address of roborio, no responses
  • t=6 first ssh syn packet to roborio from computer (ipv4)

Here's the raw tcpdump output for those interested:

Code:
OSX Computer is 10.24.23.143
Router is 10.24.23.129
RoboRIO is 10.24.23.22

01:23:50.827794 IP 10.24.23.143.55752 > 10.24.23.129.53: 65077+ SOA? local. (23)
01:23:50.830292 IP 10.24.23.129.53 > 10.24.23.143.55752: 65077 Refused 0/0/0 (23)

01:23:50.945125 IP 10.24.23.143.5353 > 224.0.0.251.5353: 0 [2q] A (QU)? roborio-2423-frc.local. AAAA (QU)? roborio-2423-frc.local. (46)
01:23:50.945654 IP6 fe80::aebc:32ff:febf:435d.5353 > ff02::fb.5353: 0 [2q] A (QU)? roborio-2423-frc.local. AAAA (QU)? roborio-2423-frc.local. (46)
01:23:50.948130 IP 10.24.23.22.5353 > 224.0.0.251.5353: 0*- [0q] 2/0/0 (Cache flush) AAAA fe80::280:2fff:fe17:fa48, (Cache flush) A 10.24.23.22 (78)
01:23:51.120263 IP6 fe80::aebc:32ff:febf:435d > ff02::1:ff17:fa48: ICMP6, neighbor solicitation, who has fe80::280:2fff:fe17:fa48, length 32
01:23:52.121609 IP6 fe80::aebc:32ff:febf:435d > ff02::1:ff17:fa48: ICMP6, neighbor solicitation, who has fe80::280:2fff:fe17:fa48, length 32
01:23:53.122867 IP6 fe80::aebc:32ff:febf:435d > ff02::1:ff17:fa48: ICMP6, neighbor solicitation, who has fe80::280:2fff:fe17:fa48, length 32
01:23:55.124184 IP6 fe80::aebc:32ff:febf:435d > ff02::1:ff17:fa48: ICMP6, neighbor solicitation, who has fe80::280:2fff:fe17:fa48, length 32
01:23:56.125393 IP6 fe80::aebc:32ff:febf:435d > ff02::1:ff17:fa48: ICMP6, neighbor solicitation, who has fe80::280:2fff:fe17:fa48, length 32
01:23:57.146408 IP6 fe80::aebc:32ff:febf:435d > ff02::1:ff17:fa48: ICMP6, neighbor solicitation, who has fe80::280:2fff:fe17:fa48, length 32
01:23:58.158048 IP 10.24.23.143.52204 > 10.24.23.22.22: Flags [S], seq 608500754, win 65535, options [mss 1460,nop,wscale 5,nop,nop,TS val 2000205903 ecr 0,sackOK,eol], length 0
01:23:58.160321 IP 10.24.23.22.22 > 10.24.23.143.52204: Flags [S.], seq 2654078593, ack 608500755, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 5], length 0
Interestingly enough, I found a workaround. If I connect to roborio-2423-frc.lan, that works almost instantly. Of course, it would only work when connected to the router, and I suspect the router will be configured differently at competition...
__________________
Maintainer of RobotPy - Python for FRC
Creator of pyfrc (Robot Simulator + utilities for Python) and pynetworktables/pynetworktables2js (NetworkTables for Python & Javascript)

2017 Season: Teams #1973, #4796, #6369
Team #1418 (remote mentor): Newton Quarterfinalists, 2016 Chesapeake District Champion, 2x Innovation in Control award, 2x district event winner
Team #1418: 2015 DC Regional Innovation In Control Award, #2 seed; 2014 VA Industrial Design Award; 2014 Finalists in DC & VA
Team #2423: 2012 & 2013 Boston Regional Innovation in Control Award


Resources: FIRSTWiki (relaunched!) | My Software Stuff

Last edited by virtuald : 26-01-2016 at 01:54.
Reply With Quote