similar to: 7.4 network issues

Dear Simon, every second IP-address is unwanted. We restarted? eno4: nmcli con down eno4; nmcli con up eno4 and the second address vanishes. Then after a few ours, the second ip address reappears. This is the config-file of eno2: # cat ifcfg-eno2 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes

Hi, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device

Dear Simon, > And can you diff the config of eno1 and eno4. # pwd /etc/sysconfig/network-scripts # diff -u ifcfg-eno1 ifcfg-eno4 --- ifcfg-eno1??? 2020-09-21 17:23:25.576672703 +0200 +++ ifcfg-eno4??? 2020-09-22 07:18:43.160532532 +0200 @@ -3,15 +3,20 @@ ?BROWSER_ONLY=no ?BOOTPROTO=none ?DEFROUTE=no -IPV4_FAILURE_FATAL=yes -IPV6INIT=no -IPV6_AUTOCONF=no +IPV4_FAILURE_FATAL=no

On Thu, 16 Jan 2020 15:34:43 +0100, Stephen John Smoogen <smooge at gmail.com> wrote: > On Thu, 16 Jan 2020 at 07:58, Asle Ommundsen <aommundsen at gmail.com> > 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 >>

Alice, >> Two onboard nics, Intel, eno1 and eno2 >> >> If either of them is set to onboot then network won't start. >> >> one error message says :bad vendor preset disabled This bug report from the upstream vendor (RH) for RHEL 7 might help in troubleshooting what's causing the error message: See: https://bugzilla.redhat.com/show_bug.cgi?id=1399448

Dear CentOS-Community, we are facing the following issue: A secondary ip address seems to be automatically added to a nic which causes several issues in our setup. This server is equipped with four nics which are currently in use: # nmcli con show NAME????? UUID????????????????????????????????? TYPE????? DEVICE eno2????? cb6fcb54-be52-4ab6-8324-88091a0ea1a0? ethernet? eno2 eno4?????

> -----Original Message----- > From: Gordon Messmer > Sent: Monday, August 31, 2015 12:15 PM > > On 08/31/2015 03:51 AM, Jason Pyeron wrote: > > I feel like this is an issue of libvirt starting before networking, > > but I am a fish out of water with systemd. > > Are you using the "network" or "NetworkManager" service to > configure your

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

Here is the relevant log snippet: journal: libvirt version: 1.2.8, package: 16.el7_1.3 (CentOS BuildSystem <http://bugs.centos.org>, 2015-05-12-20:12:58, worker1.bsys.centos.org) journal: failed to connect to monitor socket: No such process journal: internal error: process exited while connecting to monitor: ((null):1937): Spice-Warning **: reds.c:3036:reds_init_socket:

This does not look bad, pretty ok. But im do have a question here. > ipaddress: 10.103.1.6 X.X.103.1 This indicated that the primary interface is eno2 > 2: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > ??? inet 10.103.1.6/24 brd 10.103.1.255 scope global eno2 > 3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > ??? inet

Hi Felix > Dear Simon, > > every second IP-address is unwanted. We restarted? eno4: > > nmcli con down eno4; nmcli con up eno4 > > and the second address vanishes. Then after a few ours, the second ip > address reappears. That's really interesting. Doesn't NetworkManager also store other settings in a different location, not the ifcfg files? I think it does so and

On 18/04/2017 15:54, Frank Thommen wrote: > Hi, > > I am currently struggling with the right way to configure a bonding > device via kickstart (via PXE). > > I am installing servers which have "eno" network interfaces. Instead of > the expected bonding device with two active slaves (bonding mode is > balance-alb), I get a bonding device with only one active slave

This is my system info: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.60-1-pve (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh

> Dear Simon, > > >> And can you diff the config of eno1 and eno4. > > # pwd > /etc/sysconfig/network-scripts Okay, nothing to find here. What about eno2, you also have two IP addresses there and even in the same subnet, is this wanted or not? Can the second address of eno2 be found in the ifcfg file? Both eno2 and eno4 have "scope global secondary dynamic"

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, some months ago I ran into a hassle with following, quite simple config that works on CentOS 6 and CentOS 5 extremeley well, for years. However, I have problems getting it running on CentOS 7. ,-- bond0.100 -- brbond0.100 -> (VMs) eth0 (eno1 on C7) --. | |--- bond0 ----|--

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

On 08/23/2018 04:10 PM, TE Dukes wrote: > Here's the link: > https://paste.fedoraproject.org/paste/MMNEJmqIrEzK-A4N3MR0ZA ip route show: default via 192.168.1.1 dev eno1 proto static metric 101 192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.111 metric 100 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.110 metric 101 You have two physical devices using

On Fri, 3 Nov 2017, Mark Haney wrote: > On 11/01/2017 05:02 PM, James A. Peltier wrote: >> Leaving ksdevice= off the command line will prompt you for the location of >> the kickstart file and the device you want to use to kickstart >> > Well, things just got weird with this.? The first couple of times I included > the biosdevname etc, on the command line with

someone recommended that i should give br0 the same hardware address as eno2. I did that, and restarted the vm, and it still does not work. Here is my current host interface config: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft

Hi, I encountered a problem when creating a VLAN interface according to the Red_Hat_Enterprise_Linux-7-Networking_Guide. I configuered the parent interface ifcfg-eno1 as follows: DEVICE=eno1 TYPE=Ethernet BOOTPROTO=none ONBOOT=yes And I created a new file named ifcfg-eno1.5, the content is: DEVICE=eno1.5 BOOTPROTO=none ONBOOT=yes IPADDR=192.168.81.3 PREFIX=24