similar to: CentOS 5.7 eth0, eth1 and arpwatch flip flops

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, this might seem like a classical problem but I''ve trouble getting this working correctly: # ifconfig ### output stripped down: eth0 Link encap:Ethernet HWaddr 00:50:FC:2B:EB:1B inet addr:192.168.5.220 Bcast:192.168.5.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:02:44:60:EC:58 inet

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

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:

Hi, I''m having problems with new Shorewall installation on Fedora Core 3 (had same problem with Core 2 and upgrade did not help even iptables was upgraded from 1.2.9 to 1.2.11). I''ve followed two nic example, but starting Shorewall drops all connections and don''t permit any outgoing requests, even with "all allowed" policy. Policy file is below. Current setup

CentOS 5.5 Xen "standard" Xen Installation. I have two nics. I just put the second one to DHCP and modified the ifcfg-et01 and so far I am holding, but I am not confident. Prior they were sequential IP Addrs on same subnet. arpwatch has indicated flip flips. I can find no rhyme or reason to predict them. I know I missed I must have missed a step somewhere. I want to keep the

We have a webserver that is connected to three different networks. Due to our cabling, we have to run two of those networks over the same physical network. When connecting from OS X and Windows we are occasionally blocked because the client is sending to the wrong interface. Linux clients seem to have no problem at all. I have read the docs and understand that the problems exists because of

hi list I have a strange problem here. Maybe it is normal behavior and i search within the wrong direction. Probably someone here can give me a hint. I have a device (rhel4 kernel 2.6.9) with 3 interfaces. 2 interfaces (eth0, eth2) are bridged together (br0) and the bridge device has an ip address assigned (192.168.11.15). Another interface (eth1) has assigned 10.7.0.10. So far so good.

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, What happened to the rhel3 i386 arpwatch package? There is only a x86_64 version: sarastro:/users/henkvl 573% ls /users/mirror/Linux/centos/3/*/*/RPMS/arp* /users/mirror/Linux/centos/3/addons/x86_64/RPMS/arpwatch-2.1a11-7.E3.5.x86_64.rpm but there once was a i386 version, as a have a /var/cache/yum/addons/headers/arpwatch-14-2.1a11-7.E3.5.i386.hdr Cheers, -- Henk van Lingen, Systems

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> ---

Good day, I have gone through a couple of the HOWTO''s on how to get this to work, but I am still sitting with a very strange (for me) issue. If two clients connect via OpenVPN (bridged), they can access each other without any problems, but neither of them can access the server, nor any system behind it. I am fairly sure it is a Shorewall issue, but I am very new to Shorewall, having

On and off, I'm seeing Mar 22 14:10:04 <server> arpwatch: short (want 42) The only thing like it I find in googling is an old debian bug, with the only solution I see, from <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155182>, is "It seems that "struct ether_header" was 2 bytes too long, and with attribute packed it works fine on my NSLU2." Anyone know if

Hi, I think the package arpwatch-2.1a11-7.E3.2.i386.rpm is missing in centos-3/3.1/updates. Or is it located somewhere else? The packages libpcap-0.7.2-7.E3.2.i386.rpm and tcpdump-3.7.2-7.E3.2.i386.rpm are present and they come from the same src.rpm Jan Kees

I been running shorewall with out any problems for several months. But I''ve now run into a problem. Hopefully this will be enough information. I''m running shorewall version 1.4.8. On Fedora core 1. Coming into my location I have a T1. I have 5 internet routable IP''s. I''m currently using one as my default internet connection. My ISP''s router is

Dear all, Dear support and users: Sorry to trouble you! I configure the shorewall firewall to forward ftp and ssh port to another server, but failed. Can you help me check? I cannot login both SSH 2222 and ftp! Below is my environment: (attachment is shorewall dump) 1. Gateway (FC6) 1.1) eth0: lan static IP: 192.168.1.20 1.2) eth1: external public static IP:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.10 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.10 Nothing Earth-shattering here and there is no reason to upgrade if you are not seeing one of the corrected problems. - ----------------------------------------------------------------------- Problems corrected in version 2.0.10 1) The

This one is really throwing me. Thanks in advance for any advice. I''m working on a 4 port firewall system. It is running heartbeat+drbd. Primary box looks like this: eth0 -> net/cicso router 192.168.144.2/29 eth1 -> drbd/heartbeat crossover cable 192.168.254.253/30 eth2 -> dmz 192.168.144.10/24 eth3 -> loc 192.168.101.2/24 The IP''s

Hello I am using linux box as a network loadbalance router. ----------------- ------------ |LAN| - |eth0 eth1(1.1.1.2) | DSL1 ------- |DSLAM (1.1.1.1) | | eth2(1.1.1.10) | DSL2 ------- |DSLAM (1.1.1.9) | ---------------- ------------ But I have a

Very strange and as you suggested delete the ifcfg-eth0 file and recreate, specify your settings. I suspect your wireless device and or systemboard is faulty. Is there a BIOS hardware self-test you could perform to check the integrity of your hardware? On Sun, Feb 9, 2020, at 8:10 AM, Nicolas Kovacs wrote: > Hi, > > I've done my fair share of CentOS 7 installations, but this is the

Hello, Am Sonntag, 9. Februar 2020, 14:10:44 CET schrieb Nicolas Kovacs: > Hi, > > I've done my fair share of CentOS 7 installations, but this is the first > time I have this kind of weird problem. Here goes. > > In my office I have a battered Dell Optiplex 320 PC with two NICs that I'm > using as a bare metal sandbox server for testing purposes. > > The