Re: [OSPF] Cisco OSPF implementation - Different networks on serial links

"Acee Lindem (acee)" <> Sat, 06 June 2015 20:41 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id A8DE41A007E for <>; Sat, 6 Jun 2015 13:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.611
X-Spam-Status: No, score=-12.611 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Xl5EB-Lx_Nbm for <>; Sat, 6 Jun 2015 13:41:12 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 223361A0087 for <>; Sat, 6 Jun 2015 13:41:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=7569; q=dns/txt; s=iport; t=1433623272; x=1434832872; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=kOlIWt43ICRHL2hLtau2LMcTUlw2enrupSGh6TUi92g=; b=Qcs3SzxFsctzuv124xqS3fVCXR2Lu8RtKU676f8rOOzt+TJRQstyhxtd ZTpR01kaT8Z+TuxZtkfCk1uqdxFabo9CgMuLyDbHCsXES4MfkgB73BAFi OCL/lYW0CGcJJXAuxnu/LHkqMov1vOk3n5zb7Ad5I+bbH7vxZ49FQVE3t c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.13,564,1427760000"; d="scan'208,217";a="1361561"
Received: from ([]) by with ESMTP; 06 Jun 2015 20:41:11 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t56KfBeC010457 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 6 Jun 2015 20:41:11 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Sat, 6 Jun 2015 15:41:10 -0500
From: "Acee Lindem (acee)" <>
To: Vlad Olariu <>, "" <>
Thread-Topic: [OSPF] Cisco OSPF implementation - Different networks on serial links
Thread-Index: AQHQoJkedzREzq+820m7lEVLyw+mLg==
Date: Sat, 6 Jun 2015 20:41:10 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D198D0C520EA1aceeciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [OSPF] Cisco OSPF implementation - Different networks on serial links
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 06 Jun 2015 20:41:13 -0000

Hi Vlad,

From: Vlad Olariu <<>>
Date: Saturday, June 6, 2015 at 1:40 PM
To: OSPF WG List <<>>
Subject: [OSPF] Cisco OSPF implementation - Different networks on serial links


I was reading the OSPFv2 RFC, namely, from page 62:

The Area ID specified in the header must either:
            (1) Match the Area ID of the receiving interface.  In this
                case, the packet has been sent over a single hop.
                Therefore, the packet’s IP source address is required to
                be on the same network as the receiving interface.  This
                can be verified by comparing the packet’s IP source
                address to the interface’s IP address, after masking
                both addresses with the interface mask.  This comparison
                should not be performed on point-to-point networks. On
                point-to-point networks, the interface addresses of each
                end of the link are assigned independently, if they are
                assigned at all.

I have tried this on various Cisco routers and it doesn't work. It complains about the interfaces being in a different network.

Is this an implementation flaw?

This is really a vendor specific question and not a topic for an IETF list. Having said that, Cisco enforces a subnet model for P2P interfaces and advertises the subnet consistent with option 2 in RFC 2328, section You could make the interfaces unnumbered if you want to use addresses in different subnets. Please ping me off-list if you have further questions.

Hope this helps,