By entering this site you need to consent to the use of cookies and their functional use according to this privacy policy. Cookies help us to provide the functional services of the website. Kindly read the below message of use and consent to the use.
The following cookies are stored and shared when accessing this website:
- Internal cookies for the MediaWiki site. This is used for user authentication and article modifications.
- Third-party cookies from Google providing services for Google AdSense and Google Analytics
We will never use data collected outside of the above scope.
Action frames are only sent when done so by [[#SendToOtherGroup]].
Action frames are only sent when done so by [[#SendToOtherGroup]].
−
Communication uses standard sockets and the above Action frames. Switch consoles presumably only use the Action frames to communicate with each other?
+
Communication uses sockets with standard Data frames and the above Action frames. Switch consoles presumably only use the Action frames to communicate with each other?
−
It's unknown how connecting (?) to the group owner is done - there's no response to probe requests sent by a Linux machine.
+
There's no response to probe requests sent by a Linux machine when encryption is enabled. However, connecting works fine with encryption disabled: this uses an AccessPoint for the group owner, and standard DHCP is used, no custom authentication needed. Note that the probe response includes the same Nintendo tags included with the beacon. Once connected, the group-owner sends the same Epigram-vendor Action frame(s) described in [[#ldn]].
−
The DHCP server thread is started by the "nn.lp2p.StateMachine" thread eventually during group [[#CreateGroup|creation]].
+
The DHCP server thread is started by the "nn.lp2p.StateMachine" thread eventually during group [[#CreateGroup|creation]]. Some of the DHCP response option values are, with the disabled-encryption mentioned above: