30 May
2017
30 May
'17
8:36 p.m.
Hi Lynwood....I see it now but I get a pile of timeouts once I leave my
router:
don't have a way to do any packet captures right now
leon
C:\>tracert 44.60.44.10
Tracing route to kb3vwg-010.ampr.org [44.60.44.10]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms xtm520.wa4zlw.homedns.org [10.161.51.3]
2 1 ms 1 ms 1 ms core100.wa4zlw.ampr.org [44.56.53.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 19 ms 21 ms 19 ms kb3vwg-010.ampr.org [44.60.44.10]
Trace complete.
C:\>tracert 71.163.244.98
Tracing route to pool-71-163-244-98.washdc.fios.verizon.net [71.163.244.98]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xtm520.wa4zlw.homedns.org [10.161.51.3]
2 * * * Request timed out.
3 8 ms 24 ms 8 ms gateway-t2-1-flt3blocal1.flt.ptd.net
[207.44.126.57]
4 16 ms 16 ms 21 ms
te0-11-0-6.ccr41.iad02.atlas.cogentco.com [38.122.63.197]
5 16 ms 16 ms 15 ms verizon.iad02.atlas.cogentco.com
[154.54.10.198]
6 * * * Request timed out.
7 18 ms 20 ms 24 ms ae204-0.WASHDC-VFTTP-352.verizon-gni.net
[100.41.220.79]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 19 ms 25 ms 19 ms
pool-71-163-244-98.washdc.fios.verizon.net [71.163.244.98]
Trace complete.
C:\>
On 5/30/2017 4:26 PM, lleachii--- via 44Net wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Tom and Leon,
Thanks. I just allowed all Echo Request for now (usually I only allow
the GW Public IPs in Encap.txt).
It appears I'm still reachable, as I see your requests.
If anyone can look at the packets, can you confirm they are marked:
0xB8 (Extended Forwarding), 0xBA (EF with least cost) or 0x00 (Normal).
---
This email has been checked for viruses by AVG.
http://www.avg.com