bugzilla-daemon at netfilter.org
2013-May-04 19:17 UTC
[Bug 514] Making DNAT --to-destination resolve service named of port
https://bugzilla.netfilter.org/show_bug.cgi?id=514 Richard Clark <richardc at cybrick.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |richardc at cybrick.com Resolution|DUPLICATE | --- Comment #2 from Richard Clark <richardc at cybrick.com> 2013-05-04 21:17:46 CEST --- It was marked as a duplicate, but it it is a different module, and the fix under bug 482 did not fix this bug. This behaviour is still in iptables v1.4.14 for the DNAT module root at system:~# iptables -t nat -A zone_wan_dnat -p tcp -d 111.111.111.111 --dport ssh -j DNAT --to-destination 10.1.1.1:22 root at system:~# iptables -t nat -A zone_wan_dnat -p tcp -d 111.111.111.111 --dport ssh -j DNAT --to-destination 10.1.1.1:ssh iptables v1.4.14: Port `ssh' not valid This issue is pretty old, so I am not sure if this is still the proper area to file it now. Linux system 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux -- Configure bugmail: https://bugzilla.netfilter.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
Reasonably Related Threads
- [Bug 514] New: Making DNAT --to-destination resolve service named of port
- [Bug 514] Making DNAT --to-destination resolve service named of port
- [Bug 1428] New: Unable to dnat to port without defining destination address in inet table
- Need destination zone with DNAT- in shorewall-perl 4.2.1?
- [Bug 850] New: DNAT applied even after deleting the IP Tables DNAT Rule