Hello, as far as I know, 44.128.0.0/16 is reserved for testing and experimentation and should be treated much like an RFC1918 subnet. That means it will not be routable to anyone (although it is advertised on BGP). So I have a few questions about its use:
1. Can an AMPRNet member use 44.128.0.0/16 in their home instead of, let’s say, 192.168.1.0/24? Note that I am not talking about routing these addresses, just use them in a non-connected place. 2. Can a non-ham use 44.128.0.0/16 in their home instead of, let’s say, 192.168.1.0/24? 3. Can a company use 44.128.0.0/16 for their intranet, instead of, let’s say, 10.0.0.0/8?
Note than in all three cases, nobody is connected to 44net gateways and just use the network like any other private address. I am aware that there’s no technical limitation in doing this and there are hardly any benefits from doing this, however I am asking for informational purposes.
Thanks!
Although it would, at this moment, not have any significant effect on the operation of the network if someone used it and it leaked out, I feel it would be wise to avoid using it at all for anything permanent or semi-permanent, as some day we may decide to assign it somewhere and start routing it.
Some years ago a large router company used 44.x.x.x addresses as examples in their documentation. As one might expect, some people used them right out of the examples and they leaked. It's always wise not to trust every single router configuration to get things right, and it would only take one to complicate things.
So my advice is to avoid using 44.128.x.x for anything other than really short tests. There are plenty of non-routed RFC1918 addresses and subnets available and they are much less likely to get propagated anywhere if they leak. - Brian
On Sun, Aug 21, 2016 at 07:37:23PM +0300, DaKnOb wrote:
as far as I know, 44.128.0.0/16 is reserved for testing and experimentation and should be treated much like an RFC1918 subnet. That means it will not be routable to anyone (although it is advertised on BGP). So I have a few questions about its use:
- Can an AMPRNet member use 44.128.0.0/16 in their home instead of, let’s say, 192.168.1.0/24? Note that I am not talking about routing these addresses, just use them in a non-connected place.
- Can a non-ham use 44.128.0.0/16 in their home instead of, let’s say, 192.168.1.0/24?
- Can a company use 44.128.0.0/16 for their intranet, instead of, let’s say, 10.0.0.0/8?
Note than in all three cases, nobody is connected to 44net gateways and just use the network like any other private address. I am aware that there’s no technical limitation in doing this and there are hardly any benefits from doing this, however I am asking for informational purposes.
Thanks!
I seem to recall 44.x.x.x being used at large trade shows 20 years ago or so....
On Sun, Aug 21, 2016 at 10:24 AM, Brian Kantor Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ Although it would, at this moment, not have any significant effect on the operation of the network if someone used it and it leaked out, I feel it would be wise to avoid using it at all for anything permanent or semi-permanent, as some day we may decide to assign it somewhere and start routing it.
Some years ago a large router company used 44.x.x.x addresses as examples in their documentation. As one might expect, some people used them right out of the examples and they leaked. It's always wise not to trust every single router configuration to get things right, and it would only take one to complicate things.
So my advice is to avoid using 44.128.x.x for anything other than really short tests. There are plenty of non-routed RFC1918 addresses and subnets available and they are much less likely to get propagated anywhere if they leak. - Brian
On Sun, Aug 21, 2016 at 07:37:23PM +0300, DaKnOb wrote:
as far as I know, 44.128.0.0/16 is reserved for testing and
experimentation and should be treated much like an RFC1918 subnet. That means it will not be routable to anyone (although it is advertised on BGP). So I have a few questions about its use:
- Can an AMPRNet member use 44.128.0.0/16 in their home instead of,
let’s say, 192.168.1.0/24? Note that I am not talking about routing these addresses, just use them in a non-connected place.
- Can a non-ham use 44.128.0.0/16 in their home instead of, let’s say,
192.168.1.0/24?
- Can a company use 44.128.0.0/16 for their intranet, instead of,
let’s say, 10.0.0.0/8?
Note than in all three cases, nobody is connected to 44net gateways and
just use the network like any other private address. I am aware that there’s no technical limitation in doing this and there are hardly any benefits from doing this, however I am asking for informational purposes.
Thanks!
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
This network is used by NASDAQ for their test network. I constantly ran into it when I worked on Wall Street. I've reported this before but it always goes nowhere.
Mark
On Aug 21, 2016 14:48, "K7VE - John" k7ve@k7ve.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ I seem to recall 44.x.x.x being used at large trade shows 20 years ago or so....
On Sun, Aug 21, 2016 at 10:24 AM, Brian Kantor Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ Although it would, at this moment, not have any significant effect on the operation of the network if someone used it and it leaked out, I feel it would be wise to avoid using it at all for anything permanent or semi-permanent, as some day we may decide to assign it somewhere and start routing it.
Some years ago a large router company used 44.x.x.x addresses as examples in their documentation. As one might expect, some people used them right out of the examples and they leaked. It's always wise not to trust every single router configuration to get things right, and it would only take one to complicate things.
So my advice is to avoid using 44.128.x.x for anything other than really short tests. There are plenty of non-routed RFC1918 addresses and subnets available and they are much less likely to get propagated anywhere if they leak. - Brian
On Sun, Aug 21, 2016 at 07:37:23PM +0300, DaKnOb wrote:
as far as I know, 44.128.0.0/16 is reserved for testing and
experimentation and should be treated much like an RFC1918 subnet. That means it will not be routable to anyone (although it is advertised on
BGP).
So I have a few questions about its use:
- Can an AMPRNet member use 44.128.0.0/16 in their home instead of,
let’s say, 192.168.1.0/24? Note that I am not talking about routing
these
addresses, just use them in a non-connected place.
- Can a non-ham use 44.128.0.0/16 in their home instead of, let’s
say,
192.168.1.0/24?
- Can a company use 44.128.0.0/16 for their intranet, instead of,
let’s say, 10.0.0.0/8?
Note than in all three cases, nobody is connected to 44net gateways and
just use the network like any other private address. I am aware that there’s no technical limitation in doing this and there are hardly any benefits from doing this, however I am asking for informational purposes.
Thanks!
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
--
John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 http://k7ve.org/blog http://twitter.com/#!/john_hays http://www.facebook.com/john.d.hays
On 8/21/16 12:37 PM, DaKnOb wrote:
- Can an AMPRNet member use 44.128.0.0/16 in their home instead of, let’s
say, 192.168.1.0/24? Note that I am not talking about routing these addresses, just use them in a non-connected place. 2. Can a non-ham use 44.128.0.0/16 in their home instead of, let’s say, 192.168.1.0/24? 3. Can a company use 44.128.0.0/16 for their intranet, instead of, let’s say, 10.0.0.0/8?
Yes, people even used 5.0.0.0/8 like RFC1918 space before. No one can dictate what space you use in your own private network.
Is it a good idea? no.
-
Brian Kantor -
Bryan Fields -
DaKnOb -
K7VE - John -
Mark Phillips