libipq NAT causes RSTs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Hello *,
first of all, I _know_ I should use netfilter_queue. I don't because libipq actually has a quite nice documentation, being a set of man-pages. Unable to find something comparable for netfilter_queue I to stick to using libipq (even though having more than one queue sounds darn interesting to me)
But for the problem, maybe it's my bad. Most probably! Even in that case I'd be glad if someone to pointed that out to me!
I'm currently (trying) to write a transparent proxy application, using libipq to capture packets + iptables' redirect mechanism.
The basic idea works as follows:
+---+ +---+ +---+ | S |<---->| P |<---->| D | +---+ (1) +---+ (2) +---+
(1) uses iptables' REDIRECT target; the received data is then forwarded, using another socket connection (2)
(2) uses libipq to do some kind of SNAT and change the local source address to S's address and vice versa for the incoming packets from D
So far the theory. The application works fine, as long, as I do not remap the source port (destination port, respectively) from P to D (2). Once I enable the port remapping I get
a) syslog messages like the following:
[ 7742.939471] ip_rt_bug: [S' IP] -> [P's IP at (2)], ?
b) RST packets from P towards D, using exactly all the correct TCP settings, except for the destination port, (being 1, sometimes 2, or 3, I couldn't figure out, why)
The three-way-handshake works fine, the RSTs are generated for the _first_ packet to contain a _TCP-payload_. Also netstat tells me, there is an established connection between P and D, but somehow (I assume that this might be the trouble) looking for the corresponding socket connection on P fails.
I'm totally puzzled why that happens. libipq reinjects the packets with properly changed checksums and whatnot, yet the RSTs are generated. I've also tried NF_REPEAT, instead of the NF_ACCEPT verdict. The behavior remains identically.
Any ideas, anyone?
Thanks in advance
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHYU6AUGqFG0l5Kr0RA3DMAJ91LfFI2rkjx5Q80XG1paLg49PRAQCgvPQ3 eAu14RJDYpgiLS03lpSthDU=
=gGsR
-----END PGP SIGNATURE-----
Quoted 32 lines · Thomas Egerer
I'm currently (trying) to write a transparent proxy application, using libipq to capture packets + iptables' redirect mechanism. The basic idea works as follows:
+---+ +---+ +---+ | S |<---->| P |<---->| D | +---+ (1) +---+ (2) +---+(1) uses iptables' REDIRECT target; the received data is then forwarded, using another socket connection (2)
(2) uses libipq to do some kind of SNAT and change the local source address to S's address and vice versa for the incoming packets from DSo far the theory. The application works fine, as long, as I do not remap the source port (destination port, respectively) from P to D (2). Once I enable the port remapping I get
a) syslog messages like the following:[ 7742.939471] ip_rt_bug: [S' IP] -> [P's IP at (2)], ?b) RST packets from P towards D, using exactly all the correct TCP settings, except for the destination port, (being 1, sometimes 2, or 3, I couldn't figure out, why)
The three-way-handshake works fine, the RSTs are generated for the _first_ packet to contain a _TCP-payload_. Also netstat tells me, there is an established connection between P and D, but somehow (I assume that this might be the trouble) looking for the corresponding socket connection on P fails.
I'm totally puzzled why that happens. libipq reinjects the packets with properly changed checksums and whatnot, yet the RSTs are generated. I've also triedNF_REPEAT, instead of theNF_ACCEPTverdict. The behavior remains identically.
Quoted 1 line
Any ideas, anyone?
Most likely you're changing the source to a non-local address in LOCAL_OUT, causing rerouting of the packet and resulting in an input route instead of an output one. When dst_output is called you hit ip_rt_bug, dropping the packet. When this is the first packet of a connection, the connection tracking entry and NAT mappings are destroyed. Not sure whats causing the RSTs then, but its probably related to that.
Does changing:
return ip_route_me_harder(skb, RTN_UNSPEC);
to
return ip_route_me_harder(skb, RTN_LOCAL);
in net/ipv4/netfilter.c:nf_ip_reroute have any effect?