From owner-freebsd-wireless@FreeBSD.ORG  Sat Aug 23 19:50:21 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 450AC118
 for <freebsd-wireless@freebsd.org>; Sat, 23 Aug 2014 19:50:21 +0000 (UTC)
Received: from andre.telenet-ops.be (andre.telenet-ops.be [195.130.132.53])
 by mx1.freebsd.org (Postfix) with ESMTP id D770B3704
 for <freebsd-wireless@freebsd.org>; Sat, 23 Aug 2014 19:50:19 +0000 (UTC)
Received: from [192.168.0.95] ([141.134.88.3])
 by andre.telenet-ops.be with bizsmtp
 id iKqH1o00E04KsaM01KqHiD; Sat, 23 Aug 2014 21:50:17 +0200
Message-ID: <53F8F086.1070207@telenet.be>
Date: Sat, 23 Aug 2014 21:50:30 +0200
From: Chris Van Steenlandt <chris.vansteenlandt@telenet.be>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: "Julian H. Stacey" <jhs@berklix.com>
Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour
References: <201408231238.s7NCc8ME057766@fire.js.berklix.net>
In-Reply-To: <201408231238.s7NCc8ME057766@fire.js.berklix.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: freebsd-wireless@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Aug 2014 19:50:21 -0000

Julian,

I was not aware rc.conf was so sensitive to white space ...
I even think it shouldn't.

Anyhow the blanks were not really there in my rc.conf. I had to retype 
everything in my mail (since my laptop's network doesn't work :) and I 
made a few typo's.
But what I did do is try to put everything on one line (see last line in 
your mail) and for some reason my wireless behaves better now.

If it still does not work correctly, I will use the DLINK DWA 140 dongle 
I still have. I already plugged it in and tested it and it seems more 
stable (based on RALINK chip).

Chris

On 23-08-14 14:38, Julian H. Stacey wrote:
> Hi Chris cc wireless@
>
>> After reading quite some man pages, I finally have my laptop set up as
>> follows :
>> /etc/rc.conf :
>> ifconfig_wlan0 =" ssid myssid"
>> ifconfig_wlan0 ="mode 11g"
>> ifconfig_wlan0 ="-bgscan"
>> ifconfig_wlan0 = "WPA DHCP"
> ( I prefer wired nets & only fumble with wireless when I must, but )
> The above has multiple Bourne shell syntax errors.
>
>> ifconfig_wlan0 =" ssid myssid"
> ................^..^	delete spaces
>> ifconfig_wlan0 ="mode 11g"
> ................^	delete space
>> ifconfig_wlan0 ="-bgscan"
> ................^	delete space
>> ifconfig_wlan0 = "WPA DHCP"
> ................^.^	delete spaces
>
> a test live with with /bin/sh:
>
> ifconfig_wlan0="ssid myssid"
> ifconfig_wlan0="mode 11g"
> ifconfig_wlan0="-bgscan"
> ifconfig_wlan0="WPA DHCP"
> echo $ifconfig_wlan0
>
> & see 3 previous assertions overwritten by the fourth. So try either
>
> ifconfig_wlan0="ssid myssid"
> ifconfig_wlan0="$ifconfig_wlan0 mode 11g"
> ifconfig_wlan0="$ifconfig_wlan0 -bgscan"
> ifconfig_wlan0="$ifconfig_wlan0 WPA DHCP"
>
> or
>
> ifconfig_wlan0="ssid myssid mode 11g -bgscan WPA DHCP"
>
> Cheers,
> Julian