Using two paths to get to a destination. I can switch between the two paths.
I was planning on having path redundancy if one should fail.
Don't understand why Path 1 failed.
Path 1: Microwave link to PleasantsPk (AE6XE)
Path 2: Tunnel over internet to KM6ZPO-HAP-LITE
Path 1
Can't find a path to w6bhz-aprs-pi.
C:\Users\acct>tracert w6bhz-aprs-pi
Tracing route to w6bhz-aprs-pi.local.mesh [10.227.6.30]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms localnode.local.mesh [10.151.227.153]
2 1 ms <1 ms <1 ms dtdlink.KN6RVU-DISH3.local.mesh [10.15.32.221]
3 2 ms 2 ms 2 ms AE6XE-PleasantsPk-RM3.local.mesh [10.14.32.134]
4 3 ms 10 ms 4 ms dtdlink.W6JPL-RM3-PleasantsPk-p2p-JPL.local.mesh [10.133.78.235]
5 5 ms 9 ms 27 ms KC6RKG-NG3-SE5-SM33-RKG2PP.local.mesh [10.8.221.154]
6 34 ms 5 ms 12 ms dtdlink.WM3SH-RKM5S-S120-SM12-AM5G19.local.mesh [10.101.23.246]
7 21 ms 24 ms 138 ms K6KBM-HARPUSA-LHG-5.local.mesh [10.39.188.122]
8 29 ms 7 ms 6 ms dtdlink.K6KBM-HARPUSA-HAP-AC.local.mesh [10.251.243.20]
9 34 ms 55 ms 59 ms mid1.K6IRF-HARPUSA-HAP-AC [172.31.117.74]
10 52 ms 77 ms 62 ms mid1.K6KKK-HARPUSA-HAP-AC [172.31.117.105]
11 60 ms 53 ms 45 ms dtdlink.K6KKK-HARPUSA-LHG-5.local.mesh [10.121.208.156]
12 58 ms 42 ms 51 ms K6PVR-LA-Verdugo-W-Sector-5G.local.mesh [10.60.139.108]
13 78 ms 55 ms 53 ms dtdlink.K6PVR-LA-Verdugo-S-Sector-5G.local.mesh [10.163.170.94]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Path 2
Found path to w6bhz-aprs-pi.
C:\Users\acct>tracert w6bhz-aprs-pi
Tracing route to w6bhz-aprs-pi.local.mesh [10.227.6.30]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms localnode.local.mesh [10.151.227.153]
2 44 ms 30 ms 30 ms mid1.KM6ZPO-HAP-LITE [172.31.236.230]
3 476 ms 974 ms 466 ms mid9.K6PVR-VC-TUNNEL-SRV [172.31.146.122]
4 821 ms 502 ms 196 ms mid4.K7AZ-GravelPeak-hAP [172.31.146.161]
5 94 ms 90 ms 91 ms dtdlink.K7AZ-PTP-GP-TO-CUESTA.local.mesh [10.237.120.242]
6 211 ms 261 ms 152 ms N6CP-CuestaPeak-SLO-5G.local.mesh [10.74.209.242]
7 152 ms 109 ms 160 ms dtdlink.N6CP-Cuesta-to-Clark-P2P-Only.local.mesh [10.242.175.13]
8 172 ms 196 ms 196 ms N6CP-Clark-to-Cuesta-P2P-Only.local.mesh [10.241.175.1]
9 198 ms 139 ms 204 ms dtdlink.W6BHZ-ClarkValley-HAP.local.mesh [10.95.48.97]
10 205 ms 176 ms 316 ms w6bhz-aprs-pi.local.mesh [10.227.6.30]
Trace complete.
I was planning on having path redundancy if one should fail.
Don't understand why Path 1 failed.
Path 1: Microwave link to PleasantsPk (AE6XE)
Path 2: Tunnel over internet to KM6ZPO-HAP-LITE
Path 1
Can't find a path to w6bhz-aprs-pi.
C:\Users\acct>tracert w6bhz-aprs-pi
Tracing route to w6bhz-aprs-pi.local.mesh [10.227.6.30]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms localnode.local.mesh [10.151.227.153]
2 1 ms <1 ms <1 ms dtdlink.KN6RVU-DISH3.local.mesh [10.15.32.221]
3 2 ms 2 ms 2 ms AE6XE-PleasantsPk-RM3.local.mesh [10.14.32.134]
4 3 ms 10 ms 4 ms dtdlink.W6JPL-RM3-PleasantsPk-p2p-JPL.local.mesh [10.133.78.235]
5 5 ms 9 ms 27 ms KC6RKG-NG3-SE5-SM33-RKG2PP.local.mesh [10.8.221.154]
6 34 ms 5 ms 12 ms dtdlink.WM3SH-RKM5S-S120-SM12-AM5G19.local.mesh [10.101.23.246]
7 21 ms 24 ms 138 ms K6KBM-HARPUSA-LHG-5.local.mesh [10.39.188.122]
8 29 ms 7 ms 6 ms dtdlink.K6KBM-HARPUSA-HAP-AC.local.mesh [10.251.243.20]
9 34 ms 55 ms 59 ms mid1.K6IRF-HARPUSA-HAP-AC [172.31.117.74]
10 52 ms 77 ms 62 ms mid1.K6KKK-HARPUSA-HAP-AC [172.31.117.105]
11 60 ms 53 ms 45 ms dtdlink.K6KKK-HARPUSA-LHG-5.local.mesh [10.121.208.156]
12 58 ms 42 ms 51 ms K6PVR-LA-Verdugo-W-Sector-5G.local.mesh [10.60.139.108]
13 78 ms 55 ms 53 ms dtdlink.K6PVR-LA-Verdugo-S-Sector-5G.local.mesh [10.163.170.94]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Path 2
Found path to w6bhz-aprs-pi.
C:\Users\acct>tracert w6bhz-aprs-pi
Tracing route to w6bhz-aprs-pi.local.mesh [10.227.6.30]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms localnode.local.mesh [10.151.227.153]
2 44 ms 30 ms 30 ms mid1.KM6ZPO-HAP-LITE [172.31.236.230]
3 476 ms 974 ms 466 ms mid9.K6PVR-VC-TUNNEL-SRV [172.31.146.122]
4 821 ms 502 ms 196 ms mid4.K7AZ-GravelPeak-hAP [172.31.146.161]
5 94 ms 90 ms 91 ms dtdlink.K7AZ-PTP-GP-TO-CUESTA.local.mesh [10.237.120.242]
6 211 ms 261 ms 152 ms N6CP-CuestaPeak-SLO-5G.local.mesh [10.74.209.242]
7 152 ms 109 ms 160 ms dtdlink.N6CP-Cuesta-to-Clark-P2P-Only.local.mesh [10.242.175.13]
8 172 ms 196 ms 196 ms N6CP-Clark-to-Cuesta-P2P-Only.local.mesh [10.241.175.1]
9 198 ms 139 ms 204 ms dtdlink.W6BHZ-ClarkValley-HAP.local.mesh [10.95.48.97]
10 205 ms 176 ms 316 ms w6bhz-aprs-pi.local.mesh [10.227.6.30]
Trace complete.
Your node did have a path toward w6bhz-aprs-pi in both tests.
Path 1 fails at dtdlink.K6PVR-LA-Verdugo-S-Sector-5G.local.mesh [10.163.170.94]
Path 2 succeeds.
"Don't understand why Path 1 failed."
Ask K6PVR.
73, Chuck