Re: wlan can't discover known networks after relocating

On 9/19/19 7:30 PM, Cy Schubert wrote: > In message om> > , Johannes Lundberg writes: >> --0875960592f275a3 >> Content-Type: text/plain; charset="UTF-8" >> Content-Transfer-Encoding: quoted-printable >> >> Tested today with bgscan added. Didn=E2=80=99t connect to home network unti=

Re: wlan can't discover known networks after relocating

In message , Johannes Lundberg writes: > --0875960592f275a3 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Tested today with bgscan added. Didn=E2=80=99t connect to home network unti= > l I > manually run ifconfig wlan0 scan. > Again,

Re: wlan can't discover known networks after relocating

Tested today with bgscan added. Didn’t connect to home network until I manually run ifconfig wlan0 scan. Again, this is with failover lagg. It did however realize I wasn’t at the office anymore and the ssid field was empty in ifconfig output. Sometimes it stays the same long after I leave the

Re: wlan can't discover known networks after relocating

In message <7938e5fa-67da-35fa-10d0-ee3004438...@freebsd.org>, Johannes Lundber g writes: > > On 9/19/19 3:06 PM, Adrian Chadd wrote: > > So roaming in ifconfig/net80211 is what's set to manual. > > > > wpa_supplicant right now does RSSI threshold based roaming. All of the > > roaming and

Re: wlan can't discover known networks after relocating

