From: Yakout Esmat (yesmat@xxxxxxxxxxxxxx)
Date: Mon Jul 15 2002 - 21:08:06 GMT-3
I think using dialer string might solve the issue, I thought about that. I
will give it a try and let you guys know.
Cheers
Yakout
-----Original Message-----
From: P729 [mailto:p729@cox.net]
Sent: Tuesday, July 16, 2002 6:28 AM
To: Yakout esmat; Groupstudy
Subject: Re: Default route over ISDN
"Encapsulation failed" indicates a failure to make a layer-3 to layer-2
binding. Dialer-maps inherently make a BRI interface multipoint in nature.
When you specify the next-hop, the router knows how to make the binding by
using your dialer-map. Apparently, when you just specify the "out" interface
the layer-2 binding remains ambiguous. Have you tried using 'dialer string'
instead? This would remove the ambiguity and perhaps allow the binding to
form.
Regards,
Mas Kato
https://ecardfile.com/id/mkato
----- Original Message -----
From: "Yakout esmat" <yesmat@iprimus.com.au>
To: "Groupstudy" <ccielab@groupstudy.com>
Sent: Monday, July 15, 2002 7:01 AM
Subject: Default route over ISDN
> Any body aware of this problem..
>
> Scenario:
>
> 10.1.1.1/24--[R1]------(192.168.1.0/24)-----[R2]----
> ISDN
>
> 1) R2 is configured with a static default route
>
> Problem:
>
> 1) If the default static route on R2 is pointing to BRI0 interface "ip
route
> 0.0.0.0 0.0.0.0 bri0", R2 can't ping 10.1.1.1 on R1. Getting
"encapsulation
> failed" error when debuging ip packets, and R2 can't initiate a dial.
>
> 2) If I cahnge the default to point to next hop instead "ip route 0.0.0.0
> 0.0.0.0 192.168.1.1", every thing is sweet
>
> IOS 12.1, legacy ISDN with single dialer map statement is used, IP
classless
> is on...
>
> I must be missing some thing.
>
> Thanks
>
> Yakout
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:31 GMT-3