On Mon, 2008-07-28 at 08:45 -0400, Steve Brown wrote:
> Although mesh path timeout seems to default to 5000ms, in my testing it
> takes about 50 min. Is this really the timeout that removes a node when
> it's beacon is off for this period?
When a mesh path timeouts it is marked accordingly and
> I've been looking at this too. After the "revamp beacon configuration"
> patch, mesh no longer send beacons. If I revert it, beacons reappear and
> my two stations are found. I'm using both a b43 & zd1211rw.
>
> I believe the problem is in mac80211. It appears that the call to
> ieee80211_if
On Fri, Jul 18, 2008 at 4:12 AM, Andrey Yurovsky <[EMAIL PROTECTED]> wrote:
> This enables draft-802.11s Mesh Point operation. For that we need mesh
> beaconing. Tested with AR5212/AR5213 PCI card against Zydas and b43 mesh
> nodes.
>
> Signed-off-by: Andrey Yurovsky <[EMAIL PROTECTED]>
> ---
> d
2008/7/17 Andrey Yurovsky <[EMAIL PROTECTED]>:
> This enables draft-802.11s Mesh Point operation. For that we need mesh
> beaconing. Tested with AR5212/AR5213 PCI card against Zydas and b43 mesh
> nodes.
>
> Signed-off-by: Andrey Yurovsky <[EMAIL PROTECTED]>
> ---
> diff --git a/drivers/net/wirel
This enables draft-802.11s Mesh Point operation. For that we need mesh
beaconing. Tested with AR5212/AR5213 PCI card against Zydas and b43 mesh
nodes.
Signed-off-by: Andrey Yurovsky <[EMAIL PROTECTED]>
---
diff --git a/drivers/net/wireless/ath5k/base.c
b/drivers/net/wireless/ath5k/base.c
index
