Shorewall users - Mar 2006 - Unreplied message when i try to connect to an internal system

Unreplied message when i try to connect to an internal system

I''ve set up a shorewall 3.0.5 system on Fedora core 4

When i want to connect from an external computer to one in my network it does
not reply.

I connect from 212.19.195.160 to 212.178.64.74 trough port 8080 

The rule i made is: DNAT  net   loc:192.168.0.20:80  tcp  8080 - 212.178.64.74

(and 192.168.0.20 can be reached from inside my network).

In /var/log/messages it says it is accepted but when i do an dump in shorewall
the line tcp 6 116 SYN_SENT src=212.19.195.160 dst=212.178.64.74 sport=1782
dport=8080 packets=2 bytes=96 [UNREPLIED] src=192.168.0.20 dst=212.19.195.160
sport=80 dport=1782 packets=0 bytes=0 mark=0 use=1 apears.

Why is al my internal trafic blocked?

Thanks, 

Wendy

On Tuesday 07 March 2006 01:24, w.haasewinkel@qualityonline.nl
wrote:
> I''ve set up a shorewall 3.0.5 system on Fedora core 4
> When i want to connect from an external computer to one in my network it
> does not reply. I connect from 212.19.195.160 to 212.178.64.74 trough port
> 8080
> The rule i made is: DNAT  net   loc:192.168.0.20:80  tcp  8080 -
> 212.178.64.74 (and 192.168.0.20 can be reached from inside my network).
> In /var/log/messages it says it is accepted but when i do an dump in
> shorewall the line tcp 6 116 SYN_SENT src=212.19.195.160 dst=212.178.64.74
> sport=1782 dport=8080 packets=2 bytes=96 [UNREPLIED] src=192.168.0.20
> dst=212.19.195.160 sport=80 dport=1782 packets=0 bytes=0 mark=0 use=1
> apears. Why is al my internal trafic blocked?
Most likely, the default gateway on host 192.168.0.20 isn''t set to the
IP
address of your local interface (192.168.0.133).

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key