Sometime ago I wrote to this list about network connection problems. I reinstalled my fedora server and all was fine. Well I reinstall a windows system and had to fix grub2. So I booted F38 server and this is the error I got.
Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
I did nothing to the system and all I tried to run was 'dnf distro-sync' for updates. Is this grub2 related? Since it had to be reinstalled from scratch? The system has always been there I just cleared and reinstalled a Windows on another partition and thusly had to reinstall a new grub2 bootloader. It boots fine.
B
On 8/7/23 13:18, Bill Cunningham wrote:
Sometime ago I wrote to this list about network connection problems. I reinstalled my fedora server and all was fine. Well I reinstall a windows system and had to fix grub2. So I booted F38 server and this is the error I got.
Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
I did nothing to the system and all I tried to run was 'dnf distro-sync' for updates. Is this grub2 related? Since it had to be reinstalled from scratch? The system has always been there I just cleared and reinstalled a Windows on another partition and thusly had to reinstall a new grub2 bootloader. It boots fine.
grub is merely to get the OS loaded, it does nothing after. You have some sort of DNS issue, either with the Fedora install or with your network. Can you resolve any other sites?
On 8/7/23 13:23, Samuel Sieb wrote:
On 8/7/23 13:18, Bill Cunningham wrote:
Sometime ago I wrote to this list about network connection problems. I reinstalled my fedora server and all was fine. Well I reinstall a windows system and had to fix grub2. So I booted F38 server and this is the error I got.
Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
I did nothing to the system and all I tried to run was 'dnf distro-sync' for updates. Is this grub2 related? Since it had to be reinstalled from scratch? The system has always been there I just cleared and reinstalled a Windows on another partition and thusly had to reinstall a new grub2 bootloader. It boots fine.
grub is merely to get the OS loaded, it does nothing after. You have some sort of DNS issue, either with the Fedora install or with your network. Can you resolve any other sites?
Also, you say "no network access". Is that correct? Can you ping your router? All you show is a DNS resolve failure, that doesn't imply no network. Are you on wifi or ethernet? Does it show as connected?
On 8/7/2023 4:25 PM, Samuel Sieb wrote:
On 8/7/23 13:23, Samuel Sieb wrote:
On 8/7/23 13:18, Bill Cunningham wrote:
Sometime ago I wrote to this list about network connection problems. I reinstalled my fedora server and all was fine. Well I reinstall a windows system and had to fix grub2. So I booted F38 server and this is the error I got.
Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
I did nothing to the system and all I tried to run was 'dnf distro-sync' for updates. Is this grub2 related? Since it had to be reinstalled from scratch? The system has always been there I just cleared and reinstalled a Windows on another partition and thusly had to reinstall a new grub2 bootloader. It boots fine.
grub is merely to get the OS loaded, it does nothing after. You have some sort of DNS issue, either with the Fedora install or with your network. Can you resolve any other sites?
Also, you say "no network access". Is that correct? Can you ping your router? All you show is a DNS resolve failure, that doesn't imply no network. Are you on wifi or ethernet? Does it show as connected?
Wifi is what I am using. In the cli there is network errors reported if I try to ping anything. So I booted into the gui and there was no access. So I found my router on the wifi list of network and had to enter my router's network password. It connect and all was fine. I could ping anything and use the browser. Could there be a place where I can enter the wifi router password permanently and hopefully this would work.
B
On 8/7/23 13:42, Bill Cunningham wrote:
On 8/7/2023 4:25 PM, Samuel Sieb wrote:
On 8/7/23 13:23, Samuel Sieb wrote:
On 8/7/23 13:18, Bill Cunningham wrote:
Sometime ago I wrote to this list about network connection problems. I reinstalled my fedora server and all was fine. Well I reinstall a windows system and had to fix grub2. So I booted F38 server and this is the error I got.
Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
I did nothing to the system and all I tried to run was 'dnf distro-sync' for updates. Is this grub2 related? Since it had to be reinstalled from scratch? The system has always been there I just cleared and reinstalled a Windows on another partition and thusly had to reinstall a new grub2 bootloader. It boots fine.
grub is merely to get the OS loaded, it does nothing after. You have some sort of DNS issue, either with the Fedora install or with your network. Can you resolve any other sites?
Also, you say "no network access". Is that correct? Can you ping your router? All you show is a DNS resolve failure, that doesn't imply no network. Are you on wifi or ethernet? Does it show as connected?
Wifi is what I am using. In the cli there is network errors reported if I try to ping anything. So I booted into the gui and there was no access. So I found my router on the wifi list of network and had to enter my router's network password. It connect and all was fine. I could ping anything and use the browser. Could there be a place where I can enter the wifi router password permanently and hopefully this would work.
Look in /etc/NetworkManager/system-connections/. The connection config should have the password, so it should work now, assuming it's set to auto-connect.
On 8/7/2023 4:50 PM, Samuel Sieb wrote:
On 8/7/23 13:42, Bill Cunningham wrote:
On 8/7/2023 4:25 PM, Samuel Sieb wrote:
On 8/7/23 13:23, Samuel Sieb wrote:
On 8/7/23 13:18, Bill Cunningham wrote:
Sometime ago I wrote to this list about network connection problems. I reinstalled my fedora server and all was fine. Well I reinstall a windows system and had to fix grub2. So I booted F38 server and this is the error I got.
Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
I did nothing to the system and all I tried to run was 'dnf distro-sync' for updates. Is this grub2 related? Since it had to be reinstalled from scratch? The system has always been there I just cleared and reinstalled a Windows on another partition and thusly had to reinstall a new grub2 bootloader. It boots fine.
grub is merely to get the OS loaded, it does nothing after. You have some sort of DNS issue, either with the Fedora install or with your network. Can you resolve any other sites?
Also, you say "no network access". Is that correct? Can you ping your router? All you show is a DNS resolve failure, that doesn't imply no network. Are you on wifi or ethernet? Does it show as connected?
Wifi is what I am using. In the cli there is network errors reported if I try to ping anything. So I booted into the gui and there was no access. So I found my router on the wifi list of network and had to enter my router's network password. It connect and all was fine. I could ping anything and use the browser. Could there be a place where I can enter the wifi router password permanently and hopefully this would work.
Look in /etc/NetworkManager/system-connections/. The connection config should have the password, so it should work now, assuming it's set to auto-connect.
There were a coule of different files called *.nmconnection and one did have auto set. But I didn't see a password anywhere in the files. The did refer to the device name of the wifi connection. Anyway all seems well, for now anyway. :)
B
On Mon, Aug 07, 2023 at 05:14:04PM -0400, Bill Cunningham wrote:
On 8/7/2023 4:50 PM, Samuel Sieb wrote:
Look in /etc/NetworkManager/system-connections/. The connection config should have the password, so it should work now, assuming it's set to auto-connect.
There were a coule of different files called *.nmconnection and one did have auto set. But I didn't see a password anywhere in the files.
From what I know: the passwords might also be in /etc/sysconfig/network-scripts/keys-*
But if you have the "NetworkManager Applet" somewhere on your Desktop, right-clicking it should give access to Network settings - probably lots easier than manually setting up the above mentioned network files in /etc ...
Good luck!
Wolfgang
On 8/7/23 15:39, Wolfgang Pfeiffer wrote:
On Mon, Aug 07, 2023 at 05:14:04PM -0400, Bill Cunningham wrote:
On 8/7/2023 4:50 PM, Samuel Sieb wrote:
Look in /etc/NetworkManager/system-connections/. The connection config should have the password, so it should work now, assuming it's set to auto-connect.
There were a coule of different files called *.nmconnection and one did have auto set. But I didn't see a password anywhere in the files.
From what I know: the passwords might also be in /etc/sysconfig/network-scripts/keys-*
ifcfg files are deprecated now. Any recently made connections are stored in the nmconnection format. And the keys-* files are part of the ifcfg system.
Samuel Sieb composed on 2023-08-07 16:13 (UTC-0700):
Wolfgang Pfeiffer wrote:
From what I know: the passwords might also be in /etc/sysconfig/network-scripts/keys-*
ifcfg files are deprecated now. Any recently made connections are stored in the nmconnection format. And the keys-* files are part of the ifcfg system.
Can you say if that format equates to, or is it similar to, the format systemd-networkd uses? # inxi -S System: Host: big41 Kernel: 6.3.12-200.fc38.x86_64 arch: x86_64 bits: 64 Console: pty pts/0 Distro: Fedora release 38 (Thirty Eight) # rpm -qa | grep -iE 'kmana|d-netw|solv' | sort kf5-networkmanager-qt-5.108.0-1.fc38.x86_64 libsolv-0.7.22-4.fc38.x86_64 systemd-networkd-253.7-1.fc38.x86_64 # cat /etc/systemd/network/eth0.network [Match] PermanentMACAddress=00:00:00:00:00:00
[Network] Address=192.xxx.xxx.xxx/24 DNS=192.xxx.xxx.yyy 1.1.1.1 1.0.0.1 Gateway=192.xxx.xxx.yyy IPv6AcceptRA=no LinkLocalAddressing=no
# ls -gG /etc/resolv.conf -rw-r--r-- 1 233 Nov 30 2020 /etc/resolv.conf # ls -Gg /etc/sysconfig/network-scripts/*eth* -rw-r--r-- 1 267 Sep 9 2013 /etc/sysconfig/network-scripts/ifcfg-eth0 -rwxr-xr-x 1 6560 May 4 20:00 /etc/sysconfig/network-scripts/ifdown-eth -rwxr-xr-x 1 14192 May 4 20:00 /etc/sysconfig/network-scripts/ifup-eth # ip a ... 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff inet 192.xxx.xxx.zzz/24 brd 192.xxx.xxx.255 scope global eth0 valid_lft forever preferred_lft forever # systemctl list-unit-files | grep net | sort netconsole.service disabled disabled network-online.target static - network-pre.target static - network.service generated - network.target static - systemd-network-generator.service disabled enabled systemd-networkd-wait-online.service disabled disabled systemd-networkd-wait-online@.service disabled disabled systemd-networkd.service disabled disabled systemd-networkd.socket enabled disabled #
On 8/8/23 11:58, Felix Miata wrote:
Samuel Sieb composed on 2023-08-07 16:13 (UTC-0700):
Wolfgang Pfeiffer wrote:
From what I know: the passwords might also be in /etc/sysconfig/network-scripts/keys-*
ifcfg files are deprecated now. Any recently made connections are stored in the nmconnection format. And the keys-* files are part of the ifcfg system.
Can you say if that format equates to, or is it similar to, the format systemd-networkd uses?
# cat /etc/systemd/network/eth0.network [Match] PermanentMACAddress=00:00:00:00:00:00
[Network] Address=192.xxx.xxx.xxx/24 DNS=192.xxx.xxx.yyy 1.1.1.1 1.0.0.1 Gateway=192.xxx.xxx.yyy IPv6AcceptRA=no LinkLocalAddressing=no
It's similar only in the structure ("ini" file format), but not the content.
# ls -Gg /etc/sysconfig/network-scripts/*eth* -rw-r--r-- 1 267 Sep 9 2013 /etc/sysconfig/network-scripts/ifcfg-eth0 -rwxr-xr-x 1 6560 May 4 20:00 /etc/sysconfig/network-scripts/ifdown-eth -rwxr-xr-x 1 14192 May 4 20:00 /etc/sysconfig/network-scripts/ifup-eth
I think there's a Change for the next release to automatically convert those to the new format.
On Tue, Aug 08, 2023 at 12:39:42AM +0200, Wolfgang Pfeiffer wrote:
On Mon, Aug 07, 2023 at 05:14:04PM -0400, Bill Cunningham wrote:
On 8/7/2023 4:50 PM, Samuel Sieb wrote:
Look in /etc/NetworkManager/system-connections/. The connection config should have the password, so it should work now, assuming it's set to auto-connect.
There were a coule of different files called *.nmconnection and one did have auto set. But I didn't see a password anywhere in the files.
From what I know: the passwords might also be in /etc/sysconfig/network-scripts/keys-*
But if you have the "NetworkManager Applet" somewhere on your Desktop, right-clicking it should give access to Network settings - probably lots easier than manually setting up the above mentioned network files in /etc ...
Forgot to say that - if I'm not mistaken - the settings done via the "NetworkManager Applet" ("man nm-applet") are written to one of the mentioned two dirs in /etc ... Should be easily verified with something like
sudo find /etc -type f -cmin +0 -cmin -4
(or replacing "-cmin" with "-mmin") after changes done via this applet ..
Wolfgang
On 8/7/2023 4:23 PM, Samuel Sieb wrote:
On 8/7/23 13:18, Bill Cunningham wrote:
Sometime ago I wrote to this list about network connection problems. I reinstalled my fedora server and all was fine. Well I reinstall a windows system and had to fix grub2. So I booted F38 server and this is the error I got.
Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
I did nothing to the system and all I tried to run was 'dnf distro-sync' for updates. Is this grub2 related? Since it had to be reinstalled from scratch? The system has always been there I just cleared and reinstalled a Windows on another partition and thusly had to reinstall a new grub2 bootloader. It boots fine.
grub is merely to get the OS loaded, it does nothing after. You have some sort of DNS issue, either with the Fedora install or with your network. Can you resolve any other sites?
ping 8.8.8.8 returns 'network connection unreachable'
ping www.google.com returns there is a DNS error.
If this tell you anything.
B
On 8/7/23 13:30, Bill Cunningham wrote:
On 8/7/2023 4:23 PM, Samuel Sieb wrote:
On 8/7/23 13:18, Bill Cunningham wrote:
Sometime ago I wrote to this list about network connection problems. I reinstalled my fedora server and all was fine. Well I reinstall a windows system and had to fix grub2. So I booted F38 server and this is the error I got.
Errors during downloading metadata for repository 'fedora': - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org] Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-38&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
I did nothing to the system and all I tried to run was 'dnf distro-sync' for updates. Is this grub2 related? Since it had to be reinstalled from scratch? The system has always been there I just cleared and reinstalled a Windows on another partition and thusly had to reinstall a new grub2 bootloader. It boots fine.
grub is merely to get the OS loaded, it does nothing after. You have some sort of DNS issue, either with the Fedora install or with your network. Can you resolve any other sites?
ping 8.8.8.8 returns 'network connection unreachable'
ping www.google.com returns there is a DNS error.
If this tell you anything.
Ok, so you really don't have any network access. Are you on wifi or ethernet? Does it show as connected?
-
Bill Cunningham -
Felix Miata -
Samuel Sieb -
Wolfgang Pfeiffer