netdev - Re: Veth problems with bridge

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: <4845621E.6080104@inqnet.at>
Date:	Tue, 03 Jun 2008 17:24:14 +0200
From:	Bernhard Miklautz <miklautz@...net.at>
To:	Patrick McHardy <kaber@...sh.net>
CC:	linux-net@...r.kernel.org,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: Veth problems with bridge

Hi Patrick,

Patrick McHardy wrote:
> Bernhard Miklautz wrote:
>> [...]
>> I also tried the whole setup without using veth; the IP directly bound
>> to br0, as well as without the bridge at all. No problems with that.
>> So there might be some problems with veth?
> 
> Does "echo 0 > /proc/sys/net/bridge/bridge-nf-call-iptables" fix it?

On my hardware machine this seems to fix the problem :). But why does
bridge-nf-call-iptables influent source nat on an other interface? -
Shouldn't the source address always be translated when an output
interface is set (iptables -A POSTROUTING -o eth3 -t nat -j MASQUERADE)?

Thanks for you quick help.

Best regards,
Bernhard


--
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