Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Andy Burns Newsgroups: comp.os.linux.misc Subject: Re: Multi-Networking in Linux - Multiple Subnets Date: Thu, 30 Jul 2026 15:06:12 +0100 Lines: 19 Message-ID: References: <114fdad$1trk7$1@news1.tnib.de> <114flbe$1qul5$4@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net tt4fLR0f+REa568Lf7Wv0g2vQcKEmVAGHdOLBe/yulA4KcALu4 Cancel-Lock: sha1:Dbrz7D/TyLoombR/xngZ5qhPTOY= sha256:0FWn+YljefbYIlhTbmdEd+obXhR6PY8rH6fm7liZxoM= User-Agent: Mozilla Thunderbird Content-Language: en-GB In-Reply-To: <114flbe$1qul5$4@dont-email.me> Xref: csiph.com comp.os.linux.misc:89245 The Natural Philosopher wrote: > Andy Burns wrote: > >> If you want multiple IP subnets on a single ethernet network, you'd be >> better off using VLANs, even cheapo switches can handle that, then >> your linux box with a single NIC can have VLAN sub-interfaces e.g. >> eth1.1 on 192.168.0.1/24 and eth1.10 on 192.168.1.0/24 >> >> If you don't want VLANs you *could* use a NIC alias so that e.g. eth1 >> is on 192.168.0.1/24 and the alias eth1:2 is on 192.168.1.1/24 ... but >> why? > > They look the same to me. Sure the names of the interfaces are just one character different (a colon vs a fullstop) but with VLANs, each sub-interface will keep its traffic isolated, won't see broadcast/multicast traffic from the other one ...