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
It may suffice to only store client information on a single node. In case this node disappears, routes to clients can be rediscovered when needed. This may cause slight hiccups.
If we do this, we'd need the ability to query the network for a specific client given its MAC address.
Basically we need two new packet types:
request information about a MAC (should be flooded for now)
response containing list of IPs for that MAC
Information about a MAC should be requested whenever a new client appears, even if local information is available
The request actually claims the client. If another node thinks it owns the client, it'll compare the timestamp. If the other node has a younger timestamp, it won't respond but instead claim the client itself (by sending a request).Otherwise, it'll respond and let got of the client.
clientmgr_handle_claim dazu umbauen
The text was updated successfully, but these errors were encountered:
tcatm
changed the title
No replicated database?
No replicated database
Apr 14, 2016
With this change the program just prints an error message when
there is no support for nl80211 in the kernel.
To work properly it is checked wether ctx->wifistations_ctx.fd is
initialized (>= 0) before polling at this file descriptor in
function loop().
It may suffice to only store client information on a single node. In case this node disappears, routes to clients can be rediscovered when needed. This may cause slight hiccups.
If we do this, we'd need the ability to query the network for a specific client given its MAC address.
Basically we need two new packet types:
Information about a MAC should be requested whenever a new client appears, even if local information is available
The request actually claims the client. If another node thinks it owns the client, it'll compare the timestamp. If the other node has a younger timestamp, it won't respond but instead claim the client itself (by sending a request).Otherwise, it'll respond and let got of the client.
The text was updated successfully, but these errors were encountered: