|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Ethernet tethering at regionals
When you connect to the field, the field AP will act as a DHCP server and dish out addresses.
When you are in the pit the driver station and roboRIO assign themselves a link local address when they cannot find a DHCP. The roboRIO sends out a mDNS notice saying that it is at what ever address it assigned itself and the driver station can receive and understand it to know how to talk to the roboRIO. |
|
#2
|
||||||
|
||||||
|
Re: Ethernet tethering at regionals
There's more details here: http://wpilib.screenstepslive.com/s/...g-at-the-event
|
|
#3
|
||||
|
||||
|
Re: Ethernet tethering at regionals
We had this exact issue at Hatboro-Horsham but I forgot about it until now. Thanks for posting.
|
|
#4
|
||||
|
||||
|
Re: Ethernet tethering at regionals
Thanks guys. That explains things. I didn't realize at the event that the fallback 169 addresses will still allow things to communicate in the pits, and that any IP addresses obtained while on the field must be released. And of course, since the ip for the DAP is fixed, it cannot be pinged or accessed.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|