340
edits
Changes
Jump to navigation
Jump to search
Corrected info for WD_SendBeacon first input, added possible WD_SetLinkState function.
Line 117:
Line 117:
+
Ioctl 0x1009 input is a buffer/len pair.
Ioctl 0x1009 input is a buffer/len pair.
−WD_SendBeacon second input is the Nintendo tag code 0xDD data, starting after the timestamp. First input is channel?
+WD_SendBeacon second input is the Nintendo tag code 0xDD data, starting after the timestamp. First input is a unknown u16. Nintendo Channel increases this, then wraps around once the limit of 0xFFFF is reached. When state is 1, the tag data is copied to internal config.mpParent.beacon_nintagdata, fixed length of 0x80, when second input is not null. And the first input is written to config.mpParent.unk1_4. Unknown if the beacon is sent immediately, or via a IOS timer? It may be possible to send beacons larger than 0x70 payloadLength at offset 16 in tag data, but that's only possible if the beacon is sent immediately. If beacons are not sent immediately, beacon sending may be disabled by using WD_SetConfig(config, 0, BIT(4)), with config->mpParent.unk1_4 being 0?
+WD_SetLinkState might change which "mode"/"state" is used; 0 for Infrastructure, 1 for Ad-Hoc?
Configuration and info structs:
Configuration and info structs:
Line 189:
Line 191:
u16 unk1_4;//unk field 4 of flags 1 fields.
u16 unk1_4;//unk field 4 of flags 1 fields.
u8 channel;//Not verified if 0, but when non-zero, must be an available Nitro Allowed Channel. See _wd_info.ntr_allowed_channels.
u8 channel;//Not verified if 0, but when non-zero, must be an available Nitro Allowed Channel. See _wd_info.ntr_allowed_channels.
− u8 unka4[131];
+ u8 unka4[3];
+ u8 beacon_nintagdata[128];
wd_privacy mpParent_privacy;//Mode 3, tkip, and aes crypto modes are removed, leaving only modes none, WEP40, and WEP104.
wd_privacy mpParent_privacy;//Mode 3, tkip, and aes crypto modes are removed, leaving only modes none, WEP40, and WEP104.
} mpParent;//Ad-Hoc?
} mpParent;//Ad-Hoc?