Re: AD-Hoc network specify channel

[Simon Schampijer <simon schampijer de>]

On 05/07/2010 11:10 PM, Dan Williams wrote:
> On Thu, 2010-05-06 at 23:17 +0200, Simon Schampijer wrote:
> > On 04/23/2010 02:15 AM, Dan Williams wrote:
> > > On Sat, 2010-04-17 at 16:02 +0200, Simon Schampijer wrote:
> > > > On 04/14/2010 10:42 PM, Dan Williams wrote:
> > > > > On Tue, 2010-04-13 at 21:36 +0200, Simon Schampijer wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I am trying to create an Ad-Hoc Network with a specific channel. From
> > > > > > the spec [1] I know that I have to set the band as well. However the
> > > > > > created network always has channel 1. The nm-applet does not have an
> > > > > > option to set the channel, and is using channel one, too.
> > > > > >
> > > > > > Using iwconfig to create an Ad-Hoc network I can set a channel fine. Is
> > > > > > it fully implemented or do I miss something else?
> > > > >
> > > > > It should be, though it's likely not possible if you're using
> > > > > nm-connection-editor since the channel/band aren't accessible there.
> > > > > But looking at it now, they *should* be accessible for ad-hoc
> > > > > connections.  So we'll need to whip up some code for page-wifi.c to
> > > > > hide/show them when ad-hoc is selected.
> > > >
> > > > Yes, agreed. Having it accessible as a setting from within nm-applet
> > > > would be nice.
> > > >
> > > > > (this is because wpa_supplicant only has the ability to set the channel
> > > > > for ad-hoc networks, not a limitation in NM.  wpa_supplicant does not
> > > > > have the ability to set a band limitation for infrastructure networks,
> > > > > which means we can't let users limit particular connection to only
> > > > > 802.11a for example)
> > > > >
> > > > > See nm_supplicant_config_add_setting_wireless() in NM for where the
> > > > > frequency gets sent to the supplicant, and build_supplicant_config() for
> > > > > where the channel/band get translated into a frequency.
> > > > >
> > > > > Also check nm_ap_new_fake_from_connection() to ensure that the frequency
> > > > > is getting correctly set on the fake AP.
> > > > >
> > > > > This all should work as long as the connection dict has the band/freq
> > > > > specified.
> > > > >
> > > > > Dan
> > > >
> > > > Actually when looking at the logs something caught my eye. The frequency
> > > > was listed as being 5210 when I specified channel 11 and 'bg' as the
> > > > band. Looking at the code I found a little typo. Patches for master and
> > > > the NETWORKMANAGER_0_7 branch are attached.
> > > >
> > > > Dan, as always, thanks for taking the time to reply that detailed,
> > >
> > > Pushed to stable and master, thanks!
> > >
> > > Dan
> >
> > Hi Dan,
> >
> > is there a new rpm planned for Fedora 11 of the NETWORKMANAGER_0_7
> > branch? Anything I can help here?
>
> Built here:
>
> https://admin.fedoraproject.org/updates/NetworkManager-0.7.2.997-1.fc11

Thanks!

> The best thing you can do is get yourself and 2 other people to test it,
> and if it works give it a +1 karma in the update tool.  After it reaches
> +3 karma, it'll get auto-pushed to stable F11-updates.
>
> Let me know!

Tested here fine as working and pinged others to do testing, too.

Regards,
   Simon