[c-nsp] /31's on Eth p-t-p links instead of /30's

Spyros Kakaroukas skakaroukas at rolaware.com
Thu Sep 11 02:35:51 EDT 2014


We've been using /31s wherever we can for quite a while now. Never had any problems with it on cisco ( or any other quality vendor ) routers/switches. The only issue is that, on customer-facing links, there's the occasional customer device that does not support it ( or even worse, lets you configure it and then arps for every destination instead of routing to the other end ). In those cases, we just switch to /30s .

Spyros Kakaroukas
IP Engineer / CCIE #36537

Rolaware Hellas SA
78 Kifisias Avenue, Marousi, 15125, Greece
T:  +30 211 000 7089 | M: +30 695 676 0684
F:  +30 211 000 7099 | E: skakaroukas at rolaware.com

? Consider our environment – Think before you print ?

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of CiscoNSP List
Sent: Thursday, September 11, 2014 8:47 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] /31's on Eth p-t-p links instead of /30's

Hi Everyone,

Ive read a few previous (older) posts on this topic, and it seems /31's are used quite a bit (Service Providers etc).

Just trying to conserve IPv4 addresses - Has anyone run into any issues with using /31's? (OSPF/BGP....anything else?)


cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

This e-mail and any attachment(s) contained within are confidential and are intended only for the use of the individual to whom they are addressed. The information contained in this communication may be privileged, or exempt from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and delete the communication without retaining any copies. Rolaware Hellas SA is not responsible for, nor endorses, any opinion, recommendation, conclusion, solicitation, offer or agreement or any information contained in this communication.

More information about the cisco-nsp mailing list