4,562
edits
Changes
Jump to navigation
Jump to search
Line 1,501:
Line 1,501: − + + + +
→lp2p
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]].
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]]. Some of the DHCP response option values are, with the disabled-encryption mentioned above:
The DHCP server thread is started by the "nn.lp2p.StateMachine" thread eventually during group [[#CreateGroup|creation]]. The DHCP Offer option values are the following, with the disabled-encryption mentioned above:
* "Subnet Mask: 255.255.255.0"
* "DHCP Server Identifier: {...}"
* "Broadcast Address: {...}"
* "IP Address Lease Time: (5s) 5 seconds"
* "IP Address Lease Time: (5s) 5 seconds"
* "Renewal Time Value: (0s) 0 seconds"
* "Renewal Time Value: (0s) 0 seconds"