All,
I've been doing some testing with the Type of Service and Differentiated Services Code Point for tunl0. I've been working to determine if connectivity to Ronen's camera's could be slightly improved from the tunnel's perspective. I'm focusing on the improvements seen using hex code 0xB8, known as High Priority Expedited Forwarding, or 'Virtual Leased Line.'
I wanted you all to check your connections to me, and make sure that I'm still reachable. Feel free to ping, or simply use my tool at http://44.60.44.10/tools/trace/php-trace44.php/ to reach yourselves.
73,
- Lynwood KB3VWG
ip tunnel change tunl0 mode ipip ttl 64 tos B8 pmtudisc
Lynwood.
I _CAN NOT_ ping 44.60.44.10 from Internet. I can ping 44.60.44.10 from 44net aware systems.
I can access http://44.60.44.10 from Internet and from 44net aware systems.
No traceroute data from my subnet 44.165.2/25.
Best regards. --- Tom - SP2L
Sent from Xperia Z1 with AquaMail http://www.aqua-mail.com
I can ping 44.60.44.10 and http to it but I can not traceroute to it (icmp not udp)
from 44.56.53.3
leon
On 5/30/2017 4:07 PM, SP2L Tom wrote:
(Please trim inclusions from previous messages) _______________________________________________ Lynwood.
I _CAN NOT_ ping 44.60.44.10 from Internet. I can ping 44.60.44.10 from 44net aware systems.
I can access http://44.60.44.10 from Internet and from 44net aware systems.
No traceroute data from my subnet 44.165.2/25.
Best regards.
Tom - SP2L
Sent from Xperia Z1 with AquaMail http://www.aqua-mail.com
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
--- This email has been checked for viruses by AVG. http://www.avg.com
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).
Thanks and 73,
- Lynwood KB3VWG
root@router:~# ip tunnel list tunl0: ip/ip remote any local any ttl 64 tos 0xba
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
Lynwood.
Still _CAN NOT_ ping from Internet. Present IP address of my smartphone is 31.0.68.60
Best regards. --- Tom - SP2L
Sent from Xperia Z1 with AquaMail http://www.aqua-mail.com
much better:
C:>tracert 44.60.44.10
Tracing route to kb3vwg-010.ampr.org [44.60.44.10] over a maximum of 30 hops:
1 <1 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 19 ms 18 ms 19 ms kb3vwg-001.ampr.org [44.60.44.1] 4 19 ms 18 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 9 ms 8 ms 8 ms gateway-t2-1-flt3blocal1.flt.ptd.net [207.44.126.57] 4 19 ms 16 ms 17 ms te0-11-0-6.ccr41.iad02.atlas.cogentco.com [38.122.63.197] 5 16 ms 16 ms 16 ms verizon.iad02.atlas.cogentco.com [154.54.10.198] 6 * * * Request timed out. 7 18 ms 18 ms 20 ms ae204-0.WASHDC-VFTTP-352.verizon-gni.net [100.41.220.79] 8 18 ms 18 ms 21 ms pool-71-163-244-98.washdc.fios.verizon.net [71.163.244.98]
Trace complete.
C:>
On 5/30/2017 4:47 PM, lleachii--- via 44Net wrote:
(Please trim inclusions from previous messages) _______________________________________________ Ok, traceroute should work (except for 1 hop controlled by my Carrier).
--- This email has been checked for viruses by AVG. http://www.avg.com
-
Leon Zetekoff -
lleachii＠aol.com -
SP2L Tom