Re: [CentOS] After upgrade to CentOS 8.1 default gateway missing
> On Fri, 17 Jan 2020 14:39:19 +0100, Simon Matter via CentOS > wrote: > >> Anything in the logs about what was going on? If you reboot this server >> again and again, does the problem show up again? > > This is shared hosting servers that is in production with customers live > sites. So I don't want to reboot again if not absolutely needed. I guess I > will find out if the problem continues the next time there is a new > kernel. I would like to avoid doing reboots before a new kernel is > released. > > I have not had time to go over the logs yet. > > I was hoping that somone else experienced the same, but it does not seems > so. I can't believe I would be the only one in the world this would happen > to, and also that it happened on both my CentOS 8 servers. Such things happened to me in the past as well and I couldn't believe I'm the only one. But, you have to consider certain things: 1) CentOS 8 is very new and I don't think it has already widely reached the production world. I usually don't do this before .2 comes out and I feel I'm not alone with this rule. At least it has served me well in the last decade or two. 2) The number of production servers running two different IPv4 networks on two adapters, as you do, may be quite small compared to the big number of simple settings. 3) A lot of serious production servers are still using good old init scripts to handle network settings and interfaces. Now that we're almost forced to move to the more modern approach with NetworkManager and systemd, new issues will slowly appear and get fixed step by step. Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 and E1000 intel driver
At 03:27 PM 1/17/2020, Akemi Yagi wrote: On Fri, Jan 17, 2020 at 3:16 PM david wrote: > > Folks > > I know that support for the network adaptors supported by the 'e1000' > driver have been removed from the base distribution. However, I have > exactly that controller (Broadcom Gigabit Ethernet PCI, not > PCIe). Is there a way for me to add support for that on Centos > 8.1? Perhaps a driver in an RPM package? > > Thanks > > David The e1000 driver should be in the 8.1 kernel: $ modinfo e1000 filename: /lib/modules/4.18.0-147.3.1.el8_1.x86_64/kernel/drivers/net/ethernet/intel/e1000/e1000.ko.xz version:7.3.21-k8-NAPI license:GPL description:Intel(R) PRO/1000 Network Driver author: Intel Corporation, rhelversion:8.1 Akemi _ Akemi Thanks for the suggestion. Modinfo does produce that result. But "the network doesn't work". My environment is a VirtualBox VM of Centos 8 on top of Windows 10. I've defined a bridged adaptor. The hardware is the Broadcom adaptor, using DHCP. No firewall is running in Centos 8 yet. This exact configuration works fine with Centos 7. The symptom I see is that DHCP, Ping, DNS Lookup all work, but no data transfer seems to work. I tried a CURL command to a local web machine (works with Centos 7), and it just hangs. The web server does not see the request. When I switch the network adaptor (in the VM) to NAT, everything works, probably indicating that the selection of the adaptor is the problem. I used the NAT interface to complete the install. Do you have any ideas? David *** WHOA *** It appears that this is not a Centos issue. My other VM's have stopped working also. The common factor is the use of a Bridged Network in VirtualBox on Windows 10 updated last week. Based upon prior similar events, I'd guess it's a Windows screw-up. Oh well. David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Twin HDMI
On Fri, Jan 17, 2020 at 8:53 AM Mark (Netbook) wrote: > I have an Intel NUC7PJYH running CentOS 6.8. This is a NUC with standard > USB, 1GbE and 2*HDMI. FWIW, that has a Pentium Silver J2005, which has Intel® UHD Graphics 605 thats fairly new stuff, and centos 6 is pretty old now. -- -john r pierce recycling used bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 and E1000 intel driver
At 03:27 PM 1/17/2020, Akemi Yagi wrote: On Fri, Jan 17, 2020 at 3:16 PM david wrote: > > Folks > > I know that support for the network adaptors supported by the 'e1000' > driver have been removed from the base distribution. However, I have > exactly that controller (Broadcom Gigabit Ethernet PCI, not > PCIe). Is there a way for me to add support for that on Centos > 8.1? Perhaps a driver in an RPM package? > > Thanks > > David The e1000 driver should be in the 8.1 kernel: $ modinfo e1000 filename: /lib/modules/4.18.0-147.3.1.el8_1.x86_64/kernel/drivers/net/ethernet/intel/e1000/e1000.ko.xz version:7.3.21-k8-NAPI license:GPL description:Intel(R) PRO/1000 Network Driver author: Intel Corporation, rhelversion:8.1 Akemi _ Akemi Thanks for the suggestion. Modinfo does produce that result. But "the network doesn't work". My environment is a VirtualBox VM of Centos 8 on top of Windows 10. I've defined a bridged adaptor. The hardware is the Broadcom adaptor, using DHCP. No firewall is running in Centos 8 yet. This exact configuration works fine with Centos 7. The symptom I see is that DHCP, Ping, DNS Lookup all work, but no data transfer seems to work. I tried a CURL command to a local web machine (works with Centos 7), and it just hangs. The web server does not see the request. When I switch the network adaptor (in the VM) to NAT, everything works, probably indicating that the selection of the adaptor is the problem. I used the NAT interface to complete the install. Do you have any ideas? David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 and E1000 intel driver
On Fri, Jan 17, 2020 at 3:16 PM david wrote: > Folks > > I know that support for the network adaptors supported by the 'e1000' > driver have been removed from the base distribution. However, I have > exactly that controller (Broadcom Gigabit Ethernet PCI, not > PCIe). Is there a way for me to add support for that on Centos > 8.1? Perhaps a driver in an RPM package? > > e1000 is Intel, not Broadcom. Broadcom drivers are generally BCM something, like bcm5700 -- -john r pierce recycling used bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Twin HDMI
On 18/01/2020 3:53 am, Mark (Netbook) wrote: Hello, I have an Intel NUC7PJYH running CentOS 6.8. This is a NUC with standard USB, 1GbE and 2*HDMI. Installation was no problem providing acpi=off. The problem is that by default the two displays are mirrored and I can’t seem to separate them. I can only see one HDMI port from CentOS. I need to see both HDMI ports discreetly. Can you please help. It should be adjustable in the CentOS6 equivalent of System Preferences->Hardware->Displays -- Cheers Bill ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 and E1000 intel driver
On Fri, Jan 17, 2020 at 3:16 PM david wrote: > > Folks > > I know that support for the network adaptors supported by the 'e1000' > driver have been removed from the base distribution. However, I have > exactly that controller (Broadcom Gigabit Ethernet PCI, not > PCIe). Is there a way for me to add support for that on Centos > 8.1? Perhaps a driver in an RPM package? > > Thanks > > David The e1000 driver should be in the 8.1 kernel: $ modinfo e1000 filename: /lib/modules/4.18.0-147.3.1.el8_1.x86_64/kernel/drivers/net/ethernet/intel/e1000/e1000.ko.xz version:7.3.21-k8-NAPI license:GPL description:Intel(R) PRO/1000 Network Driver author: Intel Corporation, rhelversion:8.1 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Centos 8 and E1000 intel driver
Folks I know that support for the network adaptors supported by the 'e1000' driver have been removed from the base distribution. However, I have exactly that controller (Broadcom Gigabit Ethernet PCI, not PCIe). Is there a way for me to add support for that on Centos 8.1? Perhaps a driver in an RPM package? Thanks David ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] After upgrade to CentOS 8.1 default gateway missing
On Fri, 17 Jan 2020 at 07:37, Asle Ommundsen wrote: > > On Thu, 16 Jan 2020 15:34:43 +0100, Stephen John Smoogen > wrote: > > > On Thu, 16 Jan 2020 at 07:58, Asle Ommundsen > > wrote: > >> > >> Hi, > >> > >> Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after a > >> reboot of the first server the network was unavailable. In IPMI console > >> everything except the network was looking good. Network was unreachable. > >> No errors in NetworkManager. I also restarted NetworkManager, but it did > >> not help. Then I discovered that the default gateway suddenly was > >> missing. > >> > >> Then I rebooted the server one more time, but network was still down. > >> > >> Then both myself and a technician in my datcenter was debugging this (I > >> had to wake him up in the middle of the night, costing me a lot of > >> money), > >> without finding any reason for why the default gateway was missing after > >> reboot. > >> > >> Then we rebooted the server a third time, and all of a sudden the > >> problem > >> was gone and the default gateway was back. [...cut...] > > > In order to determine what is going on you need to give a lot more > > information. > > > > 1. How do these boxes get their network information? DHCP or static > > 2. If they are static, what controls the setting of ips: > > NetworkManager or network-scripts > > 3. If they are static, how are they set in > > /etc/sysconfig/network-scripts/ > > 4. Do the files in /etc/sysconfig/network-scripts list a GATEWAY= > > 5. If you are using network-manager, what does nmtui or the graphical > > tool say the gateway or default route is? > > Here is answers to your list. I have anonymized the some of the data: > Thank you for the detailed answers.. they eliminated most of the 'easy-to-fix' problems. If you do not have ipv6 you might want to turn that off as I have seen some problems where a router gives enough info to cause routing issues but shouldn't have. If you do have ipv6 and it works.. then never mind. The only other confused one i have seen is where eno1 and eno2 both have DEFROUTE=yes defined.. and you can't do that. Otherwise.. I am not sure and it will take going through the logs or repeating it happen to diagnose better. > 1) Static ip configuration > > 2) This should be NetworkManager. > nmcli output: > > eno1: connected to eno1 > inet4 1.1.1.234/29 > route4 1.1.1.232/29 > route4 0.0.0.0/0 > > eno2: connected to eno2 > inet4 192.168.0.5/24 > route4 192.168.0.0/24 > > [root@server ~]# nmcli d show | grep IP4.GATEWA > IP4.GATEWAY: 1.1.1.1.233 > > 3) > TYPE=Ethernet > PROXY_METHOD=none > BROWSER_ONLY=no > BOOTPROTO=none > DEFROUTE=yes > IPV4_FAILURE_FATAL=yes > IPV6INIT=yes > IPV6_AUTOCONF=yes > IPV6_DEFROUTE=yes > IPV6_FAILURE_FATAL=no > IPV6_ADDR_GEN_MODE=stable-privacy > NAME=eno1 > UUID=1f9ec889-3c64-470a-894b-05543ee44c29 > DEVICE=eno1 > ONBOOT=yes > IPADDR=1.1.1..234 > PREFIX=29 > GATEWAY=1.1.1.233 > IPV6_PRIVACY=no > > 4) Yes > > 5) > [root@server ~]# nmcli d show | grep IP4.GATEWA > IP4.GATEWAY: 1.1.1.233 > > nmtui shows the same gateway. > > Kind regards, > Asle Ommundsen > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Twin HDMI
Hello, I have an Intel NUC7PJYH running CentOS 6.8. This is a NUC with standard USB, 1GbE and 2*HDMI. Installation was no problem providing acpi=off. The problem is that by default the two displays are mirrored and I can’t seem to separate them. I can only see one HDMI port from CentOS. I need to see both HDMI ports discreetly. Can you please help. Regards, Mark Woolfson MW Consultancy Ltd Leeds LS18 4LY United Kingdom Tel: +44 113 259 1204 Mob: +44 786 065 2778 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] After upgrade to CentOS 8.1 default gateway missing
On Fri, 17 Jan 2020 14:39:19 +0100, Simon Matter via CentOS wrote: Anything in the logs about what was going on? If you reboot this server again and again, does the problem show up again? This is shared hosting servers that is in production with customers live sites. So I don't want to reboot again if not absolutely needed. I guess I will find out if the problem continues the next time there is a new kernel. I would like to avoid doing reboots before a new kernel is released. I have not had time to go over the logs yet. I was hoping that somone else experienced the same, but it does not seems so. I can't believe I would be the only one in the world this would happen to, and also that it happened on both my CentOS 8 servers. Kind regards, Asle Ommundsen ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] After upgrade to CentOS 8.1 default gateway missing
> On Thu, 16 Jan 2020 15:34:43 +0100, Stephen John Smoogen > wrote: > >> On Thu, 16 Jan 2020 at 07:58, Asle Ommundsen >> wrote: >>> >>> Hi, >>> >>> Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after >>> a >>> reboot of the first server the network was unavailable. In IPMI console >>> everything except the network was looking good. Network was >>> unreachable. >>> No errors in NetworkManager. I also restarted NetworkManager, but it >>> did >>> not help. Then I discovered that the default gateway suddenly was >>> missing. >>> >>> Then I rebooted the server one more time, but network was still down. >>> >>> Then both myself and a technician in my datcenter was debugging this (I >>> had to wake him up in the middle of the night, costing me a lot of >>> money), >>> without finding any reason for why the default gateway was missing >>> after >>> reboot. >>> >>> Then we rebooted the server a third time, and all of a sudden the >>> problem >>> was gone and the default gateway was back. [...cut...] > >> In order to determine what is going on you need to give a lot more >> information. >> >> 1. How do these boxes get their network information? DHCP or static >> 2. If they are static, what controls the setting of ips: >> NetworkManager or network-scripts >> 3. If they are static, how are they set in >> /etc/sysconfig/network-scripts/ >> 4. Do the files in /etc/sysconfig/network-scripts list a GATEWAY= >> 5. If you are using network-manager, what does nmtui or the graphical >> tool say the gateway or default route is? > > Here is answers to your list. I have anonymized the some of the data: > > 1) Static ip configuration > > 2) This should be NetworkManager. > nmcli output: > > eno1: connected to eno1 > inet4 1.1.1.234/29 > route4 1.1.1.232/29 > route4 0.0.0.0/0 > > eno2: connected to eno2 > inet4 192.168.0.5/24 > route4 192.168.0.0/24 > > [root@server ~]# nmcli d show | grep IP4.GATEWA > IP4.GATEWAY: 1.1.1.1.233 > > 3) > TYPE=Ethernet > PROXY_METHOD=none > BROWSER_ONLY=no > BOOTPROTO=none > DEFROUTE=yes > IPV4_FAILURE_FATAL=yes > IPV6INIT=yes > IPV6_AUTOCONF=yes > IPV6_DEFROUTE=yes > IPV6_FAILURE_FATAL=no > IPV6_ADDR_GEN_MODE=stable-privacy > NAME=eno1 > UUID=1f9ec889-3c64-470a-894b-05543ee44c29 > DEVICE=eno1 > ONBOOT=yes > IPADDR=1.1.1..234 > PREFIX=29 > GATEWAY=1.1.1.233 > IPV6_PRIVACY=no Anything in the logs about what was going on? If you reboot this server again and again, does the problem show up again? Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] PXE ValueError: new value non-existent xfs filesystem is not valid as a default fs type
On 16/01/2020 10:50, Ralf Prengel wrote: > Hallo, > has anyone a working Centos 8.1 PXE Installation? > > This is my problem > http://realtechtalk.com/Centos_PXEBoot_NetInstall_Failure__Pane_is_dead-2012-articles > All CentOS 8.1.1911 validations were done over PXE (machines reinstalled - physical or VMs). So that article mentions something specific about non distro kernel to have other kmod enabled. Is that what you need ? IF not, just ensure that you (obviously) boot anaconda through pxe with the kernel/initrd.img that *matches* the tree you're installing from (as yes, a kernel/initrd from 8.0.1905 wouldn't work to kick a 8.1.1911 install) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Limiting what devices can pair over Bluetooth?
Leon Fauster via CentOS wrote: Whats the bus that your BT is connected to, USB? I'm testing on a laptop that has built-in BT - although lsusb lists: Bus 002 Device 003: ID 0cf3:e005 Qualcomm Atheros Communications which I believe is the BT controller I never tested it with BT devices, just with "plain" usb devices but maybe its worth to take a look at the usbguard package. It supports whitelisting devices ... I've never used USBGuard - but I don't think it will help here Although the BT controller is a USB device, what devices are connected over BT are not I guess you can think of the BT controller in a similar way as, say, a USB network adapter - the NIC is a USB device, but what it connects to over the network are not. In the NIC case, you could use something like firewall rules to control what can and can't be connected to - but there doesn't seem to be anything similar for BT connections/devices James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Limiting what devices can pair over Bluetooth?
Am 16.01.20 um 12:36 schrieb James Pearson: Leon Fauster via CentOS wrote: Is it possible to control behaviour with udev rules? No idea - I haven't found anything that allows you to 'control' Bluetooth - including any mention of udev rules I have no idea if udev could be used in this way - nor where to start in creating possible udev rules :-) I asked my original question on the linux-bluetooth email list - and the only suggestion was hacking the Bluetooth kernel modules to 'filter connection requests at the PSM level' ... Whats the bus that your BT is connected to, USB? I'm testing on a laptop that has built-in BT - although lsusb lists: Bus 002 Device 003: ID 0cf3:e005 Qualcomm Atheros Communications which I believe is the BT controller I never tested it with BT devices, just with "plain" usb devices but maybe its worth to take a look at the usbguard package. It supports whitelisting devices ... -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] After upgrade to CentOS 8.1 default gateway missing
On Thu, 16 Jan 2020 15:34:43 +0100, Stephen John Smoogen wrote: On Thu, 16 Jan 2020 at 07:58, Asle Ommundsen wrote: Hi, Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after a reboot of the first server the network was unavailable. In IPMI console everything except the network was looking good. Network was unreachable. No errors in NetworkManager. I also restarted NetworkManager, but it did not help. Then I discovered that the default gateway suddenly was missing. Then I rebooted the server one more time, but network was still down. Then both myself and a technician in my datcenter was debugging this (I had to wake him up in the middle of the night, costing me a lot of money), without finding any reason for why the default gateway was missing after reboot. Then we rebooted the server a third time, and all of a sudden the problem was gone and the default gateway was back. [...cut...] In order to determine what is going on you need to give a lot more information. 1. How do these boxes get their network information? DHCP or static 2. If they are static, what controls the setting of ips: NetworkManager or network-scripts 3. If they are static, how are they set in /etc/sysconfig/network-scripts/ 4. Do the files in /etc/sysconfig/network-scripts list a GATEWAY= 5. If you are using network-manager, what does nmtui or the graphical tool say the gateway or default route is? Here is answers to your list. I have anonymized the some of the data: 1) Static ip configuration 2) This should be NetworkManager. nmcli output: eno1: connected to eno1 inet4 1.1.1.234/29 route4 1.1.1.232/29 route4 0.0.0.0/0 eno2: connected to eno2 inet4 192.168.0.5/24 route4 192.168.0.0/24 [root@server ~]# nmcli d show | grep IP4.GATEWA IP4.GATEWAY: 1.1.1.1.233 3) TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=eno1 UUID=1f9ec889-3c64-470a-894b-05543ee44c29 DEVICE=eno1 ONBOOT=yes IPADDR=1.1.1..234 PREFIX=29 GATEWAY=1.1.1.233 IPV6_PRIVACY=no 4) Yes 5) [root@server ~]# nmcli d show | grep IP4.GATEWA IP4.GATEWAY: 1.1.1.233 nmtui shows the same gateway. Kind regards, Asle Ommundsen ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
