Re: Multi-Networking in Linux - Multiple Subnets

"Carlos E. R." <[email protected]> Fri, 31 Jul 2026 14:04:37 +0200
Newsgroups comp.os.linux.misc
Message-ID <[email protected]>
On 2026-07-30 13:59, Robert Heller wrote:
> At Thu, 30 Jul 2026 13:42:04 +0200 Marc Haber <[email protected]> wrote:
> 
>>
>> "Carlos E. R." <[email protected]> wrote:
>>> eth0: flagsA63<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>>          inet 192.168.2.9  netmask 255.255.0.0  broadcast 192.168.255.255
>>
>> Using the entire 192.168.0.0/16 range for a single home network is a
>> sure sign of a person not knowing too much about networking or an
>> incompetent ISP.
> 
> Indeed.  If one really needs a class B sub-net for one's home netwoek (64K
> nodes?) I believe there are class B sub-nets under 172.16.0.0 to
> 172.31.255.255. 

Which I can not use. That modification to the ISP router will render it not working.

> The 192.168.*.0 sub-nets are for class Class C Private
> sub-nets.

LOL. ChatGPT just said to me:

The IPv4 address ranges reserved for private local networks (defined in RFC 1918) are:

| Private range                     | CIDR notation    | Number of addresses | Common use                                      |
| --------------------------------- | ---------------- | ------------------: | ----------------------------------------------- |
| **10.0.0.0 – 10.255.255.255**     | `10.0.0.0/8`     |          16,777,216 | Large enterprise networks, cloud infrastructure |
| **172.16.0.0 – 172.31.255.255**   | `172.16.0.0/12`  |           1,048,576 | Medium to large private networks                |
| **192.168.0.0 – 192.168.255.255** | `192.168.0.0/16` |              65,536 | Home routers and small office networks          |

It gives no link for this information, except citing RFC 1918

-- 
Cheers,
        Carlos E.R.
        ESπŸ‡ͺπŸ‡Έ, EUπŸ‡ͺπŸ‡Ί;