[DragonFlyBSD - Bug #3134] (Resolved) RFC 3021 (/31 networks) appear to be unsupported

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #3134 has been updated by liweitianux.

Status changed from New to Resolved
% Done changed from 0 to 100

Late reply.

The RFC 3021 (i.e., /31 networks for P2P links) support has been added by Roy Marples in commit 502aa5d8026099d86da780e109fa91f191881e0f on 2019-12-18.

So close this now.

----------------------------------------
Bug #3134: RFC 3021 (/31 networks) appear to be unsupported
http://bugs.dragonflybsd.org/issues/3134#change-14535

* Author: jailbird
* Status: Resolved
* Priority: Normal
* Category: Networking
* Target version: 6.4
* Start date: 2018-05-16
----------------------------------------
RFC 3021 introduced the concept of using /31 networks for point-to-point links.  This works in most major OSs, but it doesn't seem to work in DFly.

In DFly, the interface comes up with the correct netmask (0xfffffffe), however the kernel complaints about the other side attempting to change the permanent arp entry for the remote IP, with the arp entry according to "arp -a" being ff:ff:ff:ff:ff:ff (eg, broadcast).  Ping doesn't work, even though the interface is up.

So it appears that DFly doesn't seem to understand that for a /31 PtP link, there is no "network" and "broadcast".



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account