From: Muddasar Ahmed (Muddasar_Ahmed@xxxxxxxxx)
Date: Mon Mar 18 2002 - 10:18:17 GMT-3
Spoofing. ISDN BRI is a dialer interface which is basically not active
unless dialer process brings it up. During the route and interface look up
process it will show as down and therefore encap failed. Your route should
not point to BRI interface so that route look up completes for a destination
and dialer brings up the interface.
Some one may have a better explanation for this.....
Muddasar
----- Original Message -----
From: "Sundar Palaniappan" <sundar_palaniappan@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, March 17, 2002 6:44 PM
Subject: Static Route pointing to the exit interface
> Router A and Router B are connected via ISDN.
>
> Router A BRI interface IP is: 172.16.10.1/24
> Router B BRI interface IP is: 172.16.10.2/24
>
> Router B's ethernet interface IP is: 192.168.10.1/24
>
> ISDN works fine between these sites.
>
> Assume no dynamic routing protocol is configured on both routers.
>
> To enable connectivity to the ethernet segment on Router B, I added the
> following static route on Router A pointing to the next hop address it
works
> fine.
>
> "ip route 192.168.10.1 255.255.255.0 172.16.10.2"
>
> When I added the following static route pointing to the exit interface on
> Router A it fails.
>
> "ip route 192.168.10.1 255.255.255.0 bri0/0"
>
> Turned IP packets debug on and I was seeing "encapsulation failed"
messages.
>
> Trying to figure out what's causing the failure when the static route
> pointing to the exit interface is used. Guessing the interface type (like
> PPP, NBMA etc) is the problem.
>
> Thanks for your replies in advance.
>
> --Sundar
>
>
>
>
>
>
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:12 GMT-3