From: Geatti (geatti@xxxxxxxx)
Date: Wed Jul 26 2000 - 21:33:27 GMT-3
Thanks all for the help. "Async default routing" did the trick, I thought
async dynamic would be sufficient... I wasn't.
Three or four posts supplied me with the all I needed, again thanks for all
the help - Marco
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Dave Gingrich
Sent: Wednesday, July 26, 2000 6:27 PM
To: Sam Munzani
Cc: ccielab@groupstudy.com
Subject: Re: async routing
Try adding "async default routing" to the interface.
async default routing turns the interface into (you guessed it) a routable
interface.
async dynamic routing allows a routing protocol (eigrp, ospf,etc) to run
over the interface, but async default routing must be there too.
async mode dedicated means you cannot use the async line for CLI access to
the router. Async mode interactive allows the async port (or AUX port) to
be used for both PPP (or ARAP) and CLI, choices determined by the
autoselect parameters on the corresponding line.
If configured correctly (interactive) a single modem attached to the AUX
port can used for both dial backup, and remote access to the CLI (at least
when there is no backup connection running).
-dg
At 16:38 7/26/00 -0500, Sam Munzani wrote:
>I thought "async mode dedicated" is for null modem cable aux to aux port.
>Not sure though. I could never make async routing work with AUX port and
>modems. If you ever get it working please e-mail me your configs. I want to
>see what makes it so difficult.
>
>Sam
>
>> Try with a dialer interface. I think this should solve your problem.
>>
>> Frederic
>>
>> Geatti wrote:
>> >
>> > Nice catch on the Broadcast statement on R2 Xuping - thanks.
>> > Still doesn't work though. I've tried RIP, IGRP, EIGRP and OSPF, none
of
>> > them work over my POTS connection.
>> > I do a debug ip RIP and all I get is updates send to the loopbacks,
it's
>as
>> > if the routing process doesn't know that the async 1 interface exists
on
>> > either router in order to send the broadcast/multicast out, even though
>it
>> > is included in the RIP process as 10.0.0.0 and both status and protocol
>are
>> > UP UP.
>> >
>> > Ping :-) can ping and telnet through line all day works fine
>> > Route :-( routing broke.
>> >
>> > Appreciate any contributions,
>> > Marco
>> >
>> > (Router2-aux)---modem-------modem----(aux-Router3)
>> >
>> > R3 config - (has loop of 3.3.3.3 255.255.255.0)
>> >
>> > interface Async1
>> > ip address 10.10.10.1 255.255.255.0
>> > ip directed-broadcast
>> > encapsulation ppp
>> > dialer in-band
>> > dialer idle-timeout 200
>> > dialer map ip 10.10.10.2 name R2 modem-script fred broadcast 40
>> > dialer-group 1
>> > async dynamic routing
>> > async mode dedicated
>> > ppp authentication chap
>> >
>> > router rip
>> > network 10.0.0.0
>> > network 3.0.0.0
>> >
>> > R2 config - (has loop of 2.2.2.2 255.255.255.0)
>> >
>> > interface Async1
>> > ip address 10.10.10.2 255.255.255.0
>> > encapsulation ppp
>> > async dynamic routing
>> > async mode dedicated
>> > dialer in-band
>> > dialer map ip 10.10.10.1 name R3 broadcast
>> > ppp authentication chap
>> >
>> > router rip
>> > network 10.0.0.0
>> > network 2.0.0.0
>> >
>> > -----Original Message-----
>> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
>> > xuping
>> > Sent: Tuesday, July 25, 2000 9:20 PM
>> > To: Geatti; ccielab@groupstudy.com
>> > Subject: async routing
>> >
>> > >R2 config
>> > >
>> > >interface Async1
>> > > ip address 10.10.10.2 255.255.255.0
>> > > encapsulation ppp
>> > > async dynamic routing
>> > > async mode dedicated
>> > > dialer in-band
>> > > dialer map ip 10.10.10.1 name R3
>> > > ppp authentication chap
>> >
>> > Hi
>> >
>> > in R2 dialer map, add "brocast", since most routing protcol use brocast
>or
>> > multicast.
>> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:58 GMT-3