Hello Lads and ladies

I had a number of discussions with some devs about this patch and
there seems to be a lack of confidence in what I wrote  :)
and one person used the word suspicious to describe the patch :)

so the point to point addressing scheme is for saving ips sometimes
 it can be referred to incorrectly in my opinion as /31 addressing
 (well it is more like 2x /32 addresses) but it can be a
(summary /31 network if they are sequential
and the first ip is an even number)
it is described on the following rfc
https://tools.ietf.org/html/rfc3021

it is used to save IP allocations rather than using a
standard broadcast network allocation
for giving an ip to a client which would require /30 network
(4 Ips in total )
so an ascii diagram of what im trying to document is as follows

                          inet 10.3.4.5 0xffffffff 10.1.2.3
                              +
                              |
 +-----------------+          |  +------------------+
 |  Router A       |          v  |    Router B      |
 |                 +-+--------+--+                  |
 +-----------------+ ^           +------------------+
                     |
                     |
inet 10.1.2.3   0xffffffff 10.3.4.5

so in point to point addressing an interface on your router
you put ip address of your router interface after inet
 you set the subnet mask to /32  (255.255.255.255)
and you put the other router ip address after the subnetmask,

then on the other router you do swap the ips  in the hostname.if file
and hey presto your link works

comments suggestions and criticisms welcome
Thanks


On 24 September 2017 at 13:12, Tom Smyth <tom.sm...@wirelessconnect.eu> wrote:
> Hello lads, and ladies,
> I have included some extra info on point to point addressing on
> interfaces in OpenBSD  thanks @tedu  for the blog post that helpd me
> learn how to do point to point addressing (non Broadcast) on Openbsd
> and @theo @ingo for pointing me in the right direction on man page
> contributions earlier in the year,
> patch is below I hope it helps
>
> Index: src/share/man/man5/hostname.if.5
> ===================================================================
> RCS file: /cvs/src/share/man/man5/hostname.if.5,v
> retrieving revision 1.65
> diff -u -p -u -r1.65 hostname.if.5
> --- src/share/man/man5/hostname.if.5    10 Mar 2017 18:28:11 -0000    1.65
> +++ src/share/man/man5/hostname.if.5    23 Sep 2017 11:50:49 -0000
> @@ -91,6 +91,16 @@ Regular IPv4 network setup:
>  .Va dest_addr
>  .Ed
>  .Pp
> +Point to Point IPv4 network setup:
> +.Bd -ragged -offset indent
> +.Li inet
> +.Op Li alias
> +.Va addr
> +.Va netmask
> +.Va network_addr
> +.Va options
> +.Ed
> +.Pp
>  Regular IPv6 network setup:
>  .Bd -ragged -offset indent
>  .Li inet6
> @@ -122,6 +132,13 @@ inet6 alias fec0::1 64
>  inet6 alias fec0::2 64 anycast
>  !route add 65.65.65.65 10.0.1.13
>  up
> +.Ed
> +.Pp
> +Point to point ip addressing can also be applied to an interface
> +for example:
> +.Bd -literal -offset 1n
> +inet 10.64.100.2 0xffffffff 10.64.80.25
> +#    host_addr  /32_netmask network_addr
>  .Ed
>  .Pp
>  The above formats have the following field values:

Reply via email to