Redirection of packets based on source IP address

[Joseph Mack NA3T]

On Tue, 13 Feb 2007, Martijn Grendelman wrote:

>
> Not really. I have been running with:
>
> martijn at tweety:~> rr ipvsadm -L
> IP Virtual Server version 1.0.10 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
>  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
> TCP  212.204.230.98:www sh
>  -> tweety.sipo.nl:www           Local   200    25         44
>  -> daffy.sipo.nl:www            Route   200    12         27
> TCP  212.204.230.98:https sh persistent 360
>  -> tweety.sipo.nl:https         Local   100    0          0
>  -> daffy.sipo.nl:https          Route   100    0          0
>
> ever since that list discussion, and haven't had any problems at all.

Since the -SH scheduler sends a client's packets to the same 
realserver, I had thought that it should completely replace 
persistence. However you're using persistence with -SH, so 
apparently -SH doesn't handle keeping the client on the 
realserver as I expect. So why are you using persistence?

On a different topic - why do you have publically accessable 
realservers?

wm7d:~$ host tweety.sipo.nl
tweety.sipo.nl has address 212.204.230.96
tweety.sipo.nl mail is handled by 200 mx1.sipo.nl.
tweety.sipo.nl mail is handled by 10 mail.sipo.nl.
tweety.sipo.nl mail is handled by 100 mx0.sipo.nl.

wm7d:~$ host daffy.sipo.nl
daffy.sipo.nl has address 212.204.230.91
daffy.sipo.nl mail is handled by 10 mail.sipo.nl.
daffy.sipo.nl mail is handled by 100 mx0.sipo.nl.
daffy.sipo.nl mail is handled by 200 mx1.sipo.nl.

Thanks Joe

-- 
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!