Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> You're probably looking for this:
> https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html

Thanks, that looks like a very useful approach.

Will test that when I'm in the housing facility, and report back.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

[Johannes Lundberg]

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=
>> l I
>> manually run ifconfig wlan0 scan.
>> Again, this is with failover lagg.
> I use failover lagg too. I'm still at $JOB so no ethernet for my personal 
> FreeBSD laptop here, but that works as well, at home.
>
>> 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 network.
> Do you suspend/resume your laptop?
Not the last few months because iichid doesn't support it yet. I just
leave it on while going between work/home.
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

[Cy Schubert]

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, this is with failover lagg.

I use failover lagg too. I'm still at $JOB so no ethernet for my personal 
FreeBSD laptop here, but that works as well, at home.

>
> 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 network.

Do you suspend/resume your laptop?


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


>
>
> On Thu, Sep 19, 2019 at 18:25 Cy Schubert  wrote=
> :
>
> > 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 th=
> e
> > > > roaming and network preferences when wpa_supplicant is running is don=
> e
> > > > in wpa_supplicant. That's where you have to look. Ideally
> > > > wpa_supplicant would be triggering bgscan too periodically rather tha=
> n
> > > > only when the RSSI is low.
> > > >
> > > >
> > > >
> > > > -adrian
> > > >
> > > >
> > > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert  > > > > wrote:
> > > >
> > > > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> > > > mailto:adrian.ch...@gmail.com>> 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,
> > > > >>
> > > > >> 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.or=
> g
> > >,
> > > > >> >> 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 different
> > > > >network.
> > > > >> >>
> > > > >> >> I suffer from the dreaded "reason=3D0" when I move inside m=
> y
> > > > house:
> > > > >> >>
> > > > >> >>  > scan
> > > > >> >>  OK
> > > > >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> > > > >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> > > > >(SSID=3D'Palombia'
> > > > >> >> freq=3D2452 MHz)
> > > > >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:3d:a2:e9
> > reason
> > > =3D0
> > > > >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> > > > >> >>  <3>Trying to associate with 6c:3b:6b:ab:ce:d4
> > > > >(SSID=3D'Palombia'
> > > > >> >> freq=3D2412 MHz)
> > > > >> >>  <3>Associated with 6c:3b:6b:ab:ce:d4
> > > > >> >>
> > > > >> >> a2:e9 is the loudest AP here in my office, but my I have
> > been in
> > > > >the
> > > > >> >> other end of the house iwn consistently fails to associate
> > > > with it
> > > > >> >> and
> > > > >> >> and keeps picking the weaker AP in the far end.
> > > > >> >>
> > > > >> >> Eventually (hours!) it disconnects from the weaker ap, also
> > with
> > > > >> >> "reason=3D0" and gets it right:
> > > > >> >>
> > > > >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d=
> 4
> > > > >[GTK=3DCCMP]
> > > > >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:ab:ce:d4
> > reason
> > > =3D0
> > > > >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> > > > >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> > > > >(SSID=3D'Palombia'
> > > > >> >> freq=3D2452 MHz)
> > > > >> >>  <3>Associated with 6c:3b:6b:3d:a2:e9
> > > > >> >>  <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:=
> e9
> > > > >[PTK=3DCCMP
> > > > >> >> GTK=3DCCMP]
> > > > >> >>  <3>CTRL-EVENT-CONNECTED - Connection to
> > 6c:3b:6b:3d:a2:e9
> > > > >> completed
> > > > >> >> [id=3D3 id_str=3D]
> > > > >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e=
> 9
> > > > 

Re: wlan can't discover known networks after relocating

[Johannes Lundberg]

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 network.


On Thu, Sep 19, 2019 at 18:25 Cy Schubert  wrote:

> 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 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 bgscan too periodically rather than
> > > only when the RSSI is low.
> > >
> > >
> > >
> > > -adrian
> > >
> > >
> > > On Thu, 19 Sep 2019 at 15:04, Cy Schubert  > > > wrote:
> > >
> > > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> > > mailto:adrian.ch...@gmail.com>> 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,
> > > >>
> > > >> 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 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 different
> > > >network.
> > > >> >>
> > > >> >> I suffer from the dreaded "reason=0" when I move inside my
> > > house:
> > > >> >>
> > > >> >>  > scan
> > > >> >>  OK
> > > >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> > > >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> > > >(SSID='Palombia'
> > > >> >> freq=2452 MHz)
> > > >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9
> reason
> > =0
> > > >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> > > >> >>  <3>Trying to associate with 6c:3b:6b:ab:ce:d4
> > > >(SSID='Palombia'
> > > >> >> freq=2412 MHz)
> > > >> >>  <3>Associated with 6c:3b:6b:ab:ce:d4
> > > >> >>
> > > >> >> a2:e9 is the loudest AP here in my office, but my I have
> been in
> > > >the
> > > >> >> other end of the house iwn consistently fails to associate
> > > with it
> > > >> >> and
> > > >> >> and keeps picking the weaker AP in the far end.
> > > >> >>
> > > >> >> Eventually (hours!) it disconnects from the weaker ap, also
> with
> > > >> >> "reason=0" and gets it right:
> > > >> >>
> > > >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4
> > > >[GTK=CCMP]
> > > >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4
> reason
> > =0
> > > >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> > > >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> > > >(SSID='Palombia'
> > > >> >> freq=2452 MHz)
> > > >> >>  <3>Associated with 6c:3b:6b:3d:a2:e9
> > > >> >>  <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9
> > > >[PTK=CCMP
> > > >> >> GTK=CCMP]
> > > >> >>  <3>CTRL-EVENT-CONNECTED - Connection to
> 6c:3b:6b:3d:a2:e9
> > > >> completed
> > > >> >> [id=3 id_str=]
> > > >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9
> > > >[GTK=CCMP]
> > > >> >>
> > > >> >> And yes, working roaming would be nice too...
> > > >> >
> > > >> > I have the problem that when roaming networks become disabled
> > > >> >
> > > >> >   $ wpa_cli
> > > >> >   Selected interface 'wlan0'
> > > >> >
> > > >> >   Interactive mode
> > > >> >
> > > >> >   > list_networks
> > > >> >   network id / ssid / bssid / flags
> > > >> >   0   network1any [CURRENT]
> > > >> >   1   network2 any[DISABLED]
> > > >> >   2   network3 any[DISABLED]
> > > >> >   3   network4 any[DISABLED]
> > > >> >   4   network5 any[DISABLED]
> > > >> >   Selected interface 'wlan0'
> > > >> >
> > > >> >
> > >   

Re: wlan can't discover known networks after relocating

[Cy Schubert]

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 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 bgscan too periodically rather than
> > only when the RSSI is low.
> >
> >
> >
> > -adrian
> >
> >
> > On Thu, 19 Sep 2019 at 15:04, Cy Schubert  > > wrote:
> >
> > On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> > mailto:adrian.ch...@gmail.com>> 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,
> > >>
> > >> 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 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 different
> > >network.
> > >> >>
> > >> >> I suffer from the dreaded "reason=0" when I move inside my
> > house:
> > >> >>
> > >> >>      > scan
> > >> >>      OK
> > >> >>      <3>CTRL-EVENT-SCAN-RESULTS
> > >> >>      <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> > >(SSID='Palombia'
> > >> >> freq=2452 MHz)
> > >> >>      <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason
> =0
> > >> >>      <3>CTRL-EVENT-SCAN-RESULTS
> > >> >>      <3>Trying to associate with 6c:3b:6b:ab:ce:d4
> > >(SSID='Palombia'
> > >> >> freq=2412 MHz)
> > >> >>      <3>Associated with 6c:3b:6b:ab:ce:d4
> > >> >>
> > >> >> a2:e9 is the loudest AP here in my office, but my I have been in
> > >the
> > >> >> other end of the house iwn consistently fails to associate
> > with it
> > >> >> and
> > >> >> and keeps picking the weaker AP in the far end.
> > >> >>
> > >> >> Eventually (hours!) it disconnects from the weaker ap, also with
> > >> >> "reason=0" and gets it right:
> > >> >>
> > >> >>      <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4
> > >[GTK=CCMP]
> > >> >>      <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason
> =0
> > >> >>      <3>CTRL-EVENT-SCAN-RESULTS
> > >> >>      <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> > >(SSID='Palombia'
> > >> >> freq=2452 MHz)
> > >> >>      <3>Associated with 6c:3b:6b:3d:a2:e9
> > >> >>      <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9
> > >[PTK=CCMP
> > >> >> GTK=CCMP]
> > >> >>      <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9
> > >> completed
> > >> >> [id=3 id_str=]
> > >> >>      <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9
> > >[GTK=CCMP]
> > >> >>
> > >> >> And yes, working roaming would be nice too...
> > >> >
> > >> > I have the problem that when roaming networks become disabled
> > >> >
> > >> >       $ wpa_cli
> > >> >       Selected interface 'wlan0'
> > >> >
> > >> >       Interactive mode
> > >> >
> > >> >       > list_networks
> > >> >       network id / ssid / bssid / flags
> > >> >       0       network1        any     [CURRENT]
> > >> >       1       network2 any    [DISABLED]
> > >> >       2       network3 any    [DISABLED]
> > >> >       3       network4 any    [DISABLED]
> > >> >       4       network5 any    [DISABLED]
> > >> >       Selected interface 'wlan0'
> > >> >
> > >> >
> > >> > I address this by doing network_enable x in wpa_cli and it all
> > >comes
> > >> > back. I asked Adrian about this in the past, but it needs some
> > >> > debugging
> > >> > to pin down.
> > >>
> > >>
> > >> Is this iwm(4) as well in your case or another card?
> > >>
> > >> /bz
> > >> ___
> > >> freebsd-wirel...@freebsd.org
> >  mailing list
> > >> 

Re: wlan can't discover known networks after relocating

[Adrian Chadd]

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


On Thu, 19 Sep 2019 at 15:21, Johannes Lundberg  wrote:

>
> 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 look. Ideally wpa_supplicant would
> be triggering bgscan too periodically rather than only when the RSSI is low.
>
>
>
> -adrian
>
>
> On Thu, 19 Sep 2019 at 15:04, Cy Schubert  wrote:
>
>> On September 19, 2019 8:20:07 AM PDT, Adrian Chadd <
>> adrian.ch...@gmail.com> 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,
>> >>
>> >> 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>
>> <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 different
>> >network.
>> >> >>
>> >> >> I suffer from the dreaded "reason=0" when I move inside my house:
>> >> >>
>> >> >>  > scan
>> >> >>  OK
>> >> >>  <3>CTRL-EVENT-SCAN-RESULTS
>> >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
>> >(SSID='Palombia'
>> >> >> freq=2452 MHz)
>> >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0
>> >> >>  <3>CTRL-EVENT-SCAN-RESULTS
>> >> >>  <3>Trying to associate with 6c:3b:6b:ab:ce:d4
>> >(SSID='Palombia'
>> >> >> freq=2412 MHz)
>> >> >>  <3>Associated with 6c:3b:6b:ab:ce:d4
>> >> >>
>> >> >> a2:e9 is the loudest AP here in my office, but my I have been in
>> >the
>> >> >> other end of the house iwn consistently fails to associate with it
>> >> >> and
>> >> >> and keeps picking the weaker AP in the far end.
>> >> >>
>> >> >> Eventually (hours!) it disconnects from the weaker ap, also with
>> >> >> "reason=0" and gets it right:
>> >> >>
>> >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4
>> >[GTK=CCMP]
>> >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0
>> >> >>  <3>CTRL-EVENT-SCAN-RESULTS
>> >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
>> >(SSID='Palombia'
>> >> >> freq=2452 MHz)
>> >> >>  <3>Associated with 6c:3b:6b:3d:a2:e9
>> >> >>  <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9
>> >[PTK=CCMP
>> >> >> GTK=CCMP]
>> >> >>  <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9
>> >> completed
>> >> >> [id=3 id_str=]
>> >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9
>> >[GTK=CCMP]
>> >> >>
>> >> >> And yes, working roaming would be nice too...
>> >> >
>> >> > I have the problem that when roaming networks become disabled
>> >> >
>> >> >   $ wpa_cli
>> >> >   Selected interface 'wlan0'
>> >> >
>> >> >   Interactive mode
>> >> >
>> >> >   > list_networks
>> >> >   network id / ssid / bssid / flags
>> >> >   0   network1any [CURRENT]
>> >> >   1   network2 any[DISABLED]
>> >> >   2   network3 any[DISABLED]
>> >> >   3   network4 any[DISABLED]
>> >> >   4   network5 any[DISABLED]
>> >> >   Selected interface 'wlan0'
>> >> >
>> >> >
>> >> > I address this by doing network_enable x in wpa_cli and it all
>> >comes
>> >> > back. I asked Adrian about this in the past, but it needs some
>> >> > debugging
>> >> > to pin down.
>> >>
>> >>
>> >> Is this iwm(4) as well in your case or another card?
>> >>
>> >> /bz
>> >> ___
>> >> freebsd-wirel...@freebsd.org mailing list
>> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>> >> To unsubscribe, send any mail to
>> >"freebsd-wireless-unsubscr...@freebsd.org
>> >> "
>> >>
>> >___
>> >freebsd-current@freebsd.org mailing list
>> >https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> >To unsubscribe, send any mail to
>> >"freebsd-current-unsubscr...@freebsd.org"
>>
>> With wpa_supplicant running roaming is set to manual. Bgscan should be
>> enabled.
>>
>> At home we have two n (and 2 g) wifi networks. When powering 

Re: wlan can't discover known networks after relocating

[Johannes Lundberg]

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 look. Ideally
> wpa_supplicant would be triggering bgscan too periodically rather than
> only when the RSSI is low.
>
>
>
> -adrian
>
>
> On Thu, 19 Sep 2019 at 15:04, Cy Schubert  > wrote:
>
> On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> mailto:adrian.ch...@gmail.com>> 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,
> >>
> >> 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 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 different
> >network.
> >> >>
> >> >> I suffer from the dreaded "reason=0" when I move inside my
> house:
> >> >>
> >> >>      > scan
> >> >>      OK
> >> >>      <3>CTRL-EVENT-SCAN-RESULTS
> >> >>      <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> >(SSID='Palombia'
> >> >> freq=2452 MHz)
> >> >>      <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0
> >> >>      <3>CTRL-EVENT-SCAN-RESULTS
> >> >>      <3>Trying to associate with 6c:3b:6b:ab:ce:d4
> >(SSID='Palombia'
> >> >> freq=2412 MHz)
> >> >>      <3>Associated with 6c:3b:6b:ab:ce:d4
> >> >>
> >> >> a2:e9 is the loudest AP here in my office, but my I have been in
> >the
> >> >> other end of the house iwn consistently fails to associate
> with it
> >> >> and
> >> >> and keeps picking the weaker AP in the far end.
> >> >>
> >> >> Eventually (hours!) it disconnects from the weaker ap, also with
> >> >> "reason=0" and gets it right:
> >> >>
> >> >>      <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4
> >[GTK=CCMP]
> >> >>      <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0
> >> >>      <3>CTRL-EVENT-SCAN-RESULTS
> >> >>      <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> >(SSID='Palombia'
> >> >> freq=2452 MHz)
> >> >>      <3>Associated with 6c:3b:6b:3d:a2:e9
> >> >>      <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9
> >[PTK=CCMP
> >> >> GTK=CCMP]
> >> >>      <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9
> >> completed
> >> >> [id=3 id_str=]
> >> >>      <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9
> >[GTK=CCMP]
> >> >>
> >> >> And yes, working roaming would be nice too...
> >> >
> >> > I have the problem that when roaming networks become disabled
> >> >
> >> >       $ wpa_cli
> >> >       Selected interface 'wlan0'
> >> >
> >> >       Interactive mode
> >> >
> >> >       > list_networks
> >> >       network id / ssid / bssid / flags
> >> >       0       network1        any     [CURRENT]
> >> >       1       network2 any    [DISABLED]
> >> >       2       network3 any    [DISABLED]
> >> >       3       network4 any    [DISABLED]
> >> >       4       network5 any    [DISABLED]
> >> >       Selected interface 'wlan0'
> >> >
> >> >
> >> > I address this by doing network_enable x in wpa_cli and it all
> >comes
> >> > back. I asked Adrian about this in the past, but it needs some
> >> > debugging
> >> > to pin down.
> >>
> >>
> >> Is this iwm(4) as well in your case or another card?
> >>
> >> /bz
> >> ___
> >> freebsd-wirel...@freebsd.org
>  mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> To unsubscribe, send any mail to
> >"freebsd-wireless-unsubscr...@freebsd.org
> 
> >> "
> >>
> >___
> >freebsd-current@freebsd.org 
> mailing list
> >https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >To unsubscribe, send any mail to
> 

Re: wlan can't discover known networks after relocating

[Adrian Chadd]

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 bgscan too periodically rather than only when the RSSI is low.



-adrian


On Thu, 19 Sep 2019 at 15:04, Cy Schubert  wrote:

> 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,
> >>
> >> 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 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 different
> >network.
> >> >>
> >> >> I suffer from the dreaded "reason=0" when I move inside my house:
> >> >>
> >> >>  > scan
> >> >>  OK
> >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> >(SSID='Palombia'
> >> >> freq=2452 MHz)
> >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0
> >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> >> >>  <3>Trying to associate with 6c:3b:6b:ab:ce:d4
> >(SSID='Palombia'
> >> >> freq=2412 MHz)
> >> >>  <3>Associated with 6c:3b:6b:ab:ce:d4
> >> >>
> >> >> a2:e9 is the loudest AP here in my office, but my I have been in
> >the
> >> >> other end of the house iwn consistently fails to associate with it
> >> >> and
> >> >> and keeps picking the weaker AP in the far end.
> >> >>
> >> >> Eventually (hours!) it disconnects from the weaker ap, also with
> >> >> "reason=0" and gets it right:
> >> >>
> >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4
> >[GTK=CCMP]
> >> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0
> >> >>  <3>CTRL-EVENT-SCAN-RESULTS
> >> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
> >(SSID='Palombia'
> >> >> freq=2452 MHz)
> >> >>  <3>Associated with 6c:3b:6b:3d:a2:e9
> >> >>  <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9
> >[PTK=CCMP
> >> >> GTK=CCMP]
> >> >>  <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9
> >> completed
> >> >> [id=3 id_str=]
> >> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9
> >[GTK=CCMP]
> >> >>
> >> >> And yes, working roaming would be nice too...
> >> >
> >> > I have the problem that when roaming networks become disabled
> >> >
> >> >   $ wpa_cli
> >> >   Selected interface 'wlan0'
> >> >
> >> >   Interactive mode
> >> >
> >> >   > list_networks
> >> >   network id / ssid / bssid / flags
> >> >   0   network1any [CURRENT]
> >> >   1   network2 any[DISABLED]
> >> >   2   network3 any[DISABLED]
> >> >   3   network4 any[DISABLED]
> >> >   4   network5 any[DISABLED]
> >> >   Selected interface 'wlan0'
> >> >
> >> >
> >> > I address this by doing network_enable x in wpa_cli and it all
> >comes
> >> > back. I asked Adrian about this in the past, but it needs some
> >> > debugging
> >> > to pin down.
> >>
> >>
> >> Is this iwm(4) as well in your case or another card?
> >>
> >> /bz
> >> ___
> >> freebsd-wirel...@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> To unsubscribe, send any mail to
> >"freebsd-wireless-unsubscr...@freebsd.org
> >> "
> >>
> >___
> >freebsd-current@freebsd.org mailing list
> >https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >To unsubscribe, send any mail to
> >"freebsd-current-unsubscr...@freebsd.org"
>
> With wpa_supplicant running roaming is set to manual. Bgscan should be
> enabled.
>
> At home we have two n (and 2 g) wifi networks. When powering off one ap it
> connects to the other (in addition to using lagg to failover from ethernet
> to wifi and back).
>
> Your wpa_supplicant should contain each ssid you intend to use. A wildcard
> can be used for open networks.
>
> It's a while since I've tested this functionality but I can test again
> when I get home tonight.
>
>
> --
> Pardon the typos and autocorrect, small keyboard in use.
> Cheers,
> Cy Schubert 
> FreeBSD UNIX:  Web: http://www.FreeBSD.org
>
> The need of the many outweighs the greed of the few.
>
___
freebsd-current@freebsd.org mailing list

Re: wlan can't discover known networks after relocating

