That works for me...
--- "Kevin L. Kultgen" <[EMAIL PROTECTED]> wrote:
> Thanx, I'll let ya know if it doesn't work. No news
> is good news.
>
> Kevin L. Kultgen
>
> ----- Original Message -----
> From: ""Erick B."" <[EMAIL PROTECTED]>
> Newsgroups: groupstudy.cisco
> Sent: Tuesday, February 20, 2001 3:42 PM
> Subject: RE: Dialer NAT backup dilemma
>
>
> > Here ya go... adjust as necessary. There are
> similar
> > examples on cisco.com.
> >
> > ip nat pool backup 10.10.10.6 10.10.10.6 netmask
> > 255.255.255.0
> > ip nat pool primary 2.2.2.10 2.2.2.20 netmask
> > 255.255.255.0
> > ip nat inside source route-map backup pool backup
> > ip nat inside source route-map primary pool
> primary
> >
> > access-list 1 permit any
> >
> > dialer-list 1 protocol ip permit
> >
> > route-map backup permit 10
> > match ip address 1
> > match interface BRI1/0
> >
> > route-map primary permit 10
> > match ip address 1
> > match interface Serial0/1
> >
> > --- "Stull, Cory" <[EMAIL PROTECTED]> wrote:
> > > Kevin,
> > >
> > > I just got in a hurry so I'll give a quick short
> > > answer.... You should be
> > > able to do pat using the interface.. Define
> both
> > > the dialer interface and
> > > the dsl interface as outside interfaces and the
> > > local area network interface
> > > as inside.. Setup the nat command to use the
> > > interface so that whenever it
> > > goes out the dsl interface it will be PATted to
> that
> > > IP and whenever it goes
> > > out the dialer interface it will be PATted to
> that
> > > IP address..
> > >
> > > I've never tried this but in theory it should
> > > work... Let me know if
> > > not...
> > >
> > > Thanks
> > > Cory
> > >
> > >
> > > -----Original Message-----
> > > From: Kevin L. Kultgen
> [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, February 20, 2001 2:34 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Dialer NAT backup dilemma
> > >
> > >
> > > I have scoured all the books I have and CCO for
> an
> > > answer but keep coming up
> > > dry. So I hope someone has an answer. It's not
> an
> > > ovely complex scenario,
> > > and I would think that someone else has tripped
> > > across it before.
> > >
> > > I have a client that requires 24x7 Internet
> Access.
> > > The have a DSL Modem
> > > plugged into a 2611 (Eth 0/0) and a BRI NT1 WIC
> for
> > > backup. I can get it
> > > all to work, in terms of floating static routes
> and
> > > connectivity, but the
> > > catch is that they use a private address space
> and
> > > require the use of NAT.
> > > NAT doesn't appear to fail over. Actually it
> does
> > > but it continues to use
> > > the address of the Ethernet 0/0 interface, (Same
> for
> > > a Tunnel interface that
> > > they have). Is there a way to set NAT up so
> that
> > > the address will change to
> > > the new address assigned to the Dialer
> Interface?
> > > Maybe same for the
> > > Tunnel. I was thinking that a Loopback
> interface
> > > may be required but keep
> > > failing to see the appropriate usage...
> > >
> > > Any ideas? Like I said, it's not hugely complex
> and
> > > I'm sure that other
> > > people have tripped across it, but I don't see
> it
> > > documented anywhere.
> > >
> > > --
> > > Kevin L. Kultgen
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
