From: Richard Dumoulin (richard.dumoulin@vanco.es)
Date: Tue Jun 08 2004 - 15:32:07 GMT-3
LOL, Has anyone ever seen this ?!?!?!?
R4 and R5 are connected via isdn. R4 calls R5. When R5 receives the call it
sends ARP requests to its OWN ethernet interface to resolve R4 BRI ip
address until PPP authentication occurs. Then the mapping works !!
Rack1R5#
*Mar 1 00:41:12.833: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to
up
Rack1R5#
Rack1R5#
Rack1R5#
Rack1R5#
Rack1R5#
Rack1R5#
Rack1R5#
*Mar 1 00:41:12.857: %ISDN-6-LAYER2UP: Layer 2 for Interface BR1/0, TEI 123
changed to up
Rack1R5#
Rack1R5#
Rack1R5#
*Mar 1 00:41:13.622: IP ARP: sent rep src 187.1.45.4 000a.b7d9.4e41,
dst 187.1.45.4 ffff.ffff.ffff Ethernet0/1
*Mar 1 00:41:14.608: %LINEPROTO-5-UPDOWN: Line protocol on Interface
BRI1/0:1, changed state to up
Rack1R5#
Rack1R5#
Rack1R5#
Rack1R5#
*Mar 1 00:41:18.839: %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected
to 916600035 ROUTER4
Rack1R5#u all
All possible debugging has been turned off
Rack1R5#sh run int bri 1/0
Building configuration...
Current configuration : 256 bytes
!
interface BRI1/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 ROUTER4 broadcast
dialer-group 1
isdn switch-type basic-net3
ppp authentication pap callin
ppp chap password 0 CISCO
end
**********************************************************************
Any opinions expressed in the email are those of the individual and not necessarily the company. This email and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering it to the intended recipient, be advised that you have received this email in error and that any dissemination, distribution, copying or use is strictly prohibited.
If you have received this email in error, or if you are concerned with the content of this email please e-mail to: e-security.support@vanco.co.uk
The contents of an attachment to this e-mail may contain software viruses which could damage your own computer system. While the sender has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening any attachments to this e-mail.
**********************************************************************
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:35 GMT-3