Re: Multi-Networking in Linux - Multiple Subnets
The Natural Philosopher <[email protected]> Thu, 30 Jul 2026 13:32:46 +0100
| Newsgroups | comp.os.linux.misc |
|---|---|
| Organization | A little, after lunch |
| Message-ID | <[email protected]> |
On 30/07/2026 12: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. The 192.168.*.0 sub-nets are for class Class C Private > sub-nets. > If it's private it doesn't really matter: these networks were defined to NOT be on the public internet that's all, Many routers will allow multiple local networks to be defined and will route between them. If not the simple answer is to insert a linux machine preferably with two interfaces, but linux allows two IP addresses to be assigned to a single interface >> >>> Works for me as above :-) >> >> Until the moment you'd want to connect to another network. >> >> Greetings >> Marc > -- There is something fascinating about science. One gets such wholesale returns of conjecture out of such a trifling investment of fact. Mark Twain