Thank you for your help Tom. Indeed from FAQ17 "If the chain is FORWARD and the IN and OUT interfaces are the same, then you probably need the routeback option on that interface in /etc/shorewall/interfaces" solved the problem.
Sorry I missed that... -David Tom Eastep wrote: > David Rabby wrote: >> Hello, I've been trying solve this for the past few months and still >> no success. I would appreciate any hints as to what I am overlooking. > >> I've sent to [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> the >> status.txt.gz that is the output from */sbin/shorewall reset* and >> */sbin/shorewall dump > /tmp/status.txt* . The connection attempt >> that is failing shows up in the logs as: >> >> Jun 8 20:20:45 FORWARD:REJECT:IN=eth0 OUT=eth0 SRC=75.154.176.159 >> DST=72.55.144.9 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=51513 DF >> PROTO=TCP SPT=4161 DPT=82 WINDOW=65535 RES=0x00 SYN URGP=0 > > The above log message, along with your report, suggests that you have > been having a Shorewall issue "for the past few months" but haven't > thought to consult the Shorewall FAQ. > > See Shorewall FAQ 17. > > -Tom ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