I've no idea, bgscan is broken with atheros NICs because the driver still doesn't do background scan without dropping frames :( (one of many thing I'd love to fix, but life/time.) please do experiment though! I think wpa_supplicant's roaming logic would benefit from a lot more work. -adrian

Re: wlan can't discover known networks after relocating

On 9/19/19 3:06 PM, Adrian Chadd wrote: > So roaming in ifconfig/net80211 is what's set to manual. > > wpa_supplicant right now does RSSI threshold based roaming. All of the > roaming and network preferences when wpa_supplicant is running is done > in wpa_supplicant. That's where you have to

Re: wlan can't discover known networks after relocating

So roaming in ifconfig/net80211 is what's set to manual. wpa_supplicant right now does RSSI threshold based roaming. All of the roaming and network preferences when wpa_supplicant is running is done in wpa_supplicant. That's where you have to look. Ideally wpa_supplicant would be triggering

Re: wlan can't discover known networks after relocating

On September 19, 2019 8:20:07 AM PDT, Adrian Chadd wrote: >Roaming is done in wpa_supplicant when it's running.That's where the >smarts >need to be. :( > > > >-adrian > > >On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb > >wrote: > >> On 19 Sep 2019, at 12:28, Tom Jones wrote: >> >> Hi, >> >>

Re: wlan can't discover known networks after relocating

Roaming is done in wpa_supplicant when it's running.That's where the smarts need to be. :( -adrian On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb wrote: > On 19 Sep 2019, at 12:28, Tom Jones wrote: > > Hi, > > freebsd-wireless might be a better list for all this .. > > > > On Tue, Sep 17,

Re: wlan can't discover known networks after relocating

On 19 Sep 2019, at 12:28, Tom Jones wrote: Hi, freebsd-wireless might be a better list for all this .. On Tue, Sep 17, 2019 at 04:36:28PM +, Poul-Henning Kamp wrote: In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.org>, Johannes Lundber g writes: For a long time now

Re: wlan can't discover known networks after relocating

On Tue, Sep 17, 2019 at 04:36:28PM +, Poul-Henning Kamp wrote: > > In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.org>, Johannes > Lundber > g writes: > > >For a long time now I have had this problem with iwm and wlan0. Whenever > >I move between work and home it won't

Re: wlan can't discover known networks after relocating

In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.org>, Johannes Lundber g writes: >For a long time now I have had this problem with iwm and wlan0. Whenever >I move between work and home it won't reconnect automatically and I have >to do wlan0 scan manually for it to pick up the

Re: wlan/ifconfig stopped working sometime between 5/25 and 6/3

Thanks, Andriy. Indeed, this patch fixed my issue. Hiro On Tue, 07 Jun 2016 15:54:36 +0300 "Andriy Voskoboinyk" wrote: > Tue, 07 Jun 2016 07:42:48 +0300 було написано Adrian Chadd > : > > Hi, > > the attached patch should fix this issue > (no idea if

Re: wlan/ifconfig stopped working sometime between 5/25 and 6/3

Tue, 07 Jun 2016 07:42:48 +0300 було написано Adrian Chadd : Hi, the attached patch should fix this issue (no idea if it can be fixed in a better way...) Hi, this is a recent change to the regulatory handling. I've emailed Andriy who wrote the code. :) Andriy, any

Re: wlan/ifconfig stopped working sometime between 5/25 and 6/3

Hi, this is a recent change to the regulatory handling. I've emailed Andriy who wrote the code. :) Andriy, any ideas? -adrian On 6 June 2016 at 20:15, Yoshihiro Ota wrote: > Hi, > > I started getting the following error when I tried to bring up wireless > connection

Re: WLAN hardware not recognized

Adrian Chadd wrote: > Right, you need to create the interface: > > ifconfig wlan0 create wlandev iwn0 > > then run wpa_spuplicant > > (or do it all in /etc/rc.conf .. :) That seems to work. There seems to be something configured wrong for wpa_supplicant but WLAN

Re: WLAN hardware not recognized

On 3/1/16, Carsten Kunze wrote: > Conrad Meyer wrote: > >> "[1] iwn0: mem 0xf7b0-0xf7b01fff >> irq 18 at device 0.0 on pci3" is fine; "module iwn already present!" >> is fine. >> >> What makes you say it isn't recognized or doesn't work? > >

Re: WLAN hardware not recognized

Conrad Meyer wrote: > "[1] iwn0: mem 0xf7b0-0xf7b01fff > irq 18 at device 0.0 on pci3" is fine; "module iwn already present!" > is fine. > > What makes you say it isn't recognized or doesn't work? ifconfig iwn0 says "interface iwn0 does not exist". Also starting

Re: Re: WLAN hardware not recognized

Right, you need to create the interface: ifconfig wlan0 create wlandev iwn0 then run wpa_spuplicant (or do it all in /etc/rc.conf .. :) -a On 1 March 2016 at 14:13, Carsten Kunze wrote: > Adrian Chadd wrote: > >> sysctl net.wlan.devices >>

Aw: Re: WLAN hardware not recognized

Adrian Chadd wrote: > sysctl net.wlan.devices > > iwn0 no longer shows up in ifconfig -a . > > > -a Ok, "sysctl -a|grep iwn" gives quite some output. Actually I tried to start wpa_supplicant, but WLAN didn't react. Then--just for testing--I wrote "ifconfig iwn0

Re: WLAN hardware not recognized

sysctl net.wlan.devices iwn0 no longer shows up in ifconfig -a . -a On 1 March 2016 at 13:42, Conrad Meyer wrote: > "[1] iwn0: mem 0xf7b0-0xf7b01fff > irq 18 at device 0.0 on pci3" is fine; "module iwn already present!" > is fine. > > What makes you say it isn't

Re: WLAN hardware not recognized

"[1] iwn0: mem 0xf7b0-0xf7b01fff irq 18 at device 0.0 on pci3" is fine; "module iwn already present!" is fine. What makes you say it isn't recognized or doesn't work? On Tue, Mar 1, 2016 at 1:01 PM, Carsten Kunze wrote: > Conrad Meyer wrote: > >>

Re: WLAN hardware not recognized

Conrad Meyer wrote: > kldload iwn6000fw, iwn6000g2afw, iwn6000g2bfw. This or edit loader.conf doesn't help, all these things had already been in the kernel. dmesg stays the same. ___ freebsd-current@freebsd.org mailing list

Re: WLAN hardware not recognized

kldload iwn6000fw, iwn6000g2afw, iwn6000g2bfw. On Tue, Mar 1, 2016 at 12:48 PM, Carsten Kunze wrote: > Larry Rosenman wrote: > >> Did you load the iwn firmware? > > How do I do this? > > I put "if_iwn_load="YES"" into /boot/loader.conf, now I get >

Re: WLAN hardware not recognized

On 2016-03-01 14:48, Carsten Kunze wrote: Larry Rosenman wrote: Did you load the iwn firmware? How do I do this? I put "if_iwn_load="YES"" into /boot/loader.conf, now I get "module iwn already present!" in dmesg... ___

Re: WLAN hardware not recognized

Larry Rosenman wrote: > Did you load the iwn firmware? How do I do this? I put "if_iwn_load="YES"" into /boot/loader.conf, now I get "module iwn already present!" in dmesg... ___ freebsd-current@freebsd.org mailing list

Re: Aw: Re: WLAN hardware not recognized

On 2016-03-01 12:23, Carsten Kunze wrote: Joe Nosay wrote: Is the card removable? If so, have you tried plugging in one that would have the driver already included with the base - so to speak - system? Have you tried the card in another computer/laptop? It is an

Aw: Re: WLAN hardware not recognized

Joe Nosay wrote: > Is the card removable? If so, have you tried plugging in one that would > have the driver already included with the base - so to speak - system? Have > you tried the card in another computer/laptop? It is an integrated card. Theoretical it is

Re: WLAN hardware not recognized

Is the card removable? If so, have you tried plugging in one that would have the driver already included with the base - so to speak - system? Have you tried the card in another computer/laptop? On Tue, Mar 1, 2016 at 10:47 AM, Carsten Kunze wrote: > Hello, > > the WLAN

Re: wlan/wpi are more broken than 3 weeks.

On Saturday 01 January 2011 19:47:21 you wrote: On Mon, Dec 27, 2010 at 02:05:25AM +0100, Bernhard Schmidt wrote: On Monday 27 December 2010 01:32:56 Steve Kargl wrote: On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote: [ .. ] If you can get debug output while the

Re: wlan/wpi are more broken than 3 weeks.

On Mon, Dec 27, 2010 at 02:05:25AM +0100, Bernhard Schmidt wrote: On Monday 27 December 2010 01:32:56 Steve Kargl wrote: On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote: How about providing the info I asked for last time? Now that you have build the necessary options into

Re: wlan/wpi are more broken than 3 weeks.

On 26/12/10 02:55 PM, Steve Kargl wrote: First reported here, http://lists.freebsd.org/pipermail/freebsd-current/2010-December/021664.html I now see a never ending spew in /var/log/messages of laptop:kargl[232] tail /var/log/messages Dec 26 07:41:12 laptop kernel: wlan0: link state changed

Re: wlan/wpi are more broken than 3 weeks.

On Sun, Dec 26, 2010 at 04:43:48PM -0500, Etienne Robillard wrote: On 26/12/10 02:55 PM, Steve Kargl wrote: First reported here, http://lists.freebsd.org/pipermail/freebsd-current/2010-December/021664.html I now see a never ending spew in /var/log/messages of laptop:kargl[232] tail

Re: wlan/wpi are more broken than 3 weeks.

On Sunday 26 December 2010 22:39:58 Steve Kargl wrote: On Sun, Dec 26, 2010 at 04:43:48PM -0500, Etienne Robillard wrote: On 26/12/10 02:55 PM, Steve Kargl wrote: First reported here, http://lists.freebsd.org/pipermail/freebsd-current/2010-December/021664 .html I now see a

Re: wlan/wpi are more broken than 3 weeks.

On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote: How about providing the info I asked for last time? Now that you have build the necessary options into the kernel you should be able to run with wlandebug 0x enabled. Perhaps, I got busy with real life work, and

Re: wlan/wpi are more broken than 3 weeks.

On Monday 27 December 2010 01:32:56 Steve Kargl wrote: On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote: How about providing the info I asked for last time? Now that you have build the necessary options into the kernel you should be able to run with wlandebug 0x

Re: wlan problem. auto change channel

Date: Thu, 02 Dec 2010 11:41:46 +0700 From: Veniamin Gvozdikov g.venia...@googlemail.com Sender: owner-freebsd-curr...@freebsd.org Hi everybody! I have problem with my access point with freebsd after update of 7.3 to 8.1. I can't connect to AP. AP has auto change channel (

Re: WLAN card not working anymore

In message: [EMAIL PROTECTED] Harti Brandt [EMAIL PROTECTED] writes: : my Avaya Wireless PC Card (actually seems to be a Lucent) stopped to : work in my laptop as I updated the kernel today. It now says pcic0: Card : type unrecognized by bridge is unsupported.. What does this mean and

Re: WLAN card not working anymore

On Thu, 3 Jul 2003, M. Warner Losh wrote: MWLIn message: [EMAIL PROTECTED] MWLHarti Brandt [EMAIL PROTECTED] writes: MWL: my Avaya Wireless PC Card (actually seems to be a Lucent) stopped to MWL: work in my laptop as I updated the kernel today. It now says pcic0: Card MWL: type

Re: WLAN card not working anymore

Hi. On Thu, Jul 03, 2003 at 01:39:19PM +0200, Harti Brandt wrote: Jul 3 09:18:29 harti kernel: wi0: Lucent Firmware: Station (7.52.1) Well, I'm still seeing problems with my Lucent Card on -CURRENT (there were postings here about that earlier, but Ican't provide details at the moment as I

Re: WLAN card not working anymore

On Thu, 3 Jul 2003, Oliver Brandmueller wrote: OBHi. OB OBOn Thu, Jul 03, 2003 at 01:39:19PM +0200, Harti Brandt wrote: OB Jul 3 09:18:29 harti kernel: wi0: Lucent Firmware: Station (7.52.1) OB OBWell, I'm still seeing problems with my Lucent Card on -CURRENT (there OBwere postings here about

Re: WLAN

At 12:25 PM +1030 2003/02/24, Daniel O'Connor wrote: 802.11g isn't a final standard yet either (note no WiFi logo on 11g stuff) WiFi waffled. There probably won't be any kind of a WiFi logo on 11g equipment. Or 11a, for that matter. They're too beholden to corporate interests, and I don't

Re: WLAN

In message: [EMAIL PROTECTED] Gerald Mixa [EMAIL PROTECTED] writes: : does anybody know wether FreeBSD supports PCMCIA cards for wireless : lan based on 802.11g (54MBit/s) standard? Nope. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the

Re: WLAN

On Mon, 2003-02-24 at 07:27, Gerald Mixa wrote: does anybody know wether FreeBSD supports PCMCIA cards for wireless lan based on 802.11g (54MBit/s) standard? Nope.. 802.11g isn't a final standard yet either (note no WiFi logo on 11g stuff) Personally I'd wait a bit until the standard is

Re: wlan device fails with latest CURRENT

In message: [EMAIL PROTECTED] Christian Brueffer [EMAIL PROTECTED] writes: : Hi, : : just installed DP2 on my IBM Thinkpad R32 and updated to the latest : -CURRENT. : My wlan device (Prism 2.5, internal, no pccard) fails at bootup: : : wi0: Intersil Prism2.5 mem 0xf800-0xf8000fff