From: Scott Morris (swm@emanon.com)
Date: Fri Mar 11 2005 - 16:15:43 GMT-3
Since you are not doing any authentication, this is exactly correct.
When you ping from R4, the line will go up, because R4 knows where to send
to and where to go. So the packet goes to R5.
R5 looks at the incoming ICMP and tries to respond, but needs to look at
where to send it. It sees a dialer map, but that gives noplace to go.
If you were running CHAP, then the name part would actually correlate (see
"show dialer" output). Until that time though, you'll need a phone number
to give it some way to say "Oh, I'm already connected to that guy!" and send
the packet back.
HTH,
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Roy
Dempsey
Sent: Friday, March 11, 2005 12:16 PM
To: ccielab@groupstudy.com
Subject: Re: ISDN problem
Hi Simon,
Had this EXACT problem yesterday. This should work, according to my
understanding. However, the only way I could get it to work is to add the
dialer string to the R5 router, thus breaking the requirement you mention.
However, if you then go on and configure PPP encapsulation and
authentication on the interface, you can remove the dialer string.
I think its related to R5 not knowing what to do with the traffic, even
though there is only one configured interface and the debug shows it being
sent to this Interface. Once you configure authentication, the router can
map the traffic to the interface using the hostname of the calling router
On Fri, 11 Mar 2005 17:02:28 -0000, simon hart <simon.hart@btinternet.com>
wrote:
> Hi all,
>
> I am having a bit of a nightmare with some simple ISDN configuration:
> I am trying to establish a connection between two routers R4 and R5.
> R5 should not be able to initiate a call - only R4. I am using legacy
> DDR, configs below
>
> Frame_R4#
> !
> interface BRI0
> ip address 187.1.45.4 255.255.255.0
> encapsulation ppp
> dialer map ip 187.1.45.5 name Rack1R5 broadcast 2222 dialer-group 1
> isdn switch-type basic-ni isdn spid1 1211 end !
> dialer-list 1 protocol ip permit
>
> Rack1R5#
> !
> interface BRI0/0
> ip address 187.1.45.5 255.255.255.0
> encapsulation ppp
> dialer idle-timeout 0
> dialer map ip 187.1.45.4 name Rack1R5 broadcast isdn switch-type
> basic-ni isdn spid1 2122 end
>
> If I ping from Frame_R4 then the ISDN line is brought up but no
> response to the pings. If I debug IP packet on R5 I notice that I
> have an encapsulation
> failure:
> Rack1R5#
> *Mar 1 07:52:46.460: IP: s=187.1.45.4 (BRI0/0), d=187.1.45.5
> (BRI0/0), len 100, rcvd 3 *Mar 1 07:52:46.460: IP: s=187.1.45.5
> (local), d=187.1.45.4 (BRI0/0), len 100, sending *Mar 1 07:52:46.460:
> IP: s=187.1.45.5 (local), d=187.1.45.4 (BRI0/0), len 100,
> encapsulation failed Rack1R5# *Mar 1 07:52:48.459: IP: s=187.1.45.4
> (BRI0/0), d=187.1.45.5 (BRI0/0), len 100, rcvd 3 *Mar 1 07:52:48.459:
> IP: s=187.1.45.5 (local), d=187.1.45.4 (BRI0/0), len 100, sending *Mar
> 1 07:52:48.463: IP: s=187.1.45.5 (local), d=187.1.45.4 (BRI0/0), len
> 100, encapsulation failed
>
> As you can see it is showing an encapsulation failure, however the map
> looks fine and the config is exactly as dictated within the solution
> guide of the Internetwork expert solution guide
>
> Any comments most welcome
>
> S.
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.7.1 - Release Date: 09/03/2005
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:45 GMT-3