[Cy Schubert]

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,
>>
>> 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 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 different
>network.
>> >>
>> >> I suffer from the dreaded "reason=0" when I move inside my house:
>> >>
>> >>  > scan
>> >>  OK
>> >>  <3>CTRL-EVENT-SCAN-RESULTS
>> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
>(SSID='Palombia'
>> >> freq=2452 MHz)
>> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0
>> >>  <3>CTRL-EVENT-SCAN-RESULTS
>> >>  <3>Trying to associate with 6c:3b:6b:ab:ce:d4
>(SSID='Palombia'
>> >> freq=2412 MHz)
>> >>  <3>Associated with 6c:3b:6b:ab:ce:d4
>> >>
>> >> a2:e9 is the loudest AP here in my office, but my I have been in
>the
>> >> other end of the house iwn consistently fails to associate with it
>> >> and
>> >> and keeps picking the weaker AP in the far end.
>> >>
>> >> Eventually (hours!) it disconnects from the weaker ap, also with
>> >> "reason=0" and gets it right:
>> >>
>> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4
>[GTK=CCMP]
>> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0
>> >>  <3>CTRL-EVENT-SCAN-RESULTS
>> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9
>(SSID='Palombia'
>> >> freq=2452 MHz)
>> >>  <3>Associated with 6c:3b:6b:3d:a2:e9
>> >>  <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9
>[PTK=CCMP
>> >> GTK=CCMP]
>> >>  <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9
>> completed
>> >> [id=3 id_str=]
>> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9
>[GTK=CCMP]
>> >>
>> >> And yes, working roaming would be nice too...
>> >
>> > I have the problem that when roaming networks become disabled
>> >
>> >   $ wpa_cli
>> >   Selected interface 'wlan0'
>> >
>> >   Interactive mode
>> >
>> >   > list_networks
>> >   network id / ssid / bssid / flags
>> >   0   network1any [CURRENT]
>> >   1   network2 any[DISABLED]
>> >   2   network3 any[DISABLED]
>> >   3   network4 any[DISABLED]
>> >   4   network5 any[DISABLED]
>> >   Selected interface 'wlan0'
>> >
>> >
>> > I address this by doing network_enable x in wpa_cli and it all
>comes
>> > back. I asked Adrian about this in the past, but it needs some
>> > debugging
>> > to pin down.
>>
>>
>> Is this iwm(4) as well in your case or another card?
>>
>> /bz
>> ___
>> freebsd-wirel...@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>> To unsubscribe, send any mail to
>"freebsd-wireless-unsubscr...@freebsd.org
>> "
>>
>___
>freebsd-current@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to
>"freebsd-current-unsubscr...@freebsd.org"

With wpa_supplicant running roaming is set to manual. Bgscan should be enabled. 
 

At home we have two n (and 2 g) wifi networks. When powering off one ap it 
connects to the other (in addition to using lagg to failover from ethernet to 
wifi and back).

Your wpa_supplicant should contain each ssid you intend to use. A wildcard can 
be used for open networks.

It's a while since I've tested this functionality but I can test again when I 
get home tonight. 


-- 
Pardon the typos and autocorrect, small keyboard in use.
Cheers,
Cy Schubert 
FreeBSD UNIX:  Web: http://www.FreeBSD.org

The need of the many outweighs the greed of the few.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Freddie Cash]

On Thu, Sep 19, 2019 at 12:01 PM Andreas Nilsson  wrote:

> Seems like more of a bios enumeration issue. You should be able to set a
> boot order better suited for your setup there. And if that does not work,
> just move the sata cables around seems like the most straight forward
> solution.
>
> Although I think I've heard it is bad practice to use raw devices for zfs,
> especially if need to replace a drive, which day happens to be a different
> revision, with a few fewer blocks available. Then you will not be able to
> do the replace.
>
>
Back in the good ol' days of ZFS versions where everyone was compatible
with Solaris, this was an issue.  However, the ondisk format (or ZFS label
setup?) was changed to leave 1 MB of free space at the end of the drive to
allow for this.

With ZFSv6, for example, if you used a raw device for the vdev, and that
disk died, and the replacement was 1 sector smaller, the replace would
fail.  Today, with OpenZFS, the replace would succeed.

There's also 1 MB or so of reserved space in the pool such that if you fill
the pool "100%", you can still do a "zfs destroy" of a dataset to free up
space.  Previously, this would fail, as you need space in the pool to write
the metadata for the destroy before doing the destroy.

ZFS of today is much more resilient to these kinds of niggles that bit us
all, back in the day.  :D

-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Another X server start failure

[Clay Daniels Jr.]

Assuming you are running 13.0 Current, and already put the entry in
/etc/rc.conf:
kld_list="amdgpu"   #Yes, no path needed, just "amdgpu"

Having done that, try this in /boot/loader.conf

hw.syscons.disable=1  # then reboot

I'm not the expert here, but the cause is what I might call a "framebuffer
problem" with AMD graphics and drm-kmod. There were changes in August to
drm-current-kmod that  took me a while to overcome myself, but thanks to
the folks on this list, I'm back online with 13.0 Current.

Good luck,
Clay

On Thu, Sep 19, 2019 at 6:00 AM  wrote:

> Having a Raden 240 (sometimes 250) and an older AMDGPU. The older card is
> deactivated in BIOS but it is been found by the X -configure problem. X
> server
> did start one time with -config /root/xorg.conf.new, copied to /etc/X11/
> xorg.conf, never got back any "blank black grafic" screen. Rebuilt new
> world
> and the kern with WITNESS option on and option LOCK_PROFILING. Using llvm-
> devel is useless in that case, if it doesn't with the 8.0.X.
>
> Can't enter framebuffer mode, tells /var/log/x11_*.log,  no VESA, no xfcb.
> sddm tells: xauth: bad add command line, bad delete command line, bad add
> commandline. It used to work with even X -configure fatal error and sddm,
> so
> what to xrite in xauth; normally sddm autoconfigs.
>
> I guess it's the recognization from both cards, what is the option to
> really
> and finally deactivate this on-board card on an ASUS PRIME 350 board (I
> just
> mean NOT to cut the part of the board where grafics situatiated with a
> laser-
> cutter :-) )? This one has never been used as it been too old for good 3D-
> Gaming what has been a topic a year ago - not for me, but for a user.
>
> What's the state of art for 3D-virutal-glasses and gloves? I guess the
> same as
> with the AI! I guess freeBSD has other functions to do than beeing a
> desktop
> OS!
>
> Thx for help in advance,
> Yours, Miranda
>
>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Daniel Engberg]

Hi Kurt!

You're probably looking for this: 
https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html


Best regards,
Daniel
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Toomas Soome]

> On 19 Sep 2019, at 21:48, Kurt Jaeger  wrote:
> 
> Hi!
> 
 Also the question is, what you mean with ???system looses track
> 
>>> I interpret the hang during boot as 'it looses track'. So I guess
>>> it tries to read the kernel from the wrong drives.
> 
>> no, loader does probe disks to see which devices make up the pool and hung 
>> system is not about reading the kernel from wrong place.
> 
>> I bet it is BIOS system?
> 
> If you mean: no UEFI boot ? Yes, it boots via BIOS, not UEFI.
> 
>> Since the raidz seems to be created partitionless, what version
>> of freebsd are you using?
> 
> FreeBSD 12.0p10, amd64.
> 
>> BIOS up to date?
> 
> The board is an X10SRi-F. dmidecode reports BIOS 3.1, supermicro
> has 3.1c, but the release notes do not mention things like that
> (or at least I don't understand them that way).
> 
> https://www.supermicro.com/en/products/motherboard/X10SRi-F
> 
>> can you test pool visibility in loader with latest current
>> usb/cd start - like press esc in menu and check lsdev -v
>> (assuming you get to menu) ? the same with uefi?
> 
> I will test this when I'm at the facility. Will take some time.
> 

Those data disks are 10TB 512e, I can not recall if loader in 12.0p10 does 
ignore partitionless disks in pools or not, if the bios is buggy about large 
disks, that does explain the hung system… in that case, the loader in current 
should be fine.

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Andreas Nilsson]

