>> Michel Py wrote :
>> Result : IPv4 is still there, and now we have a mess. Had Class E become an
>> extension
>> of RFC1918, we would not have it because large folk who needed a bigger
>> private space
>> than 10/8 would have been quite happy with 240/4 (16 consecutive Class A).
>> Another
>> failed policy that produced the opposite effect of the intent.
> Ronald F. Guilmette wrote :
> I really have no knowledge of any of this, and your contentions are rather
> entirely perplexing. If people want to use 240.0.0.0/4 -internally- as
> private RFC1918 address space, who's preventing them from doing so?
Impossible. It's disabled in the stack, hard-coded as a martian or a bogon,
can't even configure it, name it.
C:\Users\Administrator>ping 240.1.2.3
Pinging 240.1.2.3 with 32 bytes of data
PING: transmit failed. General failure.
c2851-michel#conf t
Enter configuration commands, one per line. End with CNTL/Z.
c2851-michel(config)#inte loo 240
May 5 22:40:11.081 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Loopback240, changed state to up
c2851-michel(config-if)#ip add 240.1.2.3 255.255.255.0
Not a valid host address - 240.1.2.3
c2851-michel(config)#ip route 240.0.0.0 255.255.255.0 192.168.2.1
%Invalid destination prefix
Works great with Squatted DoD prefix, though :
c2851-michel#conf t
Enter configuration commands, one per line. End with CNTL/Z.
c2851-michel(config)#inte loo 30
May 5 22:47:13.675 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Loopback30, changed state to up
c2851-michel(config-if)#ip add 30.1.2.3 255.255.255.0
c2851-michel(config-if)#end
c2851-michel#ping 30.1.2.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 30.1.2.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
C:\Users\Administrator>ping 30.1.2.3
Pinging 30.1.2.3 with 32 bytes of data:
Reply from 30.1.2.3: bytes=32 time=1ms TTL=254
Reply from 30.1.2.3: bytes=32 time=1ms TTL=254
Reply from 30.1.2.3: bytes=32 time=1ms TTL=254
Reply from 30.1.2.3: bytes=32 time=1ms TTL=254
Ping statistics for 30.1.2.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
> As long as there are no route leaks for any of this to the outside world, I
> don't see the issue/problem.
Now you sound like Carlos.
Michel.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
