linux-kernel - SNATed connections show as original ip in /proc/net/tcp

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:	Sun, 11 Jul 2010 05:10:21 -0400
From:	"Noah McNallie" <n0ah@...h.org>
To:	linux-kernel@...r.kernel.org
Subject: SNATed connections show as original ip in /proc/net/tcp

just as the topic describes.

I'm currently doing SNAT to force some destination tcp ports to be routed  
through a specific route rather than the default route. To accomplish this  
I mark thoes packets with iptables, use 'ip' to specify marked packets via  
the specified route, and then use iptables to change their source address.

one problem i've noticed is that in netstat (and hence /proc/net/tcp) the  
connections are shown as their original source. this causes problems with  
some things such as identd, because identd won't see the SNATed to ip with  
that port open. hence it will reply that it has no connection.

anyway i can get around this?

noah
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/