You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any reason the ad-hoc interface should not have a unique, node-specific name? I imagine it would help with debugging and identifying nodes at a distance. From my understanding, the name of the ad-hoc interface is arbitrary and nodes will still mesh as long as the BSSIDs are the same. I'm probably going to make this change, just wanted to record my thoughts and see what others think.
The text was updated successfully, but these errors were encountered:
Is there any reason the ad-hoc interface should not have a unique, node-specific name? I imagine it would help with debugging and identifying nodes at a distance. From my understanding, the name of the ad-hoc interface is arbitrary and nodes will still mesh as long as the BSSIDs are the same. I'm probably going to make this change, just wanted to record my thoughts and see what others think.
The text was updated successfully, but these errors were encountered: