Errr, that should say "/ip route print"
instead, to show dynamic routes.
Also, you can engage the /tool sniffer quick to check for your
traceroute making it into your modem, just as you did before with
the routing issue. I wouldn't count on "last-ip" being an
accurate representation, it's just a random sampling of taffic and
can miss packets.
--Bart
On 04/10/2014 07:03 PM, Bart Kus wrote:
On 04/10/2014 06:57 PM, Dean Gibson
AE7Q wrote:
Resent with my correct eMail address ...
On 2014-04-10 18:56, Dean Gibson
wrote:
On 2014-04-10 18:27, Bart Kus
wrote:
....
>traceroute
44.24.240.173
traceroute to 44.24.240.173
(44.24.240.173), 30 hops max, 38 byte packets
1 209.59.211.184 (209.59.211.184) 0.172
ms 0.075 ms 0.062 ms
...
17 44.24.242.19 (44.24.242.19) 95.778 ms
98.257 ms 95.279 ms
18 44.24.242.10 (44.24.242.10) 142.098
ms 103.353 ms 148.017 ms
19 44.24.240.132 (44.24.240.132) 137.942
ms 112.522 ms 113.787 ms
20 * * *
21 * * *
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?
Where are these following traces from? The modem? Was
there a specific source IP used?
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?
Yes, absolutely sure:
[eo@Paine-s2] > /ip address print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK
INTERFACE
0 ;;; default configuration
44.24.240.132/28 44.24.240.128
ether1-local
1 44.24.240.161/28 44.24.240.160
wlan1-gateway
The modem has 2 interfaces, so 2 IPs. Which IP you see along the
trace depends on the direction your trace is taking.
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
stop. The modem was on, I was monitoring it with /interface wireless monitor 0,
and the "last-ip" field never changed (as it usually does on
an attempted access).
Can you show your modem's routing table and firewall here? (/ip
route export; /ip firewall export)
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.
That's cool, the bug-finding is appreciated. Although in this
case, I suspect it's on your end.
--Bart
_______________________________________________
PSDR mailing list
PSDR@hamwan.org
http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org