Jon wrote: > > Well, OK. I had hoped that would be overkill for this situation, but > here it is (lower). > >> But -- these issues are virtually never problems that you can diagnose >> by looking just at the firewall itself. The DNAT troubleshooting tips in >> FAQs 1a and 1b are still your best friends (as is a packet sniffer like >> tcpdump or wireshark).
Have you used a packet sniffer yet to see what is happening? > I must admit that I had hoped such a succinct problem as "standard ports > don't work but non-standard ports do" would ring a bell amongst the list > members. The only difference between "standard" and "non-standard" ports is in your mind. Neither Shorewall nor any of the software that it configures understands the concept of "standard" vs "non-standard" ports (although Netfilter has support for certain problem applications like FTP). I hope that I'm not a "one of". Being a one-of is an > interesting thing for those who come after, but a truly crappy thing to > be in the first place. > > Requested info: You are having a connection problem (external clients cannot connect to your internal server. According to the flowchart and text in the support guidelines, that calls for the output of "shorewall dump" collected in a particular manner. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- 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
