similar to: pbond0: received packet with own address as source address

I have a working LVS-Setup on CentOS 5.4 with the following settings in sysctl.conf: net.ipv4.conf.lo.arp_ignore = 1 net.ipv4.conf.lo.arp_announce = 2 net.ipv4.conf.all.arp_ignore = 1 net.ipv4.conf.all.arp_announce = 2 Now I''d like to use shorewall, but after activating it, shorewall changes both arp_ignore values to 0. I just found out how to set arp_ignore for separate interfaces, but

From: Stephen Hemminger <shemminger@linux-foundation.org> This adds another inet device option to enable gratuitous ARP when device is brought up or address change. This is handy for clusters or virtualization. Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> ---

Hi all, I''ve posted a few times with regards to this error and would like to phrase it a diff way because I have some new info. When running my Xen kernel in conjunction with the Gitco repos and using a mode 0 bond which is round robin, my logs fill with; pbond0: received packet with own address as source address When running a non Xen kernel but using the same type of mode 0

Hello, I have a CentOS 7.3 + updates server where my configuration arises from the need to connect via iSCSI to a Dell PS Series storage array and Dell not supporting bonding. So that I need to use 2 nics on the same vlan to connect to iSCSI portal IP and then use multipath. Also, the iSCSI lan is on a dedicated vlan I have only these 2 x 10Gbit adapters and I also need to put other vlans on them

Hi all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

Hi folks, I have lots of messages like these appearing on my local CentOS 5.2 consoles: > Oct 17 12:03:29 machine kernel: printk: 1 messages suppressed. > Oct 17 12:03:29 machine kernel: pbond0: received packet with own address as source address I have disabled console logging in syslog.conf, and even if I shut down syslog and kernel logger, the messages keep coming on the local

Hello everyone, I''m trying to get multiple guests to connect their networks to the Xen network bridge xenbr0 that''s tied to two bonded interfaces. My current dom0 network looks like this: (eth0 + eth1) => bond0 -> pbond0 -> xenbr0 eth0 and eth1 are bonding under Red Hat EL5, and Xen is configured to use bond0 as the main network device. Xend-config is set to use the

Greetings all. This has been an ongoing issue for me for a few months, and I''ve been trying to get an answer. My server has two NICs, and I want to set up the following: NICs (x2) -> bond (mode 5) -> Xen Bridge -> Doms ...however, trying to configure this doesn''t seem to work: network-bridge steals eth0 instead of bond0, which breaks the bond AND my networking. The

I have a bonded interface running in mode 1 which is active/passive and no issue with this. I need to change it to mode 0 for active/active setup. Does mode 0 is dependent on the switches configuration? My setup is: 2 links from bonded interface is connected to different switches. When I change to mode0 from mode1 , bond0 is not coming up. These are the steps I performed 1) changed to options

Hi, I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one of those is saying frequently in /var/log/messages: kernel: bond0: received packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0

Hi all, Read many posts on the subject. Using 802.3ad. Few problems; Cannot ping some hosts on the network, they are all up. Cannot resolve via DNS which is one of the hosts that I cannot ping, internal nor external DNS hosts. Unplugging the NICS and plugging them back in will then not allow pining if the default d=gateway. When cold booting it somewhat works, some hosts are pingable while

Dear all, Has anyone experienced this whilst running DRBD over eth1 between two CentOS 5.7 servers? eth1 is a private IP address, unroutable. eth0 is the public address. CentOS will reply sometimes once every 3 days or every 14mins~ saying "My public IP is on eth1" to arp requests when it's not, it's eth0. This freezes traffic and causes issues. We've looked at arp*

Hi, the docs suggest to use firewalling in Dom0. I have a question: Dom0 sees al the interfaces, not just those considered its "own" ones. So should I set up firewalling to use/protect only Dom0''s own interfaces, leaving individual firewalls to DomUs, or should I set up firewalling on the physical interfaces (peth*)? To make things a bit worse I'' using bonding,

Shorewall 4.5.1.1 I have 5 interfaces on a centos box, the first two are internal on two different subnets, the next two are two different ISP''s and the last one is a private network for testing and administration. The second internal subnet (eth1) is rejecting all the arp requests to it and I get the following in the log files ever second or two - May 16 05:28:54 services kernel:

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

Running on Centos 5.6 with KVM... I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge? I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. There also seems to be a bug with 5.6

Hi, I have a linux server running kernel 2.6.19 that is connected with 2 seperate 100Mbit links to the same isp: +---+ +---------------+ | I | +---------------+ | | | S | | | | eth0 --+--------------+ P | | |

Hi, Has any one had problems with mail clients were your DNS is like this; doman.com MX 50 mail.domain.com domain.com MX 100 mail2.domain.com domain.com CNAME www.domain.com -aurf

Hi all, I noticed that my ssh logins to a particular server were taking up to 5 seconds to finally login. My tcpdump -vv weren't producing much output (not good) and my pings to and from that host were normal and almost identical to other hosts on my subnet that had no ssh login delay issues. Log files also showed nothing alarming. My hosts file was missing this at the very end of