Am Montag, 16. September 2024, 19:59:44 CEST schrieb Frank McCormick:
> I am faced with a strange problem. I have no internet access on Trixie
> on one of two partitions on my ssd.
> I was attempting to solve a problem I am having with Vivaldi by
> installing Seahorse. Apt quit halfway through downloading the necessary
> files complaining it could not resolve a bunch of Debian repositories.
> Ever since that I have no internet access in Trixie. It's not a hardware
> problem as I have full access on the other partition which runs Opensuse
> Tumbleweed. Earlier today I did an update of Trixie and it went fine.
>
> Can someone help me diagnose the problem ?
>
> This is my apt sources list
>
> deb http://deb.debian.org/debian trixie main contrib non-free
> non-free-firmware
> deb-src http://deb.debian.org/debian trixie main contrib non-free
> deb http://deb.debian.org/debian trixie-updates main contrib non-free
> non-free-firmware
> deb-src http://deb.debian.org/debian trixie-updates main contrib non-free
>
> deb http://deb.debian.org/debian trixie-backports main contrib non-free
> non-free-firmware
> deb-src http://deb.debian.org/debian trixie-backports main contrib non-free
> deb http://deb.debian.org/debian trixie-proposed-updates
> non-free-firmware main contrib non-free
>
> Thanks
What does
ifconfig -a
(eecute as root) tell?
Is it really enp0 or enp0s25?
Second question:
If you give the network interface a hard ip, does it work?
In /etc/network/interfaces edit these lines like the example
------
auto lo enp0s10
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
iface enp0s10 inet static
address 192.168.3.2
netmask 255.255.255.0
broadcast 192.168.178.255
gateway 192.168.3.2
--------
Check the correct name of your ethernet device! See above.
Also create (if not eistent) a file /etc/resolv.conf and enter DNS IPs like this example.
----
# Generated by NetworkManager
nameserver 208.67.222.222
nameserver 208.67.220.220
nameserver fd00::de39:6fff:fe2a:6101
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2a02:560:58ad:b300:de39:6fff:fe2a:6101
-------
PLEASE NOTE: This is only for testing purposes! If you are using networ-manager, it will wuse its own configuration files.
If this above is working, check, what is the difference to networ-manager.
If you now the ethernet device name (like enp0s10 in my eample), you can also try
dhclient enp0s10
as root. Of course you have to use the name of your ethernet device. (Besides, these names are called "predicted names", but I think, you now this already).
Good luck!
Hans