Channel Switching

[Francesco]

Are you running any tests?
Does the iw commands to get and set mesh parameters work?
I refer to the ones listed in the howto page such as

   - mesh_retry_timeout
   - mesh_confirm_timeout
   - mesh_holding_timeout
   - mesh_max_peer_links
   - mesh_max_retries
   - mesh_ttl
   - mesh_auto_open_plinks
   - mesh_hwmp_max_preq_retries
   - mesh_path_refresh_time
   - mesh_min_discovery_timeout
   - mesh_hwmp_active_path_timeout
   - mesh_hwmp_preq_min_interval
   - mesh_hwmp_net_diameter_traversal_time



2009/3/4 Brian DeLacey <bdelacey at gmail.com>

> I now understand it's a feature that mesh points are required to be on the
> same channel (frequency) to communicate.
>
> My mesh is back up and running with a half-dozen machines - desktops,
> laptops and netbooks. I also have the Edimax EW-7318Ug USB adapter working
> across all these machines (2573 Ralink Tech, RT2501USB, RT73 chipset.)
>
> I returned to a baseline of Ubuntu 8.10 with all it's updates - including
> Linux 2.6.27-11 - and the Feb 14th build of Linux Wireless. This combo seems
> to work well. I  also meshed in an Acer  (with the Edimax USB) using a March
> 4 '09 daily build of Jaunty - including Linux 2.6.28-8 - and the March 4 '09
> version of Linux Wireless.
>
> I'll try to add more Jaunty builds into the mix, and push the baseline
> ahead incrementally, to see how that goes.
>
>
>
> On Wed, Mar 4, 2009 at 1:27 AM, Brian DeLacey <bdelacey at gmail.com> wrote:
>
>> I tested recent Ubuntu/Jaunty and Linux Wireless (~ 3/3/09) on Dell
>> desktops with wireless PCI cards. (One had an Atheros AR2413 802.11bg NIC;
>> the other Atheros AR5413 802.11 abg NIC.) These could mesh and ping each
>> other.
>>
>> However, I had to put them on the same CHANNEL to make the connection. Is
>> this a bug or a feature?
>>
>> I also tried USB wireless adapters. The chipset is identifed as "2573
>> Ralink Tech, RT2501USB" according to lsusb. The device is a EW-7318Ug USB
>> adapter with chipset RT73. These are  recognized as mesh points -
>> according to "iw list" - however they cannot ping each other. These worked
>> in recent builds, but no longer connect.
>>
>> Brian
>>
>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.open80211s.org
> http://open80211s.com/mailman/listinfo/devel
>
>


-- 
Francesco Cappuccio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://open80211s.com/pipermail/devel/attachments/20090305/8893d9e9/attachment.html