[c-nsp] 1841 w/2 Internet and NAT

[Charles J. Boening]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce,

Just knowing it will work is helpful.  We're going to use the T1
directly on the 1841 as the primary so detecting it going down should be
easy barring an ISP routing failure or something that leaves the T1 up
and the route installed.

Thanks for the information.


Charlie


 

> -----Original Message-----
> From: Bruce Pinsky [mailto:bep at whack.org] 
> Sent: Tuesday, October 03, 2006 3:55 PM
> To: Charles J. Boening
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] 1841 w/2 Internet and NAT
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Charles J. Boening wrote:
> > 
> > I was wondering if someone knew if the Cisco 1841 with advanced 
> > services could support NAT to two different providers?
> > 
> > I have one provider on a T1 and another provider on Ethernet to 
> > another router that goes T1.  I understand that without dynamic 
> > routing, incoming connections will be effected.  That's ok. 
>  I'm just 
> > worried about keeping Internet access from the inside going.
> > 
> 
> It's certainly possible to map into two different NAT pools 
> from different provider address spaces.  That being said, if 
> one of the links goes down, existing connections will be reset.
> 
> My concern is detecting "failure" on the ethernet interface 
> for rerouting since you are likely to suffer soft failures in 
> the forwarding path that leave the connection up, but 
> blackholing traffic.  You need some detection mechanism to 
> move traffic off of that link should that occur.  Something 
> like "Enhanced Object Tracking" or "Reliable Static Routing 
> Using Object Tracking" would be desirable.
> 
> http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/product
> s_feature_guide09186a00801541be.html
> 
> http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/product
> s_feature_guide09186a00801d862d.html
> 
> - --
> =========
> bep
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.4 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFFIuovE1XcgMgrtyYRAtuYAJ0e6ylTU3hjEc24MsPeBMG0Z1uquACgsJm6
> kCxWIoKhYrE7TZZCKS/vE5c=
> =6Yxs
> -----END PGP SIGNATURE-----
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)

iD8DBQFFIvjBcGGHuFdGSWARAhZeAJ4i12uftPOv4FJVUzGyhkiyXw+RFwCeOQWw
sikaTuiM+Qd2RGT5xlF8gi0=
=xyAI
-----END PGP SIGNATURE-----