Re: Multi-Networking in Linux - Multiple Subnets
c186282 <[email protected]> Fri, 31 Jul 2026 01:16:13 -0400
| Newsgroups | comp.os.linux.misc |
|---|---|
| Organization | wokiesux |
| Message-ID | <[email protected]> |
On 7/31/26 01:08, rbowman wrote: > On Thu, 30 Jul 2026 21:53:18 +0200, Marc Haber wrote: > >> rbowman <[email protected]> wrote: >>> On Thu, 30 Jul 2026 18:43:11 +0200, Marc Haber wrote: >>> >>>> With a /16 Netmask, covering the entire 192.168 RFC 1918 range, as if >>>> we have plenty of IPv4 addresses? >>>> >>>> Please, let me see that ISPs customer documentation. They do have it >>>> online, don't they? I'm familiar with that industry for nearly 30 >>>> years and have never seen a setup like that. It sounds so brain-dead >>>> that my first idea was that you haven't understood. >>> >>> wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >>> inet 192.168.1.124 netmask 255.255.255.0 broadcast >>> 192.168.1.255 >>> >>> It's the same on the machine with a wired connection. >> >> Please get the basics of IP networking right and take a look at the >> netmask. >> >> Greetings Marc > > Networking isn't an area where I have any great deal of skills. I plug the > stuff in and it works. I'm not going to screw around for the sake of some > hypothetical purity. I'm kind of the same way. It's SO complex under the hood ... well ... it'd better Just Work. I know I'm asking for something a bit out of the ordinary. There have been a few proposed options I'm gonna look into. However I'm not gonna massively edit huge scripts or config files, requiring arcane knowledge. The more "standard" the better. The modern environment CAN use up more than 254 addresses - or at least CROWD the 254 so badly that it's hard to organize. With "IOT" stuff this will just get WORSE.