On Thu, Sep 19, 2019, 20:56 Michael Gmelin  wrote:

>
>
> On 19. Sep 2019, at 19:15, Kurt Jaeger  wrote:
>
> >>> I've made a few more details available here:
> >
> >>> https://people.freebsd.org/~pi/host/gpart.txt
> >
> >> What about gpart output of the pool drives?
> >
> > No gpart on the bck pool, raw drives.
> >
> >> In general you would create zpools using gptids or gpt labels, not the
> devices, so you???re independent of device numbering. The boot loader
> should only be installed on drives that contain the boot pool (maybe you
> have old boot loaders on data drives?).
> >
> > I think not, because they are used as raw drives.
> >
> > Maybe that decision was an error in hindsight.
>
> Yeah, it’s not optimal that way. I made it a habit to use GPT on all pools
> and label partitions with the enclosure slots they’re in (makes it easier
> to not make mistakes in case of emergency). I also leave a bit of space at
> the beginning and end of the drive (allows adding in a boot partition later
> or more flexibility when replacing the drive).
>
> Anyway, I’m curious what the exact problem will turn out to be.
>
> Cheers,
> Michael
>
> >
> > --
> > p...@opsec.eu+49 171 3101372One year to
> go !
>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>

Seems like more of a bios enumeration issue. You should be able to set a
boot order better suited for your setup there. And if that does not work,
just move the sata cables around seems like the most straight forward
solution.

Although I think I've heard it is bad practice to use raw devices for zfs,
especially if need to replace a drive, which day happens to be a different
revision, with a few fewer blocks available. Then you will not be able to
do the replace.

Best regards
Andreas

>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Michael Gmelin]

On 19. Sep 2019, at 19:15, Kurt Jaeger  wrote:

>>> I've made a few more details available here:
> 
>>> https://people.freebsd.org/~pi/host/gpart.txt
> 
>> What about gpart output of the pool drives?
> 
> No gpart on the bck pool, raw drives.
> 
>> In general you would create zpools using gptids or gpt labels, not the 
>> devices, so you???re independent of device numbering. The boot loader should 
>> only be installed on drives that contain the boot pool (maybe you have old 
>> boot loaders on data drives?).
> 
> I think not, because they are used as raw drives.
> 
> Maybe that decision was an error in hindsight.

Yeah, it’s not optimal that way. I made it a habit to use GPT on all pools and 
label partitions with the enclosure slots they’re in (makes it easier to not 
make mistakes in case of emergency). I also leave a bit of space at the 
beginning and end of the drive (allows adding in a boot partition later or more 
flexibility when replacing the drive).

Anyway, I’m curious what the exact problem will turn out to be.

Cheers,
Michael

> 
> -- 
> p...@opsec.eu+49 171 3101372One year to go !

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> >> Also the question is, what you mean with ???system looses track

> > I interpret the hang during boot as 'it looses track'. So I guess
> > it tries to read the kernel from the wrong drives.

> no, loader does probe disks to see which devices make up the pool and hung 
> system is not about reading the kernel from wrong place.

> I bet it is BIOS system?

If you mean: no UEFI boot ? Yes, it boots via BIOS, not UEFI.

> Since the raidz seems to be created partitionless, what version
> of freebsd are you using?

FreeBSD 12.0p10, amd64.

> BIOS up to date?

The board is an X10SRi-F. dmidecode reports BIOS 3.1, supermicro
has 3.1c, but the release notes do not mention things like that
(or at least I don't understand them that way).

https://www.supermicro.com/en/products/motherboard/X10SRi-F

> can you test pool visibility in loader with latest current
> usb/cd start - like press esc in menu and check lsdev -v
> (assuming you get to menu) ? the same with uefi?

I will test this when I'm at the facility. Will take some time.

Thanks for the pointers!

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

> > I've made a few more details available here:

> > https://people.freebsd.org/~pi/host/gpart.txt

> What about gpart output of the pool drives?

No gpart on the bck pool, raw drives.

> In general you would create zpools using gptids or gpt labels, not the 
> devices, so you???re independent of device numbering. The boot loader should 
> only be installed on drives that contain the boot pool (maybe you have old 
> boot loaders on data drives?).

I think not, because they are used as raw drives.

Maybe that decision was an error in hindsight.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Firefox – GtkFileChooserNative – file selection dialogues

[Graham Perrin]

Firefox does not use xdg-desktop-portal for file selection dialogs


> This patch makes Firefox's GTK3 platform support use
> GtkFileChooserNative when available. GtkFileChooserNative
> transparently uses the desktop portals interface, which
> enables Firefox to use native Qt file dialogs on KDE, or
> sandboxed file dialogs in Flatpak.

– RESOLVED FIXED, mozilla64

Can I benefit from this patch on FreeBSD?

(What am I missing?)

TIA

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Guido Falsi]

On 19/09/19 18:54, Freddie Cash wrote:
> On Thu, Sep 19, 2019 at 9:47 AM Guido Falsi  > wrote:
> 
> On 19/09/19 18:04, Michael Gmelin wrote:
> >
> > What about gpart output of the pool drives?
> >
> > In general you would create zpools using gptids or gpt labels, not
> the devices, so you’re independent of device numbering. The boot
> loader should only be installed on drives that contain the boot pool
> (maybe you have old boot loaders on data drives?).
> >
> 
> Actually the installer will at least some times use the adaX device to
> create ZFS pools. At least it did for me when I recently rebuilt a
> machine after a (multiple) disk crash.
> 
> So it could not be Kurt fault if he has a pool with adaX devices in it.
> 
> I installed the system on one disk and the installed used adaX to create
> the pool. I added the second disk to the mirror a few days later.
> 
> Now I have:
> 
>   pool: zroot
>  state: ONLINE
>   scan: resilvered 24.6G in 0 days 00:09:41 with 0 errors on Tue Sep  3
> 16:10:08 2019
> config:
> 
>         NAME          STATE     READ WRITE CKSUM
>         zroot         ONLINE       0     0     0
>           mirror-0    ONLINE       0     0     0
>             ada0p4    ONLINE       0     0     0
>             gpt/zfs1  ONLINE       0     0     0
> 
> errors: No known data errors
> 
> Now, in the case of a mirror (or a zraid) this could be fixed by
> detaching adaX devices and reattaching them using the label. Disvantage
> is the cluster will need to resilver, causing some degraded time and
> extra disk load.
> 
> 
> Boot off a LiveCD/USB stick.  Export the pool.  Import the pool with -d
> /dev/gpt and it will use the GPT labels instead.  Reboot into the
> system, and it should continue to use the GPT labels.  No resilvering
> required. 

Good suggestion. I did not think about it. I'll try that once I can
reboot the machine.

-- 
Guido Falsi 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Gary Jennejohn]

On Thu, 19 Sep 2019 18:04:54 +0200
Michael Gmelin  wrote:

> > On 19. Sep 2019, at 17:57, Kurt Jaeger  wrote:
> > 
> > Hi!
> >   
> >>> We have a system with 10 SATA disks. 2 disks are for the system,
> >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup 
> >>> purposes:
> >>> 
> >>> bck72.8T  38.7T  34.1T- - 1%53%  1.00x  
> >>> ONLINE  -  
> >   
> >>> The problem is that if all 10 disks are connected, the system
> >>> looses track from where it should boot and fails to boot (serial boot 
> >>> log):  
> >   
> >> Why this order does change?  One would expect disks 0 and 1 to be OS disks 
> >> and the rest for data???  
> > 
> > 0+1 are 2.5", and the initial setup was:
> > - we installed system disks as zroot 
> > - shipped the box to the housing facility
> > - booted and added the drives
> > 
> > At that time we did not do additional tests about the disk/boot sequence
> > etc.
> >   
> >> Also the question is, what you mean with ???system looses track  
> > 
> > I interpret the hang during boot as 'it looses track'. So I guess
> > it tries to read the kernel from the wrong drives.
> >   
> >> disk4 becomes adaX? why it matters, are you using ufs on boot disks?  
> > 
> > No, zpool only.
> > 
> > I've made a few more details available here:
> > 
> > https://people.freebsd.org/~pi/host/dmesg.txt
> > https://people.freebsd.org/~pi/host/devlist.txt
> > https://people.freebsd.org/~pi/host/gpart.txt
> > https://people.freebsd.org/~pi/host/pciconf.txt
> > https://people.freebsd.org/~pi/host/zpool.txt  
> 
> What about gpart output of the pool drives?
> 
> In general you would create zpools using gptids or gpt labels,
> not the devices, so you___re independent of device numbering. 
> The boot loader should only be installed on drives that contain
> the boot pool (maybe you have old boot loaders on data
> drives?).
> 

Maybe the cam(4) hint settings could help in your case.

-- 
Gary Jennejohn
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Freddie Cash]

On Thu, Sep 19, 2019 at 9:47 AM Guido Falsi  wrote:

> On 19/09/19 18:04, Michael Gmelin wrote:
> >
> > What about gpart output of the pool drives?
> >
> > In general you would create zpools using gptids or gpt labels, not the
> devices, so you’re independent of device numbering. The boot loader should
> only be installed on drives that contain the boot pool (maybe you have old
> boot loaders on data drives?).
> >
>
> Actually the installer will at least some times use the adaX device to
> create ZFS pools. At least it did for me when I recently rebuilt a
> machine after a (multiple) disk crash.
>
> So it could not be Kurt fault if he has a pool with adaX devices in it.
>
> I installed the system on one disk and the installed used adaX to create
> the pool. I added the second disk to the mirror a few days later.
>
> Now I have:
>
>   pool: zroot
>  state: ONLINE
>   scan: resilvered 24.6G in 0 days 00:09:41 with 0 errors on Tue Sep  3
> 16:10:08 2019
> config:
>
> NAME  STATE READ WRITE CKSUM
> zroot ONLINE   0 0 0
>   mirror-0ONLINE   0 0 0
> ada0p4ONLINE   0 0 0
> gpt/zfs1  ONLINE   0 0 0
>
> errors: No known data errors
>
> Now, in the case of a mirror (or a zraid) this could be fixed by
> detaching adaX devices and reattaching them using the label. Disvantage
> is the cluster will need to resilver, causing some degraded time and
> extra disk load.
>

Boot off a LiveCD/USB stick.  Export the pool.  Import the pool with -d
/dev/gpt and it will use the GPT labels instead.  Reboot into the system,
and it should continue to use the GPT labels.  No resilvering required.

-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Guido Falsi]

On 19/09/19 18:04, Michael Gmelin wrote:
> 
> What about gpart output of the pool drives?
> 
> In general you would create zpools using gptids or gpt labels, not the 
> devices, so you’re independent of device numbering. The boot loader should 
> only be installed on drives that contain the boot pool (maybe you have old 
> boot loaders on data drives?).
> 

Actually the installer will at least some times use the adaX device to
create ZFS pools. At least it did for me when I recently rebuilt a
machine after a (multiple) disk crash.

So it could not be Kurt fault if he has a pool with adaX devices in it.

I installed the system on one disk and the installed used adaX to create
the pool. I added the second disk to the mirror a few days later.

Now I have:

  pool: zroot
 state: ONLINE
  scan: resilvered 24.6G in 0 days 00:09:41 with 0 errors on Tue Sep  3
16:10:08 2019
config:

NAME  STATE READ WRITE CKSUM
zroot ONLINE   0 0 0
  mirror-0ONLINE   0 0 0
ada0p4ONLINE   0 0 0
gpt/zfs1  ONLINE   0 0 0

errors: No known data errors

Now, in the case of a mirror (or a zraid) this could be fixed by
detaching adaX devices and reattaching them using the label. Disvantage
is the cluster will need to resilver, causing some degraded time and
extra disk load.

-- 
Guido Falsi 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Toomas Soome]

> On 19 Sep 2019, at 18:57, Kurt Jaeger  wrote:
> 
> Hi!
> 
>>> We have a system with 10 SATA disks. 2 disks are for the system,
>>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:
>>> 
>>> bck72.8T  38.7T  34.1T- - 1%53%  1.00x  ONLINE  
>>> -
> 
>>> The problem is that if all 10 disks are connected, the system
>>> looses track from where it should boot and fails to boot (serial boot log):
> 
>> Why this order does change?  One would expect disks 0 and 1 to be OS disks 
>> and the rest for data???
> 
> 0+1 are 2.5", and the initial setup was:
> - we installed system disks as zroot 
> - shipped the box to the housing facility
> - booted and added the drives
> 
> At that time we did not do additional tests about the disk/boot sequence
> etc.
> 
>> Also the question is, what you mean with ???system looses track
> 
> I interpret the hang during boot as 'it looses track'. So I guess
> it tries to read the kernel from the wrong drives.


no, loader does probe disks to see which devices make up the pool and hung 
system is not about reading the kernel from wrong place.

I bet it is BIOS system? Since the raidz seems to be created partitionless, 
what version of freebsd are you using? BIOS up to date? can you test pool 
visibility in loader with  latest current usb/cd start - like press esc in menu 
and check lasdev -v (assuming you get to menu)… the same with uefi?

rgds,
toomas


> 
>> disk4 becomes adaX? why it matters, are you using ufs on boot disks?
> 
> No, zpool only.
> 
> I've made a few more details available here:
> 
> https://people.freebsd.org/~pi/host/dmesg.txt
> https://people.freebsd.org/~pi/host/devlist.txt
> https://people.freebsd.org/~pi/host/gpart.txt
> https://people.freebsd.org/~pi/host/pciconf.txt
> https://people.freebsd.org/~pi/host/zpool.txt
> 
> -- 
> p...@opsec.eu+49 171 3101372One year to go !
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Michael Gmelin]

> On 19. Sep 2019, at 17:57, Kurt Jaeger  wrote:
> 
> Hi!
> 
>>> We have a system with 10 SATA disks. 2 disks are for the system,
>>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:
>>> 
>>> bck72.8T  38.7T  34.1T- - 1%53%  1.00x  ONLINE  
>>> -
> 
>>> The problem is that if all 10 disks are connected, the system
>>> looses track from where it should boot and fails to boot (serial boot log):
> 
>> Why this order does change?  One would expect disks 0 and 1 to be OS disks 
>> and the rest for data???
> 
> 0+1 are 2.5", and the initial setup was:
> - we installed system disks as zroot 
> - shipped the box to the housing facility
> - booted and added the drives
> 
> At that time we did not do additional tests about the disk/boot sequence
> etc.
> 
>> Also the question is, what you mean with ???system looses track
> 
> I interpret the hang during boot as 'it looses track'. So I guess
> it tries to read the kernel from the wrong drives.
> 
>> disk4 becomes adaX? why it matters, are you using ufs on boot disks?
> 
> No, zpool only.
> 
> I've made a few more details available here:
> 
> https://people.freebsd.org/~pi/host/dmesg.txt
> https://people.freebsd.org/~pi/host/devlist.txt
> https://people.freebsd.org/~pi/host/gpart.txt
> https://people.freebsd.org/~pi/host/pciconf.txt
> https://people.freebsd.org/~pi/host/zpool.txt

What about gpart output of the pool drives?

In general you would create zpools using gptids or gpt labels, not the devices, 
so you’re independent of device numbering. The boot loader should only be 
installed on drives that contain the boot pool (maybe you have old boot loaders 
on data drives?).

-m


> -- 
> p...@opsec.eu+49 171 3101372One year to go !
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

> > We have a system with 10 SATA disks. 2 disks are for the system,
> > 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:
> > 
> > bck72.8T  38.7T  34.1T- - 1%53%  1.00x  ONLINE  
> > -

> > The problem is that if all 10 disks are connected, the system
> > looses track from where it should boot and fails to boot (serial boot log):

> Why this order does change?  One would expect disks 0 and 1 to be OS disks 
> and the rest for data???

0+1 are 2.5", and the initial setup was:
- we installed system disks as zroot 
- shipped the box to the housing facility
- booted and added the drives

At that time we did not do additional tests about the disk/boot sequence
etc.

> Also the question is, what you mean with ???system looses track

I interpret the hang during boot as 'it looses track'. So I guess
it tries to read the kernel from the wrong drives.

> disk4 becomes adaX? why it matters, are you using ufs on boot disks?

No, zpool only.

I've made a few more details available here:

https://people.freebsd.org/~pi/host/dmesg.txt
https://people.freebsd.org/~pi/host/devlist.txt
https://people.freebsd.org/~pi/host/gpart.txt
https://people.freebsd.org/~pi/host/pciconf.txt
https://people.freebsd.org/~pi/host/zpool.txt

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

[Adrian Chadd]

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, 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 reconnect automatically and I
> >>> have
> >>> to do wlan0 scan manually for it to pick up the different network.
> >>
> >> I suffer from the dreaded "reason=0" when I move inside my house:
> >>
> >>  > scan
> >>  OK
> >>  <3>CTRL-EVENT-SCAN-RESULTS
> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia'
> >> freq=2452 MHz)
> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0
> >>  <3>CTRL-EVENT-SCAN-RESULTS
> >>  <3>Trying to associate with 6c:3b:6b:ab:ce:d4 (SSID='Palombia'
> >> freq=2412 MHz)
> >>  <3>Associated with 6c:3b:6b:ab:ce:d4
> >>
> >> a2:e9 is the loudest AP here in my office, but my I have been in the
> >> other end of the house iwn consistently fails to associate with it
> >> and
> >> and keeps picking the weaker AP in the far end.
> >>
> >> Eventually (hours!) it disconnects from the weaker ap, also with
> >> "reason=0" and gets it right:
> >>
> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 [GTK=CCMP]
> >>  <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0
> >>  <3>CTRL-EVENT-SCAN-RESULTS
> >>  <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia'
> >> freq=2452 MHz)
> >>  <3>Associated with 6c:3b:6b:3d:a2:e9
> >>  <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 [PTK=CCMP
> >> GTK=CCMP]
> >>  <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9
> completed
> >> [id=3 id_str=]
> >>  <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 [GTK=CCMP]
> >>
> >> And yes, working roaming would be nice too...
> >
> > I have the problem that when roaming networks become disabled
> >
> >   $ wpa_cli
> >   Selected interface 'wlan0'
> >
> >   Interactive mode
> >
> >   > list_networks
> >   network id / ssid / bssid / flags
> >   0   network1any [CURRENT]
> >   1   network2 any[DISABLED]
> >   2   network3 any[DISABLED]
> >   3   network4 any[DISABLED]
> >   4   network5 any[DISABLED]
> >   Selected interface 'wlan0'
> >
> >
> > I address this by doing network_enable x in wpa_cli and it all comes
> > back. I asked Adrian about this in the past, but it needs some
> > debugging
> > to pin down.
>
>
> Is this iwm(4) as well in your case or another card?
>
> /bz
> ___
> freebsd-wirel...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org
> "
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Lockdown adaX numbers to allow booting ?

[Toomas Soome]

> On 19 Sep 2019, at 17:02, Kurt Jaeger  wrote:
> 
> Hi!
> 
> We have a system with 10 SATA disks. 2 disks are for the system,
> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:
> 
> bck72.8T  38.7T  34.1T- - 1%53%  1.00x  ONLINE  -
> 
> The problem is that if all 10 disks are connected, the system
> looses track from where it should boot and fails to boot (serial boot log):
> 
> 
> /boot/config: -Dh -S115200
> 
> Consoles: internal video/keyboard  serial port
> BTX loader 1.00  BTX version is 1.02
> Consoles: internal video/keyboard  serial port
> BIOS drive C: is disk0
> BIOS drive D: is disk1
> BIOS drive E: is disk2
> BIOS drive F: is disk3
> BIOS drive G: is disk4
> BIOS drive H: is disk5
> BIOS drive I: is disk6
> BIOS drive J: is disk7
> BIOS drive K: is disk8
> BIOS drive L: is disk9
> //
> /
> 
> 
> The system disks are detected as ada4 and ada5, when all disks are
> plugged in.
> 
> The solution right now is this to unplug all disks of the 'bck' pool,
> reboot, and re-insert the data disks after the boot is finished.
> 
> I looked into the output to kenv(1), but did not find inspiration
> on how to fix this.
> 
> Now my questions:
> 
> - Shuffeling around SATA cables seems the wrong approach to fix this.
> - Can we somehow lock down the disk numbering so that the system disks
>  are detected as ada0 and ada1 ?


Why this order does change?  One would expect disks 0 and 1 to be OS disks and 
the rest for data…

Also the question is, what you mean with “system looses track”? disk4 becomes 
adaX? why it matters, are you using ufs on boot disks?

rgds,
toomas


> - Would
>  rootdev="disk4s1a"
>  in /boot/loader.conf work or is that the wrong approach ?
> - How could we configure two drivers as root devices in loader.conf ?
> 
> -- 
> p...@opsec.eu+49 171 3101372One year to go !
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Lockdown adaX numbers to allow booting ?

[Kurt Jaeger]

Hi!

We have a system with 10 SATA disks. 2 disks are for the system,
8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:

bck72.8T  38.7T  34.1T- - 1%53%  1.00x  ONLINE  -

The problem is that if all 10 disks are connected, the system
looses track from where it should boot and fails to boot (serial boot log):


/boot/config: -Dh -S115200

Consoles: internal video/keyboard  serial port
BTX loader 1.00  BTX version is 1.02
Consoles: internal video/keyboard  serial port
BIOS drive C: is disk0
BIOS drive D: is disk1
BIOS drive E: is disk2
BIOS drive F: is disk3
BIOS drive G: is disk4
BIOS drive H: is disk5
BIOS drive I: is disk6
BIOS drive J: is disk7
BIOS drive K: is disk8
BIOS drive L: is disk9
//
/


The system disks are detected as ada4 and ada5, when all disks are
plugged in.

The solution right now is this to unplug all disks of the 'bck' pool,
reboot, and re-insert the data disks after the boot is finished.

I looked into the output to kenv(1), but did not find inspiration
on how to fix this.

Now my questions:

- Shuffeling around SATA cables seems the wrong approach to fix this.
- Can we somehow lock down the disk numbering so that the system disks
  are detected as ada0 and ada1 ?
- Would
  rootdev="disk4s1a"
  in /boot/loader.conf work or is that the wrong approach ?
- How could we configure two drivers as root devices in loader.conf ?

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

[Bjoern A. Zeeb]

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 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 different network.


I suffer from the dreaded "reason=0" when I move inside my house:

> scan
OK
<3>CTRL-EVENT-SCAN-RESULTS
	<3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' 
freq=2452 MHz)

<3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0
<3>CTRL-EVENT-SCAN-RESULTS
	<3>Trying to associate with 6c:3b:6b:ab:ce:d4 (SSID='Palombia' 
freq=2412 MHz)

<3>Associated with 6c:3b:6b:ab:ce:d4

a2:e9 is the loudest AP here in my office, but my I have been in the
other end of the house iwn consistently fails to associate with it 
and

and keeps picking the weaker AP in the far end.

Eventually (hours!) it disconnects from the weaker ap, also with
"reason=0" and gets it right:

<3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 [GTK=CCMP]
<3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0
<3>CTRL-EVENT-SCAN-RESULTS
	<3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' 
freq=2452 MHz)

<3>Associated with 6c:3b:6b:3d:a2:e9
	<3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 [PTK=CCMP 
GTK=CCMP]
	<3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 completed 
[id=3 id_str=]

<3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 [GTK=CCMP]

And yes, working roaming would be nice too...


I have the problem that when roaming networks become disabled

$ wpa_cli
Selected interface 'wlan0'

Interactive mode

> list_networks
network id / ssid / bssid / flags
0   network1any [CURRENT]
1   network2 any[DISABLED]
2   network3 any[DISABLED]
3   network4 any[DISABLED]
4   network5 any[DISABLED]
Selected interface 'wlan0'


I address this by doing network_enable x in wpa_cli and it all comes
back. I asked Adrian about this in the past, but it needs some 
debugging

to pin down.



Is this iwm(4) as well in your case or another card?

/bz
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: wlan can't discover known networks after relocating

[Tom Jones]

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 reconnect automatically and I have
> >to do wlan0 scan manually for it to pick up the different network.
> 
> I suffer from the dreaded "reason=0" when I move inside my house:
> 
>   > scan
>   OK
>   <3>CTRL-EVENT-SCAN-RESULTS 
>   <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' 
> freq=2452 MHz)
>   <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:3d:a2:e9 reason=0
>   <3>CTRL-EVENT-SCAN-RESULTS 
>   <3>Trying to associate with 6c:3b:6b:ab:ce:d4 (SSID='Palombia' 
> freq=2412 MHz)
>   <3>Associated with 6c:3b:6b:ab:ce:d4
> 
> a2:e9 is the loudest AP here in my office, but my I have been in the
> other end of the house iwn consistently fails to associate with it and
> and keeps picking the weaker AP in the far end.
> 
> Eventually (hours!) it disconnects from the weaker ap, also with
> "reason=0" and gets it right:
> 
>   <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 [GTK=CCMP]
>   <3>CTRL-EVENT-DISCONNECTED bssid=6c:3b:6b:ab:ce:d4 reason=0
>   <3>CTRL-EVENT-SCAN-RESULTS 
>   <3>Trying to associate with 6c:3b:6b:3d:a2:e9 (SSID='Palombia' 
> freq=2452 MHz)
>   <3>Associated with 6c:3b:6b:3d:a2:e9
>   <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 [PTK=CCMP 
> GTK=CCMP]
>   <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 completed 
> [id=3 id_str=]
>   <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 [GTK=CCMP]
> 
> And yes, working roaming would be nice too...

I have the problem that when roaming networks become disabled

$ wpa_cli
Selected interface 'wlan0'

Interactive mode

> list_networks
network id / ssid / bssid / flags
0   network1any [CURRENT]
1   network2 any[DISABLED]
2   network3 any[DISABLED]
3   network4 any[DISABLED]
4   network5 any[DISABLED]
Selected interface 'wlan0'


I address this by doing network_enable x in wpa_cli and it all comes
back. I asked Adrian about this in the past, but it needs some debugging
to pin down.

- [tj]
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Another X server start failure

[mms . vanbreukelingen]

Having a Raden 240 (sometimes 250) and an older AMDGPU. The older card is 
deactivated in BIOS but it is been found by the X -configure problem. X server 
did start one time with -config /root/xorg.conf.new, copied to /etc/X11/
xorg.conf, never got back any "blank black grafic" screen. Rebuilt new world 
and the kern with WITNESS option on and option LOCK_PROFILING. Using llvm-
devel is useless in that case, if it doesn't with the 8.0.X. 

Can't enter framebuffer mode, tells /var/log/x11_*.log,  no VESA, no xfcb. 
sddm tells: xauth: bad add command line, bad delete command line, bad add 
commandline. It used to work with even X -configure fatal error and sddm, so 
what to xrite in xauth; normally sddm autoconfigs. 

I guess it's the recognization from both cards, what is the option to really 
and finally deactivate this on-board card on an ASUS PRIME 350 board (I just 
mean NOT to cut the part of the board where grafics situatiated with a laser-
cutter :-) )? This one has never been used as it been too old for good 3D-
Gaming what has been a topic a year ago - not for me, but for a user. 

What's the state of art for 3D-virutal-glasses and gloves? I guess the same as 
with the AI! I guess freeBSD has other functions to do than beeing a desktop 
OS!

Thx for help in advance, 
Yours, Miranda


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"