From: Maxim Kurushkin (m.kurushkin@orange-ftgroup.ru)
Date: Mon Jul 30 2007 - 10:08:55 ART
Hi, Djerk.
Yes, turning inverse-arp off does not prevent the router from replying
to in-arp requests. It only prevents from sending requests.
> Afaik disabling inverse-arp should make a router blind and mute to
the whole inverse-arp thing.
No, you are wrong.
WBR,
Maxim
Djerk Geurts wrote:
> I'm using 12.2(4)10b on 36040's. turning inverse-arp off does not prevent
> the router from replying to in-arp requests. (debugged and the darn things
> will still send)
>
> *Mar 14 17:39:36.371: Serial2/1: FR ARP input
> *Mar 14 17:39:36.371: datagramstart = 0x6FCD4EE, datagramsize = 34
> *Mar 14 17:39:36.371: FR encap = 0x4C110300
> *Mar 14 17:39:36.371: 80 00 00 00 08 06 00 0F
> *Mar 14 17:39:36.371: Serial2/1: FR ARP input08 00 02 04 00 09 00 00
> *Mar 14 17:39:36.371: 98 01 2D 05 4C 11 98 01 7B 03 02 02 00 40
> *Mar 14 17:39:36.375:
> *Mar 14 17:39:36.375: Serial2/1: inarp received on 305
> *Mar 14 17:39:36.375: datagramstart = 0x6E0070E, datagramsize = 34
> *Mar 14 17:39:36.375: FR encap = 0x4C010300
> *Mar 14 17:39:36.375: 80 00 00 00 08 06 00 0F 08 00 02 04 00 09 00 00
> *Mar 14 17:39:36.379: 98 01 2D 04 4C 01 98 01 7B 03 02 02 00 40
> *Mar 14 17:39:36.379:
> *Mar 14 17:39:36.379: Serial2/1: inarp received on 304
>
> Afaik disabling inverse-arp should make a router blind and mute to the whole
> inverse-arp thing. I'm about to pull my hair out...
>
> I have R1 - 5 with full mesh F/R between them
> - R4 & 5 PtP using main interfaces and no frame-relay inverse-arp at both
> ends
> - R3 is a hub with R1 & 2 as spokes (main interfaces as well)
> - R1 - 3 should use in-arp
>
> A. R1 - 3 advertise their addresses to R4 & 5 via in-arp, I can't change
> this behaviour. If allowed I could only disable in-arp per dlci.
> B. R1 - 3 learn R4 * 5's addresses (should not happen inho with in-arp
> turned off (at the source).
>
> R4 & R5 (diff IP dlci):
> interface Serial2/1
> description *** C3640-3 (FR) S1/4 ***
> ip address 15.1.45.4 255.255.255.0
> encapsulation frame-relay
> frame-relay map ip 15.1.45.5 405
> no frame-relay inverse-arp
>
> R4(config-if)#do sh fram map
> Serial2/1 (up): ip 15.1.45.5 dlci 405(0x195,0x6450), static,
> CISCO, status defined, active
> Serial2/1 (up): ip 15.1.123.1 dlci 401(0x191,0x6410), dynamic,
> broadcast,, status defined, active
> Serial2/1 (up): ip 15.1.123.2 dlci 402(0x192,0x6420), dynamic,
> broadcast,
> CISCO, status defined, active
> Serial2/1 (up): ip 15.1.123.3 dlci 403(0x193,0x6430), dynamic,
> broadcast,
> CISCO, status defined, active
>
> R3 MP interface:
> interface Serial2/1
> description *** C3640-3 (FR) S1/3 ***
> ip address 152.1.123.3 255.255.255.0
> encapsulation frame-relay
>
> R3(config-if)#do sh fram map
> Serial2/1 (up): ip 152.1.45.4 dlci 304(0x130,0x4C00), dynamic,
> broadcast,
> CISCO, status defined, active
> Serial2/1 (up): ip 152.1.45.5 dlci 305(0x131,0x4C10), dynamic,
> broadcast,
> CISCO, status defined, active
> Serial2/1 (up): ip 152.1.123.1 dlci 301(0x12D,0x48D0), dynamic,
> broadcast,, status defined, active
> Serial2/1 (up): ip 152.1.123.2 dlci 302(0x12E,0x48E0), dynamic,
> broadcast,
> CISCO, status defined, active
>
>
*******************************************************************************************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. Orange Business Services shall not be liable for the message if altered, changed or
falsified. If you are not the intended addressee of this message, please cancel it immediately and inform
the sender.
*******************************************************************************************************
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:42 ART