Announcement

Collapse
No announcement yet.

network problems after 6.8.0-35 to 6.8.0-41 netplan(etc..) update

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    network problems after 6.8.0-35 to 6.8.0-41 netplan(etc..) update

    it is not a material associated pb. you will see why.

    FROM
    Linux FLY-ENGINE 6.8.0-35-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 2 20:41:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

    TO
    Linux FLY-ENGINE 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 2 20:41:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

    i have an netplan update that broke all my connexions:
    - no network listed in manager to activate
    - local 127.0.0.0 network moved to a curious 169.x.x.x ip address.
    - deleting not functional interface in netmanager cause an error because of unreacheable files or bad rights on them ( netplan generate ok / apply not ok but net file in /netplan is deleted)
    - Impossible to use systemd renderer because of non existence for naturals config folders.( thinking it will cause some bad results with a netplan natural kubuntu context )
    - trying to configure a new interface make hasardous results in config and interface do not working( be there but no activated, and sometimes taking "Lo" name)

    to solve this problem if it is not a material or pilot pb::
    - configure new interface with netmanager ( netplan apply) ( it will show Lo interface up but not the other)
    - manually configure with console admin, ip, gateway(route add...) and resolvers( resolv.conf) for your net interface ( connexion is very unstable switch on and off all the time )
    - activate interface or reboot
    - test net with ping google or web access. you have now a basic connection
    - do an apt update
    - and force apt install kde, then apt install kde-full ( or try to remove netmanager and reinstall it)
    - reconfigure your interfaces with netmanager

    now i have retrieved a normal working connexion.

    it should exist a more specific solution but i don't know enough kubuntu specs to find it.

    i show during the resolution that WakeonLan for any created new interface is on. but not wanted. and i didn't seek where the option to disable it is located in kdenetmanager.
    Is a "ethtool eth0 -wol d" is a launch time config only ?
    Last edited by MegsOconnor; Aug 27, 2024, 01:00 PM.

    #2
    Apologies, but I can't follow what you are saying, or doing.

    Or why you are messing with netplan instead of leaving things alone and using networkmanager

    If you use netplan/networkd as the default networking renderer (as is used on Ubuntu Server) , the Network Manager GUI wont show or control the interfaces at all.

    Originally posted by MegsOconnor View Post

    - and force apt install kde, then apt install kde-full
    Why? This is overkill and also installs a lot of extra software. Kde-full is literally every KDE application available


    If you want to switch to using networkmanager as the netplan's renderer instead of networkd, this or something similar can be done

    https://ichimusai.org/set-netplan-to...etwork-manager

    Not 100% sure, as I'm not sure what you are doing, or why, or what you've done . But I built my laptop starting from Ubuntu Server and had to do something similar ( but not 100% exactly) to be able to use KDEs Networkmanager GUI to manage my WiFi.

    At to WoL, that is hardware. You enable that in your BIOS, since it is something available when the computer is shut down. Turn it off there

    But the correct command for ethtool is
    .
    Code:
    sudo ethtool eth0 -s wol d
    -s means "set an option"

    This is a one time command iirc

    Comment


      #3
      i am using ( netmanager renderer). ( default option )
      kde/kde-full -> yes overkilling... but in the case as me, you already have kde there is nothing to install, so kde-full may correct the pb. i just set working steps, may reinstall kde is useless.
      wol bios: ok already does, so thats ok.
      ethtool : yes i have found the command on forums, and badly memory retrieved.
      to be short: thinking the problem is in the interaction of netplan with Netmanager after update. tryed to reinstall netmanager or something in Kde-full package seems to solve the PB. but maybe just config the interface could work, not tested( i don't want reloose my connexion XD.)
      some events make me thinking about an attack, but it could be only a missconfig about netplan upgrade and networkmanager. may i had a bad version of netmanager when the netplan upgrade come.
      Last edited by MegsOconnor; Aug 27, 2024, 12:54 PM.

      Comment

      Working...
      X