<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Dean,</div><div><br></div><div>Have you tried using a traceroute -I to use ICMP for the traceroute? A default traceroute will choose random UDP ports at the destination, so your firewall rules WILL kill those. I would suspect an ICMP based traceroute would work.</div><div><br></div><div>Nigel</div><br><div><div>On Apr 10, 2014, at 7:34 PM, Bart Kus <<a href="mailto:me@bartk.us">me@bartk.us</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/10/2014 07:23 PM, Dean Gibson
AE7Q wrote:<br>
</div>
<blockquote cite="mid:53475216.4040207@ae7q.com" type="cite"><font color="#3333ff"><small><tt> </tt><tt>add action=drop
chain=input comment="default configuration"
in-interface=wlan1-gateway</tt><tt><br>
</tt></small></font></blockquote>
My money is on that rule killing the inbound traceroute packets
before the router can formulate a response packet.<br>
<br>
--Bart<br>
<br>
</div>
_______________________________________________<br>PSDR mailing list<br><a href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a><br>http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org<br></blockquote></div><br></body></html>