From: Carlos G Mendioroz (tron@huapi.ba.ar)
Date: Tue Nov 05 2002 - 07:46:48 GMT-3
Ebru,
you need authentication for the called party (R5) to know
who the caller is, and then be able to apply the correct map
with broadcast enabled.
I don't know how/if you can enable broadcast on an async (or DDR
for that matter) by default.
Ebru Toker wrote:
> Hi group,
>
> 2 routers (R5 and R6) have external modems connected to the aux ports. I want them to be OSPF neighbors but I have a problem. After R6 calls R5, it sends hello packets to R5 but I have this debug output on R5
>
> *Mar 1 00:36:12.236: IP: s=10.1.1.6 (Async5), d=224.0.0.5, len 64, rcvd 0
> *Mar 1 00:36:12.560: IP: s=10.1.1.5 (local), d=224.0.0.5 (Async5), len 68, sending broad/multicast
> *Mar 1 00:36:12.560: IP: s=10.1.1.5 (local), d=224.0.0.5 (Async5), len 68, encapsulation failed
>
>
> Both of the configurations are below;
>
> CALLING PARTY
>
> R6#sh run
> Building configuration...
>
> Current configuration : 1114 bytes
> !
> version 12.2
> service timestamps debug datetime msec
> service timestamps log datetime msec
> no service password-encryption
> !
> hostname R6
> !
> !
> ip subnet-zero
> !
> !
> !
> !
> chat-script Dialout ABORT ERROR ABORT BUSY "" "AT" OK "ATDT \T" TIMEOUT 45 CONNECT \c
> !
> !
> !
> interface Loopback0
> ip address 2.2.2.2 255.255.255.0
> !
> interface FastEthernet0/0
> no ip address
> shutdown
> speed auto
> !
> interface Serial0/0
> ip address 3.3.3.6 255.255.255.0
> encapsulation ppp
> !
> interface Serial0/1
> no ip address
> shutdown
> !
> interface Async5
> ip address 10.1.1.6 255.255.255.0
> encapsulation ppp
> dialer in-band
> dialer idle-timeout 900
> dialer map ip 10.1.1.5 name R5 broadcast 250
> dialer-group 1
> async default routing
> async mode interactive
> !
> router ospf 10
> log-adjacency-changes
> network 0.0.0.0 255.255.255.255 area 0
> !
> ip classless
> no ip http server
> !
> !
> dialer-list 1 protocol ip permit
> !
> !
> line con 0
> line aux 0
> exec-timeout 0 0
> script dialer Dialout
> modem InOut
> modem autoconfigure discovery
> transport input all
> autoselect ppp
> stopbits 1
> speed 115200
> flowcontrol hardware
> line vty 0 4
> login
> !
> no scheduler allocate
> end
>
> CALLED PARTY
>
> R5#sh run
> Building configuration...
>
> Current configuration : 989 bytes
> !
> version 12.2
> service timestamps debug datetime msec
> service timestamps log datetime msec
> no service password-encryption
> !
> hostname R5
> !
> !
> ip subnet-zero
> !
> !
> !
> !
> !
> !
> !
> interface FastEthernet0/0
> no ip address
> shutdown
> speed auto
> !
> interface Serial0/0
> ip address 3.3.3.5 255.255.255.0
> encapsulation ppp
> shutdown
> no fair-queue
> clockrate 128000
> !
> interface Serial0/1
> no ip address
> shutdown
> !
> interface Async5
> ip address 10.1.1.5 255.255.255.0
> encapsulation ppp
> dialer in-band
> dialer idle-timeout 900
> dialer map ip 10.1.1.6 name R6 broadcast
> dialer-group 1
> async default routing
> async mode interactive
> !
> router ospf 10
> log-adjacency-changes
> network 0.0.0.0 255.255.255.255 area 0
> !
> ip classless
> no ip http server
> !
> !
> dialer-list 1 protocol ip permit
> !
> !
> line con 0
> line aux 0
> exec-timeout 0 0
> modem InOut
> modem autoconfigure discovery
> transport input all
> autoselect ppp
> stopbits 1
> speed 115200
> flowcontrol hardware
> line vty 0 4
> login
> !
> no scheduler allocate
> end
>
> What can be the possible reason of failed encapsulation?
>
> Ebru
>
-- Carlos G Mendioroz <tron@huapi.ba.ar> LW7 EQI Argentina
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:22:53 GMT-3