From: Derek Buelna (dameon@xxxxxxxxxxx)
Date: Tue Aug 15 2000 - 04:59:37 GMT-3
Cool!
So, ip nat inside dest using rotary pool would do round robin load balancing am
ong a set of servers but the
ip nat outs source could do load balancing based on source?
Something like this? I know you can have multiple inside source lists..
Ip nat out source list 1 pool one
Ip nat out source list 2 pool two
Ip nat pool one 55.0.0.1 55.0.0.1 pre 24
Ip nat pool two 55.0.0.2 55.0.0.2 pre 24
Access-list 1 permit 10.0.0.0
Access-list 1 permit 11.0.0.0
Wait a minute, I wonder if that would translate traffic from 10.0.0.0 into 55.0
.0.1 (on the inside traffic looks like it is coming from 55.0.0.1). Then maybe
I would have to do some policy routing or something to set the next-hop if I wa
nted to accomplish load balancing to two servers bases on source address?
Thanks,
-Derek
-----Original Message-----
From: pbosio@comtech.com.au [SMTP:pbosio@comtech.com.au]
Sent: Monday, August 14, 2000 9:41 PM
To: Derek Buelna
Subject: Re: NAT: Outside Source
Derek,
I'm just configured that about 3 minutes ago..
IP NAT outside source, its just the reverse of ip nat inside source, yes you ca
n
translate coming in, again for tcp load balancing.
Cheers
Paul
Hi,
I'm messing with Nat. I've noticed:
Ip nat in ? gives options for source and dest
Ip nat in source - normal - done it a bunch of times on interfaces, addrs and
pool
Ip nat in dest - normal - can be used with a pool using rotary type for basic
tcp load balancing (braindead)
Ip nat outside source (no dest option available) - what can / would someone do
with that?
Can I translate stuff coming in?
Thanks,
-Derek
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:25 GMT-3