Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Fri, 2020-05-08 at 00:23 -0700, Samuel Sieb wrote: > It's a standard, but I don't think NetworkManager will switch to it > automatically. However, there is an option in the network settings > to pick "link-local" which is that. As far as I recall, if you boot up an unconfigured / default configuration Fedora installation, and it tries to connect to a DHCP server but can't (such as the server was down), it will eventually use link-local addresses. I seem to remember that zeroconf (which uses those addresses), is part of a default installation. And, as I seem to recall that if you booted up Fedora preconfigured to use DHCP network settings, but it couldn't find a DHCP server, it just didn't get an IP assigned to it. I can't test either of these at the moment. -- uname -rsvp Linux 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/8/20 12:04 AM, John M. Harris Jr wrote: On Thursday, May 7, 2020 10:27:29 PM MST Tim via users wrote: In the absense of DHCP, there's autoconfig, where each device randomly picks an IP out of the link-local 169.254.0.0 to 169.254.255.255 range of addresses, checks to see if it's not already use, then adopts it, or cycles through picking another until it finds one that's free. I've never seen that on any Linux distro. Is that what Workstation does? Do you know why? I've always known that to be a Windows thing. It's a standard, but I don't think NetworkManager will switch to it automatically. However, there is an option in the network settings to pick "link-local" which is that. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Thu, May 7, 2020 at 8:52 PM Samuel Sieb wrote: > On 5/7/20 9:08 AM, Tom H wrote: >> On Thu, May 7, 2020 Tom Horsley wrote: >>> On Wed, 06 May 2020 John M. Harris Jr wrote: This solved it, thank you! >>> >>> If that solved it, you may not actually be using NetworkManager. >>> I have no files at all in /etc/sysconfig/network-scripts after >>> configuring my network with just NetworkManager (it must >>> store the info somewhere, but I have no idea where). >> >> Is it possible that "network-scripts" was in use in 31 and was >> uninstalled with the upgrade to 32 without NM being enabled and >> started?! > > You should probably read the entire thread before replying to older > messages. He found that there actually were files in there. I read and reply to messages chronologically. From what I've now read, rebooting fixed the problem. Wonderful :) > Also, it doesn't matter if you have the "network-scripts" package > or not, that is still the location for most network configs. Did I imply otherwise?! ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Thursday, May 7, 2020 10:27:29 PM MST Tim via users wrote: > Tim: > > >> When you're installing a system, Anaconda gives you the chance to > >> manually configure some network details *for* the installation > >> routine to use during installation. These settings are temporary, > >> they don't write a configuration for the installed system to use, > >> later on. And if you're on a network with a DHCP server that will > >> automatically assign working addresses, you don't have to do > >> anything at this point, the DHCP system will set things up for you. > >> > >> > >> > >> During first boot of the installed system, you're given a chance to > >> manually control network settings for the newly installed system. > > > > John M. Harris Jr: > > > Odd, I don't think that's ever been the case before. I might be > > thinking of RHEL/CentOS. I don't use DHCP, but I've never had to do > > any manual configuration afterwards.. > > > I've been using Fedora since before it was Fedora, and CentOS since I > don't know when (several years), it's always been the way I described > it. At first I couldn't figure out why, after carefully configuring > network settings when starting off the the installation, the settings > weren't what I expected them to be. But it didn't take long to find > out that they were only used by the installer routine for itself. > > What's your network comprised of? All systems on my network have static IPs. > In the absense of DHCP, there's autoconfig, where each device randomly > picks an IP out of the link-local 169.254.0.0 to 169.254.255.255 range > of addresses, checks to see if it's not already use, then adopts it, or > cycles through picking another until it finds one that's free. I've never seen that on any Linux distro. Is that what Workstation does? Do you know why? I've always known that to be a Windows thing. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
Tim: >> When you're installing a system, Anaconda gives you the chance to >> manually configure some network details *for* the installation >> routine to use during installation. These settings are temporary, >> they don't write a configuration for the installed system to use, >> later on. And if you're on a network with a DHCP server that will >> automatically assign working addresses, you don't have to do >> anything at this point, the DHCP system will set things up for you. >> >> During first boot of the installed system, you're given a chance to >> manually control network settings for the newly installed system. John M. Harris Jr: > Odd, I don't think that's ever been the case before. I might be > thinking of RHEL/CentOS. I don't use DHCP, but I've never had to do > any manual configuration afterwards.. I've been using Fedora since before it was Fedora, and CentOS since I don't know when (several years), it's always been the way I described it. At first I couldn't figure out why, after carefully configuring network settings when starting off the the installation, the settings weren't what I expected them to be. But it didn't take long to find out that they were only used by the installer routine for itself. What's your network comprised of? In the absense of DHCP, there's autoconfig, where each device randomly picks an IP out of the link-local 169.254.0.0 to 169.254.255.255 range of addresses, checks to see if it's not already use, then adopts it, or cycles through picking another until it finds one that's free. And if your PC was a solo computer on no LAN, it would do that, too. As well as simply using 127.0.0.1 as itself. -- uname -rsvp Linux 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 2020-05-08 12:43, Samuel Sieb wrote: > On 5/7/20 9:30 PM, John M. Harris Jr wrote: >> On Wednesday, May 6, 2020 11:43:59 PM MST Tim via users wrote: >>> During first boot of the installed system, you're given a chance to >>> manually control network settings for the newly installed system. >> >> Odd, I don't think that's ever been the case before. I might be thinking of >> RHEL/CentOS. I don't use DHCP, but I've never had to do any manual >> configuration afterwards.. > > If you don't create a user during the install, then there's a firstboot > process that runs to let you create one. I think the wifi config can be done > at that point as well. Ethernet is either automatic or whatever was set > during the install. I've never setup or changed anything, so I can't say > which way it is. (So I might have been wrong about the installer not setting > the network config.) The "issue" of setting up a network on a new install hasn't affected me at all. So, I've not committed to memory the variations depending on the spin. So, this may well be inaccurate. Workstation Live Install - No options to configure the network or hostname. The wired network will be on and functional with DHCP. Best know how to change hostname after the install. KDE Live Install - No optons to configure the network, but you can set a hostname. You can also set password for root and configure a user with a UID and GID of your choice as well as assign the user to the wheel group. Netinstall Everything - You can configure the network fully, including a Wifi connection. Not sure how user creation is taken care of. Haven't done this type of install in a while. Something to do this afternoon? -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/7/20 9:30 PM, John M. Harris Jr wrote: On Wednesday, May 6, 2020 11:43:59 PM MST Tim via users wrote: During first boot of the installed system, you're given a chance to manually control network settings for the newly installed system. Odd, I don't think that's ever been the case before. I might be thinking of RHEL/CentOS. I don't use DHCP, but I've never had to do any manual configuration afterwards.. If you don't create a user during the install, then there's a firstboot process that runs to let you create one. I think the wifi config can be done at that point as well. Ethernet is either automatic or whatever was set during the install. I've never setup or changed anything, so I can't say which way it is. (So I might have been wrong about the installer not setting the network config.) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 11:43:59 PM MST Tim via users wrote: > On Wed, 2020-05-06 at 15:42 -0700, John M. Harris Jr wrote: > > > Apparently, nothing.. "no such connection profile". That's pretty > > odd, this was configured using NetworkManager in the Anaconda GUI. > > > When you're installing a system, Anaconda gives you the chance to > manually configure some network details *for* the installation routine > to use during installation. These settings are temporary, they don't > write a configuration for the installed system to use, later on. And > if you're on a network with a DHCP server that will automatically > assign working addresses, you don't have to do anything at this point, > the DHCP system will set things up for you. > > During first boot of the installed system, you're given a chance to > manually control network settings for the newly installed system. > > -- > > uname -rsvp > Linux 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 > > Boilerplate: All unexpected mail to my mailbox is automatically deleted. > I will only get to see the messages that are posted to the mailing list. Odd, I don't think that's ever been the case before. I might be thinking of RHEL/CentOS. I don't use DHCP, but I've never had to do any manual configuration afterwards.. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/7/20 9:08 AM, Tom H wrote: On Thu, May 7, 2020 Tom Horsley wrote: On Wed, 06 May 2020 John M. Harris Jr wrote: This solved it, thank you! If that solved it, you may not actually be using NetworkManager. I have no files at all in /etc/sysconfig/network-scripts after configuring my network with just NetworkManager (it must store the info somewhere, but I have no idea where). Is it possible that "network-scripts" was in use in 31 and was uninstalled with the upgrade to 32 without NM being enabled and started?! You should probably read the entire thread before replying to older messages. He found that there actually were files in there. Also, it doesn't matter if you have the "network-scripts" package or not, that is still the location for most network configs. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/7/20 9:06 AM, Tom H wrote: On Thu, May 7, 2020 at 12:21 AM Samuel Sieb wrote: On 5/6/20 3:10 PM, John M. Harris Jr wrote: On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: Are you using NetworkManager or something else? What do you mean they aren't being read? What is happening or not happening? I'm using NetworkManager. The interface is present, with the correct name, but didn't get an IP address assigned. My ethernet port is called enp0s25, change the following command as necessary. Run "nmcli c show enp0s25" to see what NetworkManager knows about the connection. See if there's anything missing. You can't assume that the NIC and the connction have the same name. And there's no way to run "nmcli c s" against a NIC name. Yes, as Ed reminded me, you should use "nmcli c" to find the connection before trying to get the information. Which, of course, is what I had done myself, but didn't think to add that to my reply. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Thu, May 7, 2020 at 1:14 AM Samuel Sieb wrote: > On 5/6/20 3:55 PM, Tom Horsley wrote: >> On Wed, 6 May 2020 15:34:09 -0700 Samuel Sieb wrote: >>> >>> I have no network-scripts package, but everything still goes into >>> /etc/sysconfig/network-scripts. >> >> Weird. I thought there was nothing there, at least when I first >> ran the live image, but it does have files stored there now >> that I've got everything configured. > > The install process doesn't create any network connections on the > installed system. I just installed "Server" and the static config that I set in Anaconda was transferred to the installed system. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Thu, May 7, 2020 Tom Horsley wrote: > On Wed, 06 May 2020 John M. Harris Jr wrote: > >> This solved it, thank you! > > If that solved it, you may not actually be using NetworkManager. > I have no files at all in /etc/sysconfig/network-scripts after > configuring my network with just NetworkManager (it must > store the info somewhere, but I have no idea where). Is it possible that "network-scripts" was in use in 31 and was uninstalled with the upgrade to 32 without NM being enabled and started?! ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Thu, May 7, 2020 at 12:21 AM Samuel Sieb wrote:
> On 5/6/20 3:10 PM, John M. Harris Jr wrote:
>> On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote:
>>>
>>> Are you using NetworkManager or something else?
>>> What do you mean they aren't being read? What is happening or not
>>> happening?
>>
>> I'm using NetworkManager. The interface is present, with the
>> correct name, but didn't get an IP address assigned.
>
> My ethernet port is called enp0s25, change the following command as
> necessary. Run "nmcli c show enp0s25" to see what NetworkManager
> knows about the connection. See if there's anything missing.
You can't assume that the NIC and the connction have the same name.
And there's no way to run "nmcli c s" against a NIC name.
But, if you have one NIC,
nmcli c s path 1
or
nmcli c s apath 1
should list the connection's properties. ("path" is the DBus
connection path and "apath" is the DBus active connection path.)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Thu, May 7, 2020 at 12:12 AM John M. Harris Jr wrote: > On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: >> On 5/6/20 2:46 PM, John M. Harris Jr wrote: >> >>> Anyone know if this is just broken now, and what the workaround is >>> if so? I'm fine manually setting it on boot for now, but this is >>> causing a lot of issues.. >> >> Are you using NetworkManager or something else? >> What do you mean they aren't being read? What is happening or not >> happening? > > I'm using NetworkManager. The interface is present, with the correct > name, but didn't get an IP address assigned. Does journalctl -u NetworkManager show more details than systemctl status NetworkManager Does nmcli c s list any connections? For any connection, does the output of nmcli c s id give any clue as to why it's not up? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Thu, May 7, 2020 Tom Horsley wrote: > On Wed, 06 May 2020 John M. Harris Jr wrote: > > > Anyone know if this is just broken now, and what the workaround is if so? > > I'm > > fine manually setting it on boot for now, but this is causing a lot of > > issues.. > > > > Probably don't have network-scripts installed. Ever since about fedora > 29 I think they haven't shipped network-scripts by default, you have > to fetch them via: > > dnf install network-scripts Please no; network-scripts is a deprecated package. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wed, May 6, 2020 John M. Harris Jr wrote: > > Anyone know if this is just broken now, and what the workaround is > if so? I'm fine manually setting it on boot for now, but this is > causing a lot of issues.. 1) Did you NIC name change? Compare ip l and ls /etc/sysconfig/network-scripts 2) Was NM disabled for some reason? systemctl status NetworkManager ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wed, 2020-05-06 at 15:42 -0700, John M. Harris Jr wrote: > Apparently, nothing.. "no such connection profile". That's pretty > odd, this was configured using NetworkManager in the Anaconda GUI. When you're installing a system, Anaconda gives you the chance to manually configure some network details *for* the installation routine to use during installation. These settings are temporary, they don't write a configuration for the installed system to use, later on. And if you're on a network with a DHCP server that will automatically assign working addresses, you don't have to do anything at this point, the DHCP system will set things up for you. During first boot of the installed system, you're given a chance to manually control network settings for the newly installed system. -- uname -rsvp Linux 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 2020-05-07 08:00, John M. Harris Jr wrote: > On Wednesday, May 6, 2020 4:41:27 PM MST John M. Harris Jr wrote: >> On Wednesday, May 6, 2020 4:10:56 PM MST John M. Harris Jr wrote: >> >>> "Wired connection 1".. >> >> Looking into this some more, looks like NetworkManager doesn't recognize >> that it's associated with an actual device, which I imagine is why it's >> not coming up on boot.. I may be horribly wrong, I'm not incredibly >> familiar with NetworkManager. > Well, rebooted and now NetworkManager recognizes that it's enp1s0, and it > works without network-scripts installed. Don't know what changed, but I'll > take it. > FWIW, you can do sudo nmcli connection modify Wired\ connection\ 1 connection.id eth0 to change the name to "eth0" or whatever you like to make it easier. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 5:05:10 PM MST Robert Moskowitz wrote: > On 5/6/20 7:13 PM, Samuel Sieb wrote: > > > On 5/6/20 3:55 PM, Tom Horsley wrote: > > > >> On Wed, 6 May 2020 15:34:09 -0700 > >> Samuel Sieb wrote: > >> > >> > >> > >>> I have no network-scripts package, but everything still goes into > >>> /etc/sysconfig/network-scripts. > >> > >> > >> > >> Weird. I thought there was nothing there, at least when I first > >> ran the live image, but it does have files stored there now > >> that I've got everything configured. > > > > > > > > The install process doesn't create any network connections on the > > installed system. > > > I think this is part of firstboot. > > I used my ethernet for install and first manual package installs. I > have a broadcom wifi that I need the broadcom-wl installed so a bit of > chicken and egg. But as I shared I have the network-script files. Sorry, yep it is part of firstboot. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 7:13 PM, Samuel Sieb wrote: On 5/6/20 3:55 PM, Tom Horsley wrote: On Wed, 6 May 2020 15:34:09 -0700 Samuel Sieb wrote: I have no network-scripts package, but everything still goes into /etc/sysconfig/network-scripts. Weird. I thought there was nothing there, at least when I first ran the live image, but it does have files stored there now that I've got everything configured. The install process doesn't create any network connections on the installed system. I think this is part of firstboot. I used my ethernet for install and first manual package installs. I have a broadcom wifi that I need the broadcom-wl installed so a bit of chicken and egg. But as I shared I have the network-script files. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 4:41:27 PM MST John M. Harris Jr wrote: > On Wednesday, May 6, 2020 4:10:56 PM MST John M. Harris Jr wrote: > > > On Wednesday, May 6, 2020 3:59:32 PM MST Samuel Sieb wrote: > > > > > > > On 5/6/20 3:48 PM, Ed Greshko wrote: > > > > > > > > > > > > > On 2020-05-07 06:19, Samuel Sieb wrote: > > > > > > > > > > > > > > > >> On 5/6/20 3:10 PM, John M. Harris Jr wrote: > > > >> > > > >> > > > >> > > > >>> On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: > > > >>> > > > >>> > > > >>> > > > On 5/6/20 2:46 PM, John M. Harris Jr wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Anyone know if this is just broken now, and what the workaround > > > > is > > > > if > > > > so? > > > > I'm fine manually setting it on boot for now, but this is causing > > > > a > > > > lot > > > > of issues.. > > > > > > > > > > > > > > > > > > > > > > > > > > > Are you using NetworkManager or something else? > > > What do you mean they aren't being read? What is happening or not > > > happening? > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> I'm using NetworkManager. The interface is present, with the > > > >>> correct > > > >>> name, but didn't get an IP address assigned. > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> My ethernet port is called enp0s25, change the following command as > > > >> necessary. Run "nmcli c show enp0s25" to see what NetworkManager > > > >> knows > > > >> about the connection. See if there's anything missing. > > > > > > > > > > > > > > > > > > > > > > > I would first run just "nmcli c" to see what the name of the > > > > connection > > > > is. The name is often not equal to the device. > > > > > > > > > > > > > > > Thank you, that's a good point, considering I did exactly that to find > > > out mine... > > > > > > > > Useful info, that returned that it is actually managed by NetworkManager, > > as > > > "Wired connection 1".. > > > Looking into this some more, looks like NetworkManager doesn't recognize > that it's associated with an actual device, which I imagine is why it's > not coming up on boot.. I may be horribly wrong, I'm not incredibly > familiar with NetworkManager. Well, rebooted and now NetworkManager recognizes that it's enp1s0, and it works without network-scripts installed. Don't know what changed, but I'll take it. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 4:10:56 PM MST John M. Harris Jr wrote: > On Wednesday, May 6, 2020 3:59:32 PM MST Samuel Sieb wrote: > > > On 5/6/20 3:48 PM, Ed Greshko wrote: > > > > > > > On 2020-05-07 06:19, Samuel Sieb wrote: > > > > > > > > >> On 5/6/20 3:10 PM, John M. Harris Jr wrote: > > >> > > >> > > >>> On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: > > >>> > > >>> > > On 5/6/20 2:46 PM, John M. Harris Jr wrote: > > > > > > > > > > > > > Anyone know if this is just broken now, and what the workaround is > > > if > > > so? > > > I'm fine manually setting it on boot for now, but this is causing a > > > lot > > > of issues.. > > > > > > > > > > > > > > Are you using NetworkManager or something else? > > What do you mean they aren't being read? What is happening or not > > happening? > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> I'm using NetworkManager. The interface is present, with the correct > > >>> name, but didn't get an IP address assigned. > > >> > > >> > > >> > > >> > > >> > > >> My ethernet port is called enp0s25, change the following command as > > >> necessary. Run "nmcli c show enp0s25" to see what NetworkManager > > >> knows > > >> about the connection. See if there's anything missing. > > > > > > > > > > > > I would first run just "nmcli c" to see what the name of the connection > > > is. The name is often not equal to the device. > > > > > > > > Thank you, that's a good point, considering I did exactly that to find > > out mine... > > > Useful info, that returned that it is actually managed by NetworkManager, as > "Wired connection 1".. Looking into this some more, looks like NetworkManager doesn't recognize that it's associated with an actual device, which I imagine is why it's not coming up on boot.. I may be horribly wrong, I'm not incredibly familiar with NetworkManager. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 4:18 PM, Tom Horsley wrote: On Wed, 6 May 2020 16:13:50 -0700 Samuel Sieb wrote: The install process doesn't create any network connections on the installed system. But I was able to access the network :-). NetworkManager will automatically configure an ethernet connection if it finds one. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 4:09 PM, John M. Harris Jr wrote: On Wednesday, May 6, 2020 3:21:46 PM MST Samuel Sieb wrote: On 5/6/20 3:15 PM, John M. Harris Jr wrote: While this did solve it, I wonder why it was working in F31, but stopped in F32, if that was the issue. There should probably be a warning upon upgrade, or something like that, because using /etc/sysconfig/network-scripts is not at all uncommon.. You installed "network-scripts" and that made it work? That package is deprecated and going away soon. You should make sure it works without that. Well, that's just more confusing as it turns out.. I configured this one with the GUI in Anaconda, but this is where it put the connection info. The only thing I've got in /etc/NetworkManager/system-connections/ is a VPN configuration. I installed this system as F31 via KDE Spin's installer, if that makes a difference. Careful, I think you're confusing two things here. There's the "network-scripts" package that contains some scripts for "ifup/down", etc. Those scripts shouldn't be used and are going away. They will give you a warning if you run them. NetworkManager provides it's own versions of "ifup/down" that are just wrappers for "nmcli". Then there's the directory /etc/sysconfig/network-scripts that contains the ifcfg-* files. That is not going away and NetworkManager reads interface info from there. /etc/NetworkManager/system-connections/ is kind of the native config for NetworkManager and at least VPNs get put there. Other distributions use that more, probably because ifcfg-* is a historical Redhat thing. As far as I know, the installer doesn't create any network connection configs for the installed system. Those get created when you start it. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wed, 6 May 2020 16:13:50 -0700 Samuel Sieb wrote: > The install process doesn't create any network connections on the > installed system. But I was able to access the network :-). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 3:55 PM, Tom Horsley wrote: On Wed, 6 May 2020 15:34:09 -0700 Samuel Sieb wrote: I have no network-scripts package, but everything still goes into /etc/sysconfig/network-scripts. Weird. I thought there was nothing there, at least when I first ran the live image, but it does have files stored there now that I've got everything configured. The install process doesn't create any network connections on the installed system. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 3:59:32 PM MST Samuel Sieb wrote: > On 5/6/20 3:48 PM, Ed Greshko wrote: > > > On 2020-05-07 06:19, Samuel Sieb wrote: > > > >> On 5/6/20 3:10 PM, John M. Harris Jr wrote: > >> > >>> On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: > >>> > On 5/6/20 2:46 PM, John M. Harris Jr wrote: > > > > > Anyone know if this is just broken now, and what the workaround is if > > so? > > I'm fine manually setting it on boot for now, but this is causing a > > lot > > of issues.. > > > > > Are you using NetworkManager or something else? > What do you mean they aren't being read? What is happening or not > happening? > >>> > >>> > >>> > >>> I'm using NetworkManager. The interface is present, with the correct > >>> name, but didn't get an IP address assigned. > >> > >> > >> > >> My ethernet port is called enp0s25, change the following command as > >> necessary. Run "nmcli c show enp0s25" to see what NetworkManager knows > >> about the connection. See if there's anything missing. > > > > > I would first run just "nmcli c" to see what the name of the connection > > is. The name is often not equal to the device. > > > Thank you, that's a good point, considering I did exactly that to find > out mine... Useful info, that returned that it is actually managed by NetworkManager, as "Wired connection 1".. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 3:21:46 PM MST Samuel Sieb wrote: > On 5/6/20 3:15 PM, John M. Harris Jr wrote: > > > On Wednesday, May 6, 2020 3:01:28 PM MST Tom Horsley wrote: > > > >> On Wed, 06 May 2020 14:46:35 -0700 > >> John M. Harris Jr wrote: > >> > >>> Anyone know if this is just broken now, and what the workaround is if > >>> so? > >>> I'm fine manually setting it on boot for now, but this is causing a > >>> lot > >>> of issues.. > >> > >> > >> > >> Probably don't have network-scripts installed. Ever since about fedora > >> 29 I think they haven't shipped network-scripts by default, you have > >> to fetch them via: > >> > >> > >> > >> dnf install network-scripts > >> > >> > >> > >> (which can be tricky if you have no network :-). > >> > >> > >> > >> I finally gave up and after a monster struggle got my networking > >> functioning with just NetworkManager when I installed fedora 32. > > > > > > While this did solve it, I wonder why it was working in F31, but stopped > > in F32, if that was the issue. There should probably be a warning upon > > upgrade, or something like that, because using > > /etc/sysconfig/network-scripts is not at all uncommon.. > > > You installed "network-scripts" and that made it work? That package is > deprecated and going away soon. You should make sure it works without that. Well, that's just more confusing as it turns out.. I configured this one with the GUI in Anaconda, but this is where it put the connection info. The only thing I've got in /etc/NetworkManager/system-connections/ is a VPN configuration. I installed this system as F31 via KDE Spin's installer, if that makes a difference. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 3:48 PM, Ed Greshko wrote: On 2020-05-07 06:19, Samuel Sieb wrote: On 5/6/20 3:10 PM, John M. Harris Jr wrote: On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: On 5/6/20 2:46 PM, John M. Harris Jr wrote: Anyone know if this is just broken now, and what the workaround is if so? I'm fine manually setting it on boot for now, but this is causing a lot of issues.. Are you using NetworkManager or something else? What do you mean they aren't being read? What is happening or not happening? I'm using NetworkManager. The interface is present, with the correct name, but didn't get an IP address assigned. My ethernet port is called enp0s25, change the following command as necessary. Run "nmcli c show enp0s25" to see what NetworkManager knows about the connection. See if there's anything missing. I would first run just "nmcli c" to see what the name of the connection is. The name is often not equal to the device. Thank you, that's a good point, considering I did exactly that to find out mine... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wed, 6 May 2020 15:34:09 -0700 Samuel Sieb wrote: > I have no network-scripts package, but everything still goes into > /etc/sysconfig/network-scripts. Weird. I thought there was nothing there, at least when I first ran the live image, but it does have files stored there now that I've got everything configured. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 2020-05-07 06:19, Samuel Sieb wrote: > On 5/6/20 3:10 PM, John M. Harris Jr wrote: >> On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: >>> On 5/6/20 2:46 PM, John M. Harris Jr wrote: >>> Anyone know if this is just broken now, and what the workaround is if so? I'm fine manually setting it on boot for now, but this is causing a lot of issues.. >>> >>> >>> Are you using NetworkManager or something else? >>> What do you mean they aren't being read? What is happening or not >>> happening? >> >> I'm using NetworkManager. The interface is present, with the correct name, >> but >> didn't get an IP address assigned. > > My ethernet port is called enp0s25, change the following command as > necessary. Run "nmcli c show enp0s25" to see what NetworkManager knows about > the connection. See if there's anything missing. I would first run just "nmcli c" to see what the name of the connection is. The name is often not equal to the device. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 3:19:42 PM MST Samuel Sieb wrote: > On 5/6/20 3:10 PM, John M. Harris Jr wrote: > > > On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: > > > >> On 5/6/20 2:46 PM, John M. Harris Jr wrote: > >> > >> > >> > >>> Anyone know if this is just broken now, and what the workaround is if > >>> so? > >>> I'm fine manually setting it on boot for now, but this is causing a lot > >>> of issues.. > >> > >> > >> > >> > >> Are you using NetworkManager or something else? > >> What do you mean they aren't being read? What is happening or not > >> happening? > > > > > > I'm using NetworkManager. The interface is present, with the correct name, > > but didn't get an IP address assigned. > > > My ethernet port is called enp0s25, change the following command as > necessary. Run "nmcli c show enp0s25" to see what NetworkManager knows > about the connection. See if there's anything missing. Apparently, nothing.. "no such connection profile". That's pretty odd, this was configured using NetworkManager in the Anaconda GUI. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 3:25 PM, Tom Horsley wrote: On Wed, 06 May 2020 15:13:27 -0700 John M. Harris Jr wrote: This solved it, thank you! If that solved it, you may not actually be using NetworkManager. I have no files at all in /etc/sysconfig/network-scripts after configuring my network with just NetworkManager (it must store the info somewhere, but I have no idea where). Check in /etc/NetworkManager/system-connections/ I have no network-scripts package, but everything still goes into /etc/sysconfig/network-scripts. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wed, 06 May 2020 15:13:27 -0700 John M. Harris Jr wrote: > This solved it, thank you! If that solved it, you may not actually be using NetworkManager. I have no files at all in /etc/sysconfig/network-scripts after configuring my network with just NetworkManager (it must store the info somewhere, but I have no idea where). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 3:15 PM, John M. Harris Jr wrote: On Wednesday, May 6, 2020 3:01:28 PM MST Tom Horsley wrote: On Wed, 06 May 2020 14:46:35 -0700 John M. Harris Jr wrote: Anyone know if this is just broken now, and what the workaround is if so? I'm fine manually setting it on boot for now, but this is causing a lot of issues.. Probably don't have network-scripts installed. Ever since about fedora 29 I think they haven't shipped network-scripts by default, you have to fetch them via: dnf install network-scripts (which can be tricky if you have no network :-). I finally gave up and after a monster struggle got my networking functioning with just NetworkManager when I installed fedora 32. While this did solve it, I wonder why it was working in F31, but stopped in F32, if that was the issue. There should probably be a warning upon upgrade, or something like that, because using /etc/sysconfig/network-scripts is not at all uncommon.. You installed "network-scripts" and that made it work? That package is deprecated and going away soon. You should make sure it works without that. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 3:10 PM, John M. Harris Jr wrote: On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: On 5/6/20 2:46 PM, John M. Harris Jr wrote: Anyone know if this is just broken now, and what the workaround is if so? I'm fine manually setting it on boot for now, but this is causing a lot of issues.. Are you using NetworkManager or something else? What do you mean they aren't being read? What is happening or not happening? I'm using NetworkManager. The interface is present, with the correct name, but didn't get an IP address assigned. My ethernet port is called enp0s25, change the following command as necessary. Run "nmcli c show enp0s25" to see what NetworkManager knows about the connection. See if there's anything missing. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 3:01:28 PM MST Tom Horsley wrote: > On Wed, 06 May 2020 14:46:35 -0700 > John M. Harris Jr wrote: > > > > Anyone know if this is just broken now, and what the workaround is if so? > > I'm fine manually setting it on boot for now, but this is causing a lot > > of issues.. > > > > > Probably don't have network-scripts installed. Ever since about fedora > 29 I think they haven't shipped network-scripts by default, you have > to fetch them via: > > dnf install network-scripts > > (which can be tricky if you have no network :-). > > I finally gave up and after a monster struggle got my networking > functioning with just NetworkManager when I installed fedora 32. While this did solve it, I wonder why it was working in F31, but stopped in F32, if that was the issue. There should probably be a warning upon upgrade, or something like that, because using /etc/sysconfig/network-scripts is not at all uncommon.. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 3:01:28 PM MST Tom Horsley wrote: > On Wed, 06 May 2020 14:46:35 -0700 > John M. Harris Jr wrote: > > > > Anyone know if this is just broken now, and what the workaround is if so? > > I'm fine manually setting it on boot for now, but this is causing a lot > > of issues.. > > > > > Probably don't have network-scripts installed. Ever since about fedora > 29 I think they haven't shipped network-scripts by default, you have > to fetch them via: > > dnf install network-scripts > > (which can be tricky if you have no network :-). > > I finally gave up and after a monster struggle got my networking > functioning with just NetworkManager when I installed fedora 32. This solved it, thank you! -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wednesday, May 6, 2020 2:50:27 PM MST Samuel Sieb wrote: > On 5/6/20 2:46 PM, John M. Harris Jr wrote: > > > Anyone know if this is just broken now, and what the workaround is if so? > > I'm fine manually setting it on boot for now, but this is causing a lot > > of issues.. > > > Are you using NetworkManager or something else? > What do you mean they aren't being read? What is happening or not > happening? I'm using NetworkManager. The interface is present, with the correct name, but didn't get an IP address assigned. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 5:46 PM, John M. Harris Jr wrote: Anyone know if this is just broken now, and what the workaround is if so? I'm fine manually setting it on boot for now, but this is causing a lot of issues.. "out of the box F32 workstation with Xfce" I am assuming these were created by NetworkManager: # cat /etc/sysconfig/network-scripts/ifcfg-enp3s0 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=enp3s0 UUID=ab051ba5-5260-3f64-a8d2-a887ffe75e21 DEVICE=enp3s0 ONBOOT=yes AUTOCONNECT_PRIORITY=-999 # cat /etc/sysconfig/network-scripts/ifcfg-HTTNET ESSID=HTTNET MODE=Managed KEY_MGMT=WPA-PSK SECURITYMODE=open MAC_ADDRESS_RANDOMIZATION=default TYPE=Wireless PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=HTTNET UUID=e7cef733-fb8d-4646-b102-089358705a02 DEVICE=wlp1s0 ONBOOT=yes USERS=rgm And this one has a key-HTTNET ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On Wed, 06 May 2020 14:46:35 -0700 John M. Harris Jr wrote: > Anyone know if this is just broken now, and what the workaround is if so? I'm > fine manually setting it on boot for now, but this is causing a lot of > issues.. > Probably don't have network-scripts installed. Ever since about fedora 29 I think they haven't shipped network-scripts by default, you have to fetch them via: dnf install network-scripts (which can be tricky if you have no network :-). I finally gave up and after a monster struggle got my networking functioning with just NetworkManager when I installed fedora 32. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: /etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
On 5/6/20 2:46 PM, John M. Harris Jr wrote: Anyone know if this is just broken now, and what the workaround is if so? I'm fine manually setting it on boot for now, but this is causing a lot of issues.. Are you using NetworkManager or something else? What do you mean they aren't being read? What is happening or not happening? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
/etc/sysconfig/network-scripts/ifcfg-* not read after upgrade to F32
Anyone know if this is just broken now, and what the workaround is if so? I'm fine manually setting it on boot for now, but this is causing a lot of issues.. -- John M. Harris, Jr. Splentity ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
