Unknown how long this has been going on...
When doing a traceroute from my hAP to Winlink.org, it's almost instant, no RF. When doing it from one of my dtd nodes, the link goes out RF, then thru a couple of nodes on our network, finally going to a local node offering internet access. Time about 10 seconds.
I've looked at my settings on both my hAP and this dtd node, they appear correct. I even sent screen shots to Ms. Gemini, and she said they look correct. (She also suggested contacting the node with the open internet access and have them shut it down. duh)
Disregarding the obvious...
The dtd cost from the hAP to my RF node is 96, both direction. The cost from my RF node to the first RF node it's going to, is 256. Why would Babel even consider the RF node when the cost is 96 vs 256?
Before I grab a couple of beers and attempt to understand Github procedures for posting, any suggestions?
Richard ko0ooo
When doing a traceroute from my hAP to Winlink.org, it's almost instant, no RF. When doing it from one of my dtd nodes, the link goes out RF, then thru a couple of nodes on our network, finally going to a local node offering internet access. Time about 10 seconds.
I've looked at my settings on both my hAP and this dtd node, they appear correct. I even sent screen shots to Ms. Gemini, and she said they look correct. (She also suggested contacting the node with the open internet access and have them shut it down. duh)
Disregarding the obvious...
The dtd cost from the hAP to my RF node is 96, both direction. The cost from my RF node to the first RF node it's going to, is 256. Why would Babel even consider the RF node when the cost is 96 vs 256?
Before I grab a couple of beers and attempt to understand Github procedures for posting, any suggestions?
Richard ko0ooo
Production release 4.26.10.0 is now available. Give it a shot.
Orv W6BI