static ip

[greg612]

Ok I reloaded this thing its fresh as fresh can be...... this is what im starting with now I will purge all network manager crap and see how it goes will post results

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether f8:b1:56:e4:ca:fc brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 192.168.25.56/24 metric 100 brd 192.168.25.255 scope global dynamic eno1
       valid_lft 6405sec preferred_lft 6405sec
    inet6 fe80::fab1:56ff:fee4:cafc/64 scope link 
       valid_lft forever preferred_lft forever

# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    ethernets:
        eno1:
            dhcp4: true
    version: 2

[greg612]

ok after purging network manager off no docker nothin in it

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether f8:b1:56:e4:ca:fc brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 192.168.25.3/24 brd 192.168.25.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::fab1:56ff:fee4:cafc/64 scope link 
       valid_lft forever preferred_lft forever

network:
  version: 2
  renderer: networkd
  ethernets:
     eno1:
       addresses:
          - 192.168.25.3/24
       dhcp4: false
       dhcp6: false
       routes:
         - to: default
           via: 192.168.25.1
       optional: true
       nameservers:
         addresses: [ "9.9.9.9","149.112.112.112" ]

BOOM there goes the internet gone

ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

starts ping then just sits there Im lost never seen anything like this wow just wow

this is after sitting like 15 min

ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
883 packets transmitted, 0 received, 100% packet loss, time 903146ms

[greg612]

also tried this also

james@mustang:~$ sudo apt-get purge network-manager
[sudo] password for james: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'network-manager' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  dns-root-data dnsmasq-base libbluetooth3 libndp0 libnm0 libteamdctl0 ppp pptp-linux
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
james@mustang:~$ sudo apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  dns-root-data dnsmasq-base libbluetooth3 libndp0 libnm0 libteamdctl0 ppp pptp-linux
0 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
After this operation, 3,981 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 84346 files and directories currently installed.)
Removing dns-root-data (2023112702~willsync1) ...
Removing dnsmasq-base (2.90-2build2) ...
Removing libbluetooth3:amd64 (5.72-0ubuntu5) ...
Removing libndp0:amd64 (1.8-1fakesync1build1) ...
Removing libnm0:amd64 (1.46.0-1ubuntu2) ...
Removing libteamdctl0:amd64 (1.31-1build3) ...
Removing pptp-linux (1.10.0-1build4) ...
Removing ppp (2.4.9-1+1.1ubuntu4) ...
Stopping all PPP connections...done.
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dbus (1.14.10-4ubuntu4) ...
Processing triggers for libc-bin (2.39-0ubuntu8.1) ...

[TheFu]

- 192.168.25.3/24 to 192.168.25.1 using that subnet mask?

That doesn't seem right.
When you allow DHCP, what's the IP and gateway that works?
Doesn't the gateway need to be in the same subnet as the LAN?

[MAFoElffen]

Sorry. I had typo's in Post #32. Was in a hurry. Corrected now.

Please go back an redo from the 3rd command on...

[TheFu]

For networking to work correctly, 3 things are needed.

• IP address
• Subnet/Netmask
• Gateway IP

Many posts ago, I asked to see two commands (ip a AND ip r) from a working config which would have shown these things. I asked to see it with DHCP and a working configuration. Then we could easily setup the correct values for a static IP from the working DHCP information.

This stuff isn't really that hard.

[MAFoElffen]

Look at the format of your nameservers address line...

Here is yours:

network:
  version: 2
  renderer: networkd
  ethernets:
     eno1:
       addresses:
          - 192.168.25.3/24
       dhcp4: false
       dhcp6: false
       routes:
         - to: default
           via: 192.168.25.1
       optional: true
       nameservers:
         addresses: [ "9.9.9.9","149.112.112.112" ]

Here is mine:

# Let networkd manage all devices on this system
network:
  version: 2
  renderer: networkd
  ethernets:
    enp12s0:
      addresses:
        - 10.0.0.3/8
      nameservers:
        addresses: [8.8.8.8, 8.8.4.4, 1.1.1.1]
      routes:
        - to: default
          via: 10.0.0.1
          metric: 100
          on-link: true
      dhcp4: false
      dhcp6: false
      optional: yes

[TheFu]

Both types of nameserver lines work fine, IME.

[greg612]

Thanks sorry been away for work I eill look into this in morning my bedtime

[TheFu]

Earlier this week, I installed Lubuntu 24.04 and setup a static IP using netplan. It worked fine using the examples I posted. The only issue I had was self-inflicted because I forgot to change the ethernet device name in the netplan YAML. The --debug option didn't show any error with that, which is disappointing. That error showed up somewhere else. It wasn't in my face, but it only took a 1-2 minutes to figure out and correct. Enabled systemd-networkd, then I purged nm-* and network-manager* from the system. Just feels better without that junk in the way.

I also installed Xubuntu 24.04, but it was too unstable and locked up too many times, so I deleted that install.

I still need to install Ubuntu Server 24.04. Just haven't gotten around to it. Appears that two of my issues with snap packages have better workarounds now. There's only 1 major issue remaining for me that is still a show-stopper. Access to non-hard-coded storage locations on a program-by-program basis. I did discover that my nextcloud snap install upgraded again without my approval after I've tried multiple times to hold it on a specific major release. Sigh.

I'm happy to post the working 24.04 YAML, if you like.