Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #255551 > unrolled thread

how to activate my wireless card? nmtui only shows wireless connections . . .

Started byAlbretch Mueller <lbrtchx@gmail.com>
First post2023-03-03 16:50 +0100
Last post2023-03-04 07:40 +0100
Articles 9 on this page of 29 — 10 participants

Back to article view | Back to linux.debian.user


Contents

  how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-03 16:50 +0100
    Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-03 17:10 +0100
      Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-03 18:10 +0100
        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-03 18:20 +0100
        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-03-03 18:30 +0100
          Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-03 22:50 +0100
            Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Dan Ritter <dsr@randomstring.org> - 2023-03-03 23:20 +0100
              Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-04 09:10 +0100
            Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-03 23:30 +0100
              Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-04 01:10 +0100
                Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-04 18:20 +0100
                  Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-05 03:50 +0100
                    Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-05 21:40 +0100
                      Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-05 22:00 +0100
                        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-08 00:40 +0100
            Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-04 00:40 +0100
              Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-04 01:00 +0100
    Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Jeffrey Walton <noloader@gmail.com> - 2023-03-03 23:50 +0100
      Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Greg Wooledge <greg@wooledge.org> - 2023-03-04 00:20 +0100
        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Jeffrey Walton <noloader@gmail.com> - 2023-03-04 07:10 +0100
          Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-04 18:20 +0100
            Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Jeffrey Walton <noloader@gmail.com> - 2023-03-04 19:00 +0100
              Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Curt <curty@free.fr> - 2023-03-05 18:30 +0100
                Re: how to activate my wireless card? nmtui only shows wireless connections . . . Anssi Saari <as@sci.fi> - 2023-03-05 20:30 +0100
                  Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Greg Wooledge <greg@wooledge.org> - 2023-03-05 21:10 +0100
                  Re: how to activate my wireless card? nmtui only shows wireless  connections . . . Albretch Mueller <lbrtchx@gmail.com> - 2023-03-05 21:20 +0100
                  Re: how to activate my wireless card? nmtui only shows wireless  connections . . . David Wright <deblis@lionunicorn.co.uk> - 2023-03-05 21:40 +0100
                    Re: how to activate my wireless card? nmtui only shows wireless connections . . . Anssi Saari <as@sci.fi> - 2023-03-06 21:20 +0100
        Re: how to activate my wireless card? nmtui only shows wireless  connections . . . <tomas@tuxteam.de> - 2023-03-04 07:40 +0100

Page 2 of 2 — ← Prev page 1 [2]


#255588

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2023-03-04 18:20 +0100
Message-ID<G5DI5-a3Xs-1@gated-at.bofh.it>
In reply to#255575
On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge <greg@wooledge.org> wrote:
> > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > > does not move around once installed, the interface will always have
> > > the same name like 'enp4s0'.
> >
> > That's a wonderful idea, but it doesn't quite work in practice.  There are
> > ways that a "predictable" interface name may change.  A BIOS/firmware
> > upgrade can do it.  Adding or removing devices can also do it, in
> > some cases.  They don't even have to be network interfaces.
> 
> Yeah, that's udev and systemd screwing things up.

Not really. You've got plenty of choice:

net.ifnames=0, biosdevname=0 (on Dell), and
NamePolicy={kernel,database,onboard,slot,path,mac,keep}

Who could want more?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#255595

FromJeffrey Walton <noloader@gmail.com>
Date2023-03-04 19:00 +0100
Message-ID<G5EkN-a4bQ-3@gated-at.bofh.it>
In reply to#255588
On Sat, Mar 4, 2023 at 12:12 PM David Wright <deblis@lionunicorn.co.uk> wrote:
>
> On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> > On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge <greg@wooledge.org> wrote:
> > > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > > > does not move around once installed, the interface will always have
> > > > the same name like 'enp4s0'.
> > >
> > > That's a wonderful idea, but it doesn't quite work in practice.  There are
> > > ways that a "predictable" interface name may change.  A BIOS/firmware
> > > upgrade can do it.  Adding or removing devices can also do it, in
> > > some cases.  They don't even have to be network interfaces.
> >
> > Yeah, that's udev and systemd screwing things up.
>
> Not really. You've got plenty of choice:
>
> net.ifnames=0, biosdevname=0 (on Dell), and
> NamePolicy={kernel,database,onboard,slot,path,mac,keep}

If you are creating the problem you should not be surprised there is a problem.

Jeff

[toc] | [prev] | [next] | [standalone]


#255628

FromCurt <curty@free.fr>
Date2023-03-05 18:30 +0100
Message-ID<G60lj-akUb-5@gated-at.bofh.it>
In reply to#255595
2023-03-04, Jeffrey Walton <noloader@gmail.com> wrote:
> On Sat, Mar 4, 2023 at 12:12 PM David Wright <deblis@lionunicorn.co.uk> wrote:
>>
>> On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
>> > On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge <greg@wooledge.org> wrote:
>> > > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
>> > > > The 'p' is a pci bus, the 's' is a slot number. Since the interface
>> > > > does not move around once installed, the interface will always have
>> > > > the same name like 'enp4s0'.
>> > >
>> > > That's a wonderful idea, but it doesn't quite work in practice.  There are
>> > > ways that a "predictable" interface name may change.  A BIOS/firmware
>> > > upgrade can do it.  Adding or removing devices can also do it, in
>> > > some cases.  They don't even have to be network interfaces.
>> >
>> > Yeah, that's udev and systemd screwing things up.
>>
>> Not really. You've got plenty of choice:
>>
>> net.ifnames=0, biosdevname=0 (on Dell), and
>> NamePolicy={kernel,database,onboard,slot,path,mac,keep}
>
> If you are creating the problem you should not be surprised there is a problem.
>
> Jeff
>
>

https://wiki.debian.org/NetworkInterfaceNames

* UNPREDICTABILITY
it turns out even after all this [**an enumeration of complications and corner
cases**] there are still reported cases of interfaces changing their name on a
reboot. All that needs to happen is that some buggy BIOS (or some new, less
buggy version of a driver module, or systemd's naming policy) changes its mind
about some detail like whether or not your hardware counts as the kind that
should have an ONBOARD name. There are even multiple reports of devices
changing their PCI-port numbering due to other hardware being installed.

[toc] | [prev] | [next] | [standalone]


#255631 — Re: how to activate my wireless card? nmtui only shows wireless connections . . .

FromAnssi Saari <as@sci.fi>
Date2023-03-05 20:30 +0100
SubjectRe: how to activate my wireless card? nmtui only shows wireless connections . . .
Message-ID<G62dr-am7k-5@gated-at.bofh.it>
In reply to#255628
Curt <curty@free.fr> writes:

> * UNPREDICTABILITY
> it turns out even after all this [**an enumeration of complications and corner
> cases**] there are still reported cases of interfaces changing their name on a
> reboot.

I have just this fun kind of unpredictability in my router's 4G
module. Mostly, it comes up as wwan0 but sometimes it's wwx<random>. So
I put something in my 4G management script to rename such interface if
there's no wwan0. Easier to force the interface name since I need to
know the interface in the firewall and failover script too.

[toc] | [prev] | [next] | [standalone]


#255634

FromGreg Wooledge <greg@wooledge.org>
Date2023-03-05 21:10 +0100
Message-ID<G62Q9-amAv-1@gated-at.bofh.it>
In reply to#255631
On Sun, Mar 05, 2023 at 09:22:10PM +0200, Anssi Saari wrote:
> I have just this fun kind of unpredictability in my router's 4G
> module. Mostly, it comes up as wwan0 but sometimes it's wwx<random>. So
> I put something in my 4G management script to rename such interface if
> there's no wwan0.

If you're running systemd, you can create a "dot link" file
(see systemd.link(5)) to assign names to interfaces based on any
criteria you can manage to grab hold of.  MAC address or whatever.

[toc] | [prev] | [next] | [standalone]


#255636

FromAlbretch Mueller <lbrtchx@gmail.com>
Date2023-03-05 21:20 +0100
Message-ID<G62ZP-amE5-7@gated-at.bofh.it>
In reply to#255631
 I thought “unpredictability” was the name of my daily drama show, but
apparently “I am not the only one”. Yes, I know javascript is the
primary vector they use to mess with whomever they choose, regardless
of if they wear a “tiny tin hat” or expensive shoes.
 In my case, among many other things, they somehow inject key loggers
through the browser every time I access the Internet from wherever I
access it, but there is way more to it. Probably I am too old for that
kind of crap, but why would a BIOS need to be WiFi enabled? Is the
kernel itself doing all that name changing? Why would it do that? . .
.
 As part of my work I have to do lots of text cleansing. Even
Libreoffice inserts as part of their tags lots of watermarking crap
which of course is being used to track texts, but it would just be
unnecessary noise in a text corpus. I asked them once why they were
doing that and they, expectedly, started to act like “you are
paranoid”, certainly wear a “tiny tin hat” . . .

[toc] | [prev] | [next] | [standalone]


#255639

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2023-03-05 21:40 +0100
Message-ID<G63jb-amPC-9@gated-at.bofh.it>
In reply to#255631
On Sun 05 Mar 2023 at 21:22:10 (+0200), Anssi Saari wrote:
> Curt <curty@free.fr> writes:
> 
> > * UNPREDICTABILITY
> > it turns out even after all this [**an enumeration of complications and corner
> > cases**] there are still reported cases of interfaces changing their name on a
> > reboot.
> 
> I have just this fun kind of unpredictability in my router's 4G
> module. Mostly, it comes up as wwan0 but sometimes it's wwx<random>. So
> I put something in my 4G management script to rename such interface if
> there's no wwan0. Easier to force the interface name since I need to
> know the interface in the firewall and failover script too.

So what was wrong with using a .link file like:

  [Match]
  Type=wwan
  [Link]
  NamePolicy=keep kernel

or

  [Match]
  Type=wwan
  [Link]
  Name=my4g

Did this not work?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#255660 — Re: how to activate my wireless card? nmtui only shows wireless connections . . .

FromAnssi Saari <as@sci.fi>
Date2023-03-06 21:20 +0100
SubjectRe: how to activate my wireless card? nmtui only shows wireless connections . . .
Message-ID<G6ptn-aC8a-7@gated-at.bofh.it>
In reply to#255639
David Wright <deblis@lionunicorn.co.uk> writes:

> So what was wrong with using a .link file like:
>
>   [Match]
>   Type=wwan
>   [Link]
>   NamePolicy=keep kernel
>
> or
>
>   [Match]
>   Type=wwan
>   [Link]
>   Name=my4g
>
> Did this not work?

Nothing was wrong but I just added a few lines to my management script
to do the renaming. Easy to do, easy to test.

It's not like I can have systemd-networkd manage the device, I have to
use qmi-network and udhcpc.

[toc] | [prev] | [next] | [standalone]


#255576

From<tomas@tuxteam.de>
Date2023-03-04 07:40 +0100
Message-ID<G5tIJ-9XxD-1@gated-at.bofh.it>
In reply to#255566

[Multipart message — attachments visible in raw view] — view raw

On Fri, Mar 03, 2023 at 06:09:40PM -0500, Greg Wooledge wrote:
> On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > does not move around once installed, the interface will always have
> > the same name like 'enp4s0'.
> 
> That's a wonderful idea, but it doesn't quite work in practice.  There are
> ways that a "predictable" interface name may change.  A BIOS/firmware
> upgrade can do it.  Adding or removing devices can also do it, in
> some cases.  They don't even have to be network interfaces.

And don't get us started with USB dongles, which are enumerated across
many and diverse hubs depending on your electricity supplier, moon phase
and all.

    "You're In A Maze Of Twisty Little Passages, All Alike"

Once I understood what this is doing, I decided that I have to watch
out with consistent interface names as I had to watch out with the
traditional ones: the more complex names I can't memorise don't buy
me much.

Then I decided to go back to traditional names. Luckily, that's an
option.

Cheers
-- 
t

[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user


csiph-web