We all thought outbound meant outbound from your network. Your use of -i eth0 also gave that impression since -i isn't valid for matching traffic originating on your own machine and travelling out onto the network. The PREROUTING chain is never matched by traffic originating on your own box and heading outward. Only the OUTPUT and POSTROUTING chains are. The REDIRECT target is valid only in REROUTING and OUTPUT. Try using it in OUTPUT. On Tue, Aug 5, 2008 at 11:46, Shawn Fitzgerald <sargon97@xxxxxxxxx> wrote: > I have not logged any incoming packets. I only want to redirect > outbound traffic to localhost 8080. I have only one nic card, eth0 and > it is up. Is it possible that some kernel configuration is causing > problems? > > Thanks, Shawn > > On Mon, Aug 4, 2008 at 11:31 PM, Michele Petrazzo - Unipex srl > <michele.petrazzo@xxxxxxxxx> wrote: >> Shawn Fitzgerald wrote: >>> >>> I did an iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j >>> REDIRECT --to-ports 8080 and nothing. Just to make sure the firewall was up >>> I entered iptables -A OUTPUT -j DROP and it did block all outbound traffic. >>> >>> What am I missing here? >>> >> >> Nothing it's not an answer. >> How it's your lan? How are connected your eth0? Have you log the >> incoming packets *before* redirect? Have you tried to tcpdump? >> Too little infos... >> >> Michele >> > -- > To unsubscribe from this list: send the line "unsubscribe netfilter" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
