Am Freitag, 5. Februar 2010 18:55:56 schrieb Thadeu Lima de Souza Cascardo: > I did not get automatic plinks for a peer. The last time that happened I was using different checkouts of wireless-testing on both nodes and somebody had changed the code to match a new draft version in between. And the one time before that there was a bug in the ath5k code, effectively preventing the device from beaconing. > I want automatic plinks to work. But since I've started to play with it, > why not make the command just work. It's there. If adding plinks > manually to mesh nodes is not permitted, I may just send another patch, > disallowing it entirely and making it explicit in code, comment and git > log. If I'm not mistaken the draft standard says that every node has to actively or passively scan for neighbors and automatically select candidate peers. A candidate peer has to announce a profile (Mesh Information Element) in its beacons that matches the local profile. If manual addition of plinks is allowed you could theoretically force your node to peer with a neighbor running a different profile, e.g. using a different path selection or authentication algorithm, or an implementation based on a different draft version. I can't really think of an use for it. Just my 0.01$. regards Simon Raffeiner -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
