Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection

Question

Created 4d

Replies 2

Boosts 0

Participants 2

When using the official Wi-Fi Aware demo app on iOS, with the iOS device configured as a NAN Subscriber, after successfully establishing a peer-to-peer connection with another device via Wi-Fi Aware (NAN), the network path object nwPath.availableInterfaces does not list the nan0 virtual network interface. The nan0 interface is the dedicated NAN (Neighbor Aware Networking) interface used for Wi-Fi Aware data communication. Its absence from availableInterfaces prevents the app from correctly identifying/using the NAN data path, breaking expected Wi-Fi Aware data transmission logic.

log: iOS works as subscriber: [onPathUpdate] newPath.availableInterfaces: ["en0"]

iOS works as publisher: [onPathUpdate] newPath.availableInterfaces: ["nan0"]

Boost

Answer 1

DTS Engineer OP

Apple

3d

breaking expected Wi-Fi Aware data transmission logic.

Breaking whose logic. Logic within the system frameworks? Or your own app’s logic?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

wu_aaron OP

2h

Sorry for the typo earlier. To clarify: after connecting via Wi‑Fi Aware, we need to establish multiple additional NWConnection instances and send URLSession requests over the Wi‑Fi Aware network. However, we’re encountering a system "Nexus assignment error" when attempting to create NWConnections using the nan0 interface. Could you please demonstrate how to properly establish these extra NWConnections and send URLSession data through them?

0