TIP: Click on subject to list as thread! ANSI
echo: fidonews
to: FABIO BIZZI
from: MICHIEL VAN DER VLIST
date: 2019-06-16 15:49:00
subject: Ten Years Ago

Hello Fabio,

On Sunday June 16 2019 15:31, you wrote to me:

 MV>> reserved range. 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 or
 MV>> 100.64.0.0/10.

 FB> The last class 100.64.0.0/10 is reserved for the internal connections
 FB> (like p2p) of the provider's devices and it shoudn't be used for the
 FB> customer's network (like for the end user ip address, neither for the
 FB> nat of this one)

I deliberately wrote "reserved range" instead of "private range". The range
100.64.0.0/10 (RFC6598) should indeed not be used for local adresses in the
customers network. (RFC1918) But they ARE used as addresses handed out to CPE'.
On my 3G internet dongle I often get an RFC1918 address. Using RFC6598
addresses for the WAN address in the CPE avoids conflicts with RFC1918
addresses in the LAN part of the CPE.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.