netdev - Fwd: Linux bridge for route

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-next>] [day] [month] [year] [list]

Date:	Fri, 17 Jan 2014 17:14:34 +0800
From:	tingwei liu <tingw.liu@...il.com>
To:	netfilter-devel@...r.kernel.org, netfilter@...r.kernel.org,
	netdev@...r.kernel.org
Cc:	tingwei liu <tingw.liu@...il.com>
Subject: Fwd: Linux bridge for route

Dear all,

       There is  a question has puzzled me for a long time.
       You can find the topology from attachment.

       Normal traffic is:

               PC(192.168.1.8)--->Bridge(eth0)--->Bridget(eth1)--->NAT
server-->switch--->Server(192.168.5.3)

       Now I want the ssh traffic like this:
              PC(182.168.1.8)--->Bridge(eth0)--->eth2--->NAT
server--->switch--->Server(192.168.5.3)


      What I have done on LINUX Server:
              #net.bridge.bridge-nf-call-iptables = 1
              #iptables -t nat -A POSTROUTING -s 192.168.1.8 -p tcp
--dport 22 -j SNAT --to-source 192.168.5.2

      I have find the rule matched through command "iptables -t nat
-nvL", but the packets doesn't sent to 192.168.5.3.
      and "tcpdump -i eth2 tcp port 22" can not capture any packet!

Thanks very much!

Download attachment "topology.jpg" of type "image/jpeg" (84648 bytes)