load balance problem

load balance problem

[Daniel Wittenberg]

I've been trying to test the load balancing in our lab and it doesn't
appear to be working.  I have a RH 8.0 firewall, which appears to have
all the specified options set in the kernel .config.  I am running a
sniffer on both out-going links, and only ever see traffic go down one
or the other, never both.  It's always the one I list first:

ip route add default scope global equalize \
        nexthop via 172.27.3.3 dev eth1 weight 1 onlink \
        nexthop via 172.27.1.1 dev eth0 weight 1 onlink

What looks weird is the output:
# /sbin/ip route list
172.27.15.0/24 dev eth2  scope link
172.27.1.0/24 dev eth0  proto kernel  scope link  src 172.27.1.200
172.27.3.0/24 dev eth1  scope link
127.0.0.0/8 dev lo  scope link
default equalize
        nexthop via 172.27.3.3  dev eth1 weight 1 dead onlink pervasive
        nexthop via 172.27.1.1  dev eth0 weight 1 onlink

The 172.27.3 and .1 are both the external links, but I haven't found an
explanation for what "dead" and "pervasive" are.  I also don't see those
showing up in any of the examples I've seen.  So any clues why this only
goes out the first link?  I first thought kernel or default gateway, but
made sure the original default gateway was not specified, and the kernel
appears to be correct.  Something else I've obviously missed?

Thanks!
Dan

Re: load balance problem

[hare ram]

Hi

The one it installs with Redhat RPM of IPROUTE
is borken AFAIK, better get lastest tar and install
i had same problem, after installing the  new Iproute,  the routes works
fine


hare
----- Original Message -----
From: "Daniel Wittenberg" <daniel-wittenberg@starken.com>
To: <netfilter@lists.netfilter.org>
Sent: Thursday, January 23, 2003 11:33 AM
Subject: load balance problem


> I've been trying to test the load balancing in our lab and it doesn't
> appear to be working.  I have a RH 8.0 firewall, which appears to have
> all the specified options set in the kernel .config.  I am running a
> sniffer on both out-going links, and only ever see traffic go down one
> or the other, never both.  It's always the one I list first:
>
> ip route add default scope global equalize \
>         nexthop via 172.27.3.3 dev eth1 weight 1 onlink \
>         nexthop via 172.27.1.1 dev eth0 weight 1 onlink
>
> What looks weird is the output:
> # /sbin/ip route list
> 172.27.15.0/24 dev eth2  scope link
> 172.27.1.0/24 dev eth0  proto kernel  scope link  src 172.27.1.200
> 172.27.3.0/24 dev eth1  scope link
> 127.0.0.0/8 dev lo  scope link
> default equalize
>         nexthop via 172.27.3.3  dev eth1 weight 1 dead onlink pervasive
>         nexthop via 172.27.1.1  dev eth0 weight 1 onlink
>
> The 172.27.3 and .1 are both the external links, but I haven't found an
> explanation for what "dead" and "pervasive" are.  I also don't see those
> showing up in any of the examples I've seen.  So any clues why this only
> goes out the first link?  I first thought kernel or default gateway, but
> made sure the original default gateway was not specified, and the kernel
> appears to be correct.  Something else I've obviously missed?
>
> Thanks!
> Dan
>
>
>

How to Stop scanings

[hare ram]

hi all

i have some home LAN, when some body run some network scanners
or some kind of scripts ( iam not sure)
iam getting this kind of arp -n report

first of all, i thought of its cable problem, then i downloaded scanner and
try to retrive the
ips iam able to see this report

( the MAC addresses are changed, because  for confidential information)

how do i stop scans in my network

192.168.20.106                   (incomplete)
eth1
192.168.20.100                   (incomplete)
eth1
192.168.20.45                    (incomplete)
eth1
192.168.20.101                   (incomplete)
eth1
192.168.20.102                   (incomplete)
eth1
192.168.20.47                    (incomplete)
eth1
192.168.20.103                   (incomplete)
eth1
192.168.20.46                    (incomplete)
eth1
192.168.20.96                    (incomplete)
eth1
192.168.20.41                    (incomplete)
eth1
192.168.20.97                    (incomplete)
eth1
192.168.20.40                    (incomplete)
eth1
202.63.106.17            ether   00:X0:A5:21:L0:A4   C
eth0
192.168.20.43                    (incomplete)
eth1
192.168.20.15            ether   10:F0:8L:10:12:21   C
eth1
192.168.20.42                    (incomplete)
eth1
[root@cache root]#