* I think we can get away with one queue per mesh STA neighbor for
now. Which is effectively what we have in ath(4) and we will have in
* THanks for the clarification for mesh sequence number. So we:
+ Increment it if we're generating a frame into the mesh network;
+ Keep it the same if we're forwarding a frame to a mesh peer / mesh gate
* If we store the mesh control header in the mbuf, and de-encapsulate
the frame, then re-inject into the VAP path with the correct
destination node, we could then teach the VAP path to check for that
tag and if it's there, populate the mesh header from _that_. If it's
not there, we create a new mesh tag and continue the encapsulation
How's that sound?
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"