> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: 17 January 2005 22:59
> To: Dave Page
> Cc: Michael Paesold; Josh Berkus; PostgreSQL WWW Mailing List
> Subject: Re: [pgsql-www] Fwd: [pgsql-advocacy] Website: links
> to wwwmaster.postgresql.org don't work for me
>
> "Dave Page" <dpage@vale-housing.co.uk> writes:
> > Can you ping and traceroute to demon-gw.vale-housing.co.uk?
> That's the
> > upstream router...
>
> FWIW, from here 194.217.48.42 responds to ping, but
> traceroute cuts off
> at the upstream --- maybe that's what you expect.
Yes, entirely - in fact I can see the firewall dropping UDP packets from
sss.pgh.pa.us:
Jan 17 22:57:21 net2all:DROP:IN=eth0 OUT= SRC=66.207.139.130
DST=194.217.48.42 LEN=48 TOS=0x00 PREC=0x00 TTL=4 ID=52521 PROTO=UDP
SPT=44784 DPT=33500 LEN=28
I have just noticed a few of these go though:
Jan 17 23:05:41 newnotsyn:DROP:IN=eth0 OUT= SRC=201.246.86.173
DST=194.217.48.42 LEN=52 TOS=0x08 PREC=0x00 TTL=42 ID=52338 DF PROTO=TCP
SPT=1079 DPT=80 WINDOW=16024 RES=0x00 ACK FIN URGP=0
The comment in the config file says:
TCP packets that don't have the SYN flag set and which are not part of
an established connection will be accepted from this interface, even if
NEWNOTSYN=No has been specified in /etc/shorewall/shorewall.conf.
NEWNOTSYN was set to No, I've just changed it to Yes - Alexey, Michael;
any difference?
Regards, Dave.
