![](https://seccdn.libravatar.org/avatar/926aae47e9d1677af3799a66f39f330d.jpg?s=120&d=mm&r=g)
* Ken Hughes; <ken@hughesfamily.com> on 26 Mar, 2002 wrote:
Sorry for jumping in here, but I hope this can help with a problem I'm having with port redirection in FW2. The redirection you gave is what I have in SuSEfirewall, but with FW2 in the above example, we're told we would have to put a "tcp" in between the dest(0/0) and the origin port (80). I find this odd since apparently your example works but I wanted to get clarification if possible..
Well I am not using SuSEfirewall2 (as I am running my fw with 2.2.19 so it is SUSEfirewall5-1) However quoting from the firewall2.rc.config says you are correct sorry my mistake. # A redirecting rule consists of 1) source IP/net, 2) destination # IP/net, # 3) protocol (tcp or udp) 3) original destination port and 4) local # port to # redirect the traffic to, seperated by a colon. e.g.: # "10.0.0.0/8,0/0,tcp,80,3128 0/0,172.20.1.1,tcp,80,8080" # 1 2 3 4 5 FW_REDIRECT="192.168.0.0/24,0/0,tcp,80,3128" would be the correct way for *SuSEfirewall2*. In the mean time Marc heuse needs to update this comments I believe as I counted 5 parameters Sorry for the confusion ( Now I started wondering how it did work for Steve :-0 -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx