From: Mas Kato (loomis_towcar@xxxxxxxxxxxxxx)
Date: Sun Nov 18 2001 - 02:58:48 GMT-3
[demime could not interpret encoding binary - treating as plain text]
If your intention is to do TCP load distribution among several inside hosts the
n your 'mypool' address pool needs to specify the range of addresses that corre
spond to these hosts along with the 'type rotary' keywords. The range of addres
ses in this pool should not include the inside interface address as shown in yo
ur config.
When packets arrive at the outside interface destined for the virtual host as d
efined by your access-list 11, they will be rotared among the real hosts define
d by 'mypool.'
Hope this helps,
Mas Kato
https://ecardfile.com/id/mkato
> "Juan Villamil" <juan.villamil@earthling.net> <ccielab@groupstudy.com> NAST &
ROTARYDate: Sat, 17 Nov 2001 12:32:50 -0000
>Reply-To: "Juan Villamil" <juan.villamil@earthling.net>
>
>Hi all
>
>This is something I thought was really simple!!!! But I can not get it
>to work..I even tried on different routers an IOS..
>
>Any ideas what I missed???
>
>Thanks,
>Juan
>
>Config:
>
>interface FastEthernet0/0
> ip address 137.1.0.10 255.255.255.0
> no ip directed-broadcast
> ip nat outside
>!
>!
>interface Ethernet1/0
> ip address 10.1.1.2 255.255.255.0 secondary
> ip address 10.1.1.3 255.255.255.0 secondary
> ip address 10.1.1.1 255.255.255.0
> no ip directed-broadcast
> ip nat inside
> no keepalive
>!
>!
>ip nat pool mypool 10.1.1.1 10.1.1.3 netmask 255.255.255.0 type rotary
>ip nat inside destination list 11 pool mypool
>
>ip route 0.0.0.0 0.0.0.0 137.1.0.253
>!
>access-list 11 permit 10.1.1.10
------------------------------------------------------------
Speed Racer's Official Virtual Pit Stop.
http://www.speedracerdsl.com/speedracer/
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:17 GMT-3