Sponsored Content
Special Forums IP Networking Linux load balancer ping redirect to other interface Post 302775291 by hadinetcat on Monday 4th of March 2013 01:52:55 PM
Old 03-04-2013
Linux load balancer ping redirect to other interface

Im configuring centos with load balance with ip route and ip rule
Code:
Eth0 192.168.1.5
Eth1 192.168.5.128
[root@host1 testscripts]# ip route
192.168.5.0/24 dev eth1  scope link  src 192.168.5.128
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.5
169.254.0.0/16 dev eth1  scope link 
[root@host1 testscripts]# ip route show table wan2
default via 192.168.5.2 dev eth1  src 192.168.5.128
[root@host1 testscripts]# ip route show table wan1
default via 192.168.1.1 dev eth0  src 192.168.1.5
[root@host1 testscripts]# ip rule show
0:      from all lookup 255
32762:  from 192.168.5.128 lookup wan2
32763:  from all to 192.168.1.5 lookup wan1
32765:  from 192.168.1.5 lookup wan1
32766:  from all lookup main
32767:  from all lookup default

But the problem here when I use
Code:
ping –I 192.168.1.5 www.google.com

The ping it goes to the second interface,
If the second interface is down its stick there..
What to do to fix this issue

Last edited by jim mcnamara; 03-04-2013 at 04:31 PM..
 

6 More Discussions You Might Find Interesting

1. Programming

Load Balancer

Halo mates, I m going to write a load balancer with C. Does anybody know some good reference on this? Cheers, Elton (5 Replies)
Discussion started by: EltonSky
5 Replies

2. AIX

hacmp ip load balancer failover

Hi All, How do I failover on the ip load balancer (back and forth)? It involves first to load a new config on the passive ip. If success, load the new config on the ip active (which is now passive). Any idea, please. Thanks in advance. (0 Replies)
Discussion started by: itik
0 Replies

3. Red Hat

What is the Best Load Balancer for Linux?

Hi, What's the best load balancer for Linux (CentOS, SuSE) according to your personal experience? Linux Virtual Server (LVS) is a famous one, but their download site has not been updated since 2007. Their web and mailing list are so quiet. Is the Ultra Monkey project including LVS... (1 Reply)
Discussion started by: aixlover
1 Replies

4. UNIX for Advanced & Expert Users

piranha load balancer failover

we use piranha load balancer with two nodes even the primary node is running fine and up failover happend to secondary node this happend quite few times ehy node2 cannot talk to node1 what logs are to be checked and investigate why failover occured pulse: partner dead: activating... (0 Replies)
Discussion started by: robo
0 Replies

5. Linux

Server Load balancer

Hello Guys, Hope you all doing well . :) I was checking load balance command (uptime)on VM server and got below output. # uptime 07:08:40 up 52 min, 2 users,a load average: 0.45, 0.11, 0.03 A :How we can calculate load average? Thank you in advance !! Cheers:) Dont forget... (1 Reply)
Discussion started by: Nats
1 Replies

6. Virtualization and Cloud Computing

A load balancer for Nomachine NX

Hello, in case somebody has a NoMachine NX cluster, and is suffering from its dumb round-robin dispatcher, here is a solution: nxpub (NX Pluggable User Balancer). It should run on all LUnix OS. Scripts for install/uninstall are supplied. While tested with NX 3 (NX 3.5 is the latest), it might... (2 Replies)
Discussion started by: MadeInGermany
2 Replies
NOS-TUN(8)						    BSD System Manager's Manual 						NOS-TUN(8)

NAME
nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel SYNOPSIS
nos-tun -t tunnel -s source -d destination -p protocol_number [source] target DESCRIPTION
The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface. Tunnel is the name of the tunnel device /dev/tun0 for example. Source and destination are the addresses used on the tunnel device. If you configure the tunnel against a cisco router, use a netmask of ``255.255.255.252'' on the cisco. This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not really implement. Protocol number sets tunnel mode. Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org. Target is the address of the remote tunnel device, this must match the source address set on the remote end. EXAMPLES
This end, a FreeBSD box on address 192.168.59.34: nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45 Remote cisco on address 192.168.56.45: interface tunnel 0 ip address 192.168.61.2 255.255.255.252 tunnel mode nos tunnel destination 192.168.59.34 tunnel source 192.168.56.45 AUTHORS
Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page. Isao SEKI <iseki@gongon.com> added a new flag, IP protocol number. BUGS
We do not allow for setting our source address for multihomed machines. BSD
April 11, 1998 BSD
All times are GMT -4. The time now is 11:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy