<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/10/2014 06:57 PM, Dean Gibson
AE7Q wrote:<br>
</div>
<blockquote cite="mid:53474C0D.1020804@ae7q.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Resent with my correct eMail address ...<br>
<br>
<div class="moz-cite-prefix">On 2014-04-10 18:56, Dean Gibson
wrote:<br>
</div>
<blockquote cite="mid:53474BB5.6090507@mailpen.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">On 2014-04-10 18:27, Bart Kus
wrote:<br>
</div>
<blockquote cite="mid:53474501.7050702@bartk.us" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
....<br>
<blockquote cite="mid:534741C0.5050400@ae7q.com" type="cite">
<br>
<i><small><font color="#009900"><tt>>traceroute
44.24.240.173</tt><tt><br>
</tt><tt>traceroute to 44.24.240.173 (44.24.240.173),
30 hops max, 38 byte packets</tt><tt><br>
</tt><tt> 1 209.59.211.184 (209.59.211.184) 0.172
ms 0.075 ms 0.062 ms</tt><tt><br>
</tt><tt> ...</tt><tt><br>
</tt><tt>17 44.24.242.19 (44.24.242.19) 95.778 ms
98.257 ms 95.279 ms</tt><tt><br>
</tt><tt>18 44.24.242.10 (44.24.242.10) 142.098 ms
103.353 ms 148.017 ms</tt><tt><br>
</tt><tt>19 44.24.240.132 (44.24.240.132) 137.942
ms 112.522 ms 113.787 ms</tt></font><tt><br>
</tt><tt>20 * * *</tt><tt><br>
</tt><tt>21 * * *</tt></small></i><br>
<br>
</blockquote>
<br>
Nope, that shouldn't be. The network correctly routed your
packets to the right sector @ Paine, and then failed on the
very last hop in communicating with your modem? Depending on
where the trace was originating from and the state of your
modem's routing table at the time, your modem may have had
different ideas about how to reply. Or, you might have been
disconnected at the time?<br>
<br>
Where are these following traces from? The modem? Was there
a specific source IP used?<br>
</blockquote>
<br>
The trace came from my computer on the Internet at
209.59.217.159, with the exact command you see above. Are you
sure that 44.24.240.132 is the right sector?</blockquote>
</blockquote>
<br>
Yes, absolutely sure:<br>
<br>
<tt>[eo@Paine-s2] > /ip address print </tt><tt><br>
</tt><tt>Flags: X - disabled, I - invalid, D - dynamic </tt><tt><br>
</tt><tt> # ADDRESS NETWORK
INTERFACE
</tt><tt><br>
</tt><tt> 0 ;;; default configuration</tt><tt><br>
</tt><tt> 44.24.240.132/28 44.24.240.128
ether1-local
</tt><tt><br>
</tt><tt> 1 44.24.240.161/28 44.24.240.160
wlan1-gateway
</tt><tt><br>
</tt><br>
The modem has 2 interfaces, so 2 IPs. Which IP you see along the
trace depends on the direction your trace is taking.<br>
<br>
<blockquote cite="mid:53474C0D.1020804@ae7q.com" type="cite">
<blockquote cite="mid:53474BB5.6090507@mailpen.com" type="cite">
Everything I see comes from 44.24.240.161. Note (not included
above but in my previous message) that I can traceroute to .132
OK, but attempting to go any further back in the inbound
traceroute list, seems to repeat a HamWAN IP address and then <b>stop</b>.
The modem was on, I was monitoring it with <font
color="#3333ff"><b>/interface wireless monitor 0</b></font>,
and the "last-ip" field never changed (as it usually does on an
attempted access).<br>
<br>
</blockquote>
</blockquote>
<br>
Can you show your modem's routing table and firewall here? (/ip
route export; /ip firewall export)<br>
<br>
<blockquote cite="mid:53474C0D.1020804@ae7q.com" type="cite">
<blockquote cite="mid:53474BB5.6090507@mailpen.com" type="cite">
When I post my various messages, none of them are at all urgent,
but I like to post "anomalies" if they are of help in
administration. I'm just experimenting.<br>
</blockquote>
<br>
</blockquote>
<br>
That's cool, the bug-finding is appreciated. Although in this case,
I suspect it's on your end.<br>
<br>
--Bart<br>
<br>
</body>
</html>