On 3/20/07, Jon <[EMAIL PROTECTED]> wrote: > I didn't make the "Your ISP is blocking SYN/ACK packets" leap because > the server in question is not mine. Therefore "my ISP" to me means by > rather tried and true connection which I knew be clean. Of course Tom > wouldn't know that and as soon as I realized that we could be talking > about the other server, it all came together. The owner of that server > does indeed have a "home" account and therefore it looks like ACKs are > being blocked. Yep, no great surprise there. I wish ISPs wouldn't filter my internet traffic at all, but that's not likely to happen any time soon.
> I presume, anyhow, that's what this type of trace shows? I am the 142. > and the server in question is the 66. There are no other packets with > those IPs in the trace and since I only see SYNs. I see other > connections in the trace that show ACKs, just nothing involving these > two IPs. That's correct. You could add a rule in the filtering with something like "host 66.222.148.326" and it'll only show packets to or from that host. > Thanks for the tip! Glad to hear it helped. Will ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
