Re: [PATCH net-next 1/1] Allow 0.0.0.0/8 as a valid address range

2019-07-13 Thread Paul Marks
On Wed, Jun 26, 2019 at 1:20 PM David Miller wrote: > > From: Dave Taht > Date: Sat, 22 Jun 2019 10:07:34 -0700 > > > The longstanding prohibition against using 0.0.0.0/8 dates back > > to two issues with the early internet. > > > > There was an interoperability problem with BSD 4.2 in 1984, fixe

Re: [PATCH net-next 1/1] Allow 0.0.0.0/8 as a valid address range

2019-06-26 Thread David Miller
From: Dave Taht Date: Sat, 22 Jun 2019 10:07:34 -0700 > The longstanding prohibition against using 0.0.0.0/8 dates back > to two issues with the early internet. > > There was an interoperability problem with BSD 4.2 in 1984, fixed in > BSD 4.3 in 1986. BSD 4.2 has long since been retired. > >

[PATCH net-next 1/1] Allow 0.0.0.0/8 as a valid address range

2019-06-22 Thread Dave Taht
The longstanding prohibition against using 0.0.0.0/8 dates back to two issues with the early internet. There was an interoperability problem with BSD 4.2 in 1984, fixed in BSD 4.3 in 1986. BSD 4.2 has long since been retired. Secondly, addresses of the form 0.x.y.z were initially defined only as

Re: [RFC PATCH net-next 1/1] Allow 0.0.0.0/8 as a valid address range

2019-06-13 Thread Toke Høiland-Jørgensen
Dave Taht writes: > The longstanding prohibition against using 0.0.0.0/8 dates back > to two issues with the early internet. > > There was an interoperability problem with BSD 4.2 in 1984, fixed in > BSD 4.3 in 1986. BSD 4.2 has long since been retired. > > Secondly, addresses of the form 0.x.y.

[RFC PATCH net-next 1/1] Allow 0.0.0.0/8 as a valid address range

2019-06-13 Thread Dave Taht
The longstanding prohibition against using 0.0.0.0/8 dates back to two issues with the early internet. There was an interoperability problem with BSD 4.2 in 1984, fixed in BSD 4.3 in 1986. BSD 4.2 has long since been retired. Secondly, addresses of the form 0.x.y.z were initially defined only as