• WiFi - NM puzzle.

    From Jonathan N. Little@21:1/5 to All on Fri Jul 23 20:58:31 2021
    Long story short: Some of the systems at the library I manage came with
    wifi although all are wired Ethernet. Patrons sometimes would enable
    wifi cause a password prompt and confusion. I thought the simplest
    solution was to exclude wifi from NetworkManager management.

    /etc/NetworkManager/conf.d/99-unmanaged-devices.conf

    unmanaged-devices=interface-name:wlp2s0

    Worked great until reboot and this would disable NetworkManager from
    starting, it would fail with systemd new useless error message of failed
    with error output 1.

    Question why would this disable NetworkManager and with it networking...

    BTW: my solution was to yank all the wifi cards out of the motherboard
    of effected systems.


    Take care,

    Jonathan
    -------------------
    LITTLE WORKS STUDIO
    http://www.LittleWorksStudio.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From stepore@21:1/5 to Jonathan N. Little on Fri Jul 23 23:32:54 2021
    On 07/23/2021 05:58 PM, Jonathan N. Little wrote:
    BTW: my solution was to yank all the wifi cards out of the motherboard
    of effected systems.

    Could have probably tried blocklisting the wifi kernel module.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jonathan N. Little@21:1/5 to stepore on Sat Jul 24 09:42:21 2021
    stepore wrote:
    On 07/23/2021 05:58 PM, Jonathan N. Little wrote:
    BTW: my solution was to yank all the wifi cards out of the motherboard
    of effected systems.

    Could have probably tried blocklisting the wifi kernel module.

    I thought of that but then I would have identify and match driver per
    system. The point here was that these are public access patron computers
    that even though not all systems have identical hardware that have all identical setups. Makes administration simpler. IF a systems fails I can
    have a new system setup and configured in less than 15min.

    My question was more academic as to why would configuring Network
    Manager to not manage a wifi device now under systemd fails but used to
    work pre-D.

    --
    Take care,

    Jonathan
    -------------------
    LITTLE WORKS STUDIO
    http://www.LittleWorksStudio.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Jonathan N. Little on Sat Jul 24 14:09:42 2021
    Jonathan N. Little wrote:
    stepore wrote:
    On 07/23/2021 05:58 PM, Jonathan N. Little wrote:
    BTW: my solution was to yank all the wifi cards out of the motherboard
    of effected systems.
    Could have probably tried blocklisting the wifi kernel module.

    I thought of that but then I would have identify and match driver per
    system. The point here was that these are public access patron computers
    that even though not all systems have identical hardware that have all identical setups. Makes administration simpler. IF a systems fails I can
    have a new system setup and configured in less than 15min.

    My question was more academic as to why would configuring Network
    Manager to not manage a wifi device now under systemd fails but used to
    work pre-D.


    A subsystem will fail, if a config file has a syntax error.
    It's possible the file needs more meat in it, and the
    following may not be correct either.

    [main]
    plugins=keyfile

    [keyfile]
    unmanaged-devices=interface-name:enp1s0

    Available plugins: keyfile, ifcfg-rh, ifupdown, ifcfg-suse

    keyfile
    plugin is the generic plugin that supports all the connection types
    and capabilities that NetworkManager has. It writes files out in a
    .ini-style format in /etc/NetworkManager/system-connections.
    For security, it will ignore files that are readable or writeable
    by any user or group other than root since private keys and
    passphrases may be stored in plaintext inside the file.

    You can see other examples of the idea at least, here.
    This is from the year 2011.

    https://askubuntu.com/questions/21914/how-can-i-make-networkmanager-ignore-my-wireless-card

    *******

    Good config files have commented out sections
    to show the structure, so the user has a chance
    of getting the syntax correct on the first try.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jonathan N. Little@21:1/5 to Paul on Sat Jul 24 15:45:25 2021
    Paul wrote:
    Jonathan N. Little wrote:
    stepore wrote:
    On 07/23/2021 05:58 PM, Jonathan N. Little wrote:
    BTW: my solution was to yank all the wifi cards out of the motherboard >>>> of effected systems.
    Could have probably tried blocklisting the wifi kernel module.

    I thought of that but then I would have identify and match driver per
    system. The point here was that these are public access patron computers
    that even though not all systems have identical hardware that have all
    identical setups. Makes administration simpler. IF a systems fails I can
    have a new system setup and configured in less than 15min.

    My question was more academic as to why would configuring Network
    Manager to not manage a wifi device now under systemd fails but used to
    work pre-D.


    A subsystem will fail, if a config file has a syntax error.
    It's possible the file needs more meat in it, and the
    following may not be correct either.

       [main]
       plugins=keyfile

       [keyfile]
       unmanaged-devices=interface-name:enp1s0

    Available plugins:  keyfile, ifcfg-rh, ifupdown, ifcfg-suse

    keyfile
        plugin is the generic plugin that supports all the connection types     and capabilities that NetworkManager has. It writes files out in a     .ini-style format in /etc/NetworkManager/system-connections.
        For security, it will ignore files that are readable or writeable     by any user or group other than root since private keys and
        passphrases may be stored in plaintext inside the file.

    You can see other examples of the idea at least, here.
    This is from the year 2011.

    https://askubuntu.com/questions/21914/how-can-i-make-networkmanager-ignore-my-wireless-card



    Ah ha, my searches didn't turn up that one.

    Good config files have commented out sections
    to show the structure, so the user has a chance
    of getting the syntax correct on the first try.


    Totally agree.


    --
    Take care,

    Jonathan
    -------------------
    LITTLE WORKS STUDIO
    http://www.LittleWorksStudio.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)