Path: csiph.com!news.swapon.de!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: Kevin Osthoff Newsgroups: comp.os.linux.networking Subject: Re: Separate two network bridges on linux Date: Sat, 23 Jun 2018 00:10:31 +0200 Lines: 27 Message-ID: <87muvma2w8.fsf@gmx.de> References: <878t77c331.fsf@gmx.de> <87y3f7ajhn.fsf@gmx.de> <87tvpuadm8.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain X-Trace: news.dfncis.de J28FrRQlJH/3a1DhBte4QgN9sVFPhzlSomg35vKCFCpEGkYH7piPJqGiXe Cancel-Lock: sha1:gMUirCJ7Ch6RJ6wEbBdjR4gUBk0= sha1:UhApDQQVNwdZfLQ7In6qzt+7GRE= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) Xref: csiph.com comp.os.linux.networking:4154 Grant Taylor writes: > That's just it. The kernel does forward packets between interfaces > unless you expressly stop it. > > [...] > > Bridge logical interfaces should behave the same way as physical > interfaces (in this context). Both physical and logical need > something to stop traffic from being forwarded. Ok thanks for the clearification. Do different unix operating systems behave differently regarding this aspect? Is this what is called strong / weak host model? > Filtering is necessary. The kernel has routes to both networks. So > any traffic that comes into the kernel is routed to where it needs to > go, be it the other network or the Internet. Ok i will setup filter rules. Thanks for your help. Best regard Kevin! -- No fun. Not ever!