netdev - Re: IP-less bridge as a martian source

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87wsg0wu78.fsf@tac.ki.iif.hu>
Date:	Wed, 22 Oct 2008 17:00:43 +0200
From:	Ferenc Wagner <wferi@...f.hu>
To:	netdev@...r.kernel.org
Subject: Re: IP-less bridge as a martian source

Ferenc Wagner <wferi@...f.hu> writes:

> I expected an IP-less bridge interface to pick up no IP packets, but
> apparently this isn't the case: broadcast packets with destination
> address 255.255.255.255 are reported as martians by the 2.6.18
> kernel, which I find counterintuitive (I know 2.6.18 is rather old,
> but that's the one supported by Xen).
>
>   1. Is this the expected behaviour?
>
>   2. I tried to cut down the logs by explicit iptables drops, but
>      didn't succeed.  Does martian detection happen before the
>      netfilter rules?  (I know I can disable martian logging by
>      interface, but wanted finer granularity.)
>
> If somebody could also enlighten me on the following [...]

That packet doubling turned out to be a bonding configuration error:
it was in round-robin mode instead of active-backup (part of joys of
ditstro upgrade).  Also I found a way to probe the above question
under 2.6.26, but I'd still be interested in the expected behaviour.
-- 
Thanks,
Feri.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html