Could well be.  8^D - you never really know.

From what I have read, it would seem that with DFS-FCC (instead of DFS-UNSET, electromagnetic spectrum interference is prevented by avoiding same channel operation with other pre-WiFi equipment such as comm satellites, weather radar, etc.

But the best of it all is that 95% to 100% figure that brings a grin to my face.

Best,

A.

Update:
For whatever reason, my WiCD applet now shows me a full green scale and hovering over it I get this:

This is almost all the time the link is up.
Used to be ~ 15% to 20% less than that.

Of course, I am quite aware that there are many factors at play with WiFi reception, but maybe country AR: DFS-FCC instead of country 00: DFS-UNSET actually made a difference?

Best,

A.

Indeed ...
I had to jump through a lot of hoops with my first time experiments in WiFi almos 10 years ago.
In this case, I am only a guest with no access to the router so settings are not available to me.

As for the Regulatory domain, dmesg bitches about not being to load a regulatory.db.

~$ sudo dmesg | grep regulatory
[   23.720125] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   23.772719] platform regulatory.0: firmware: failed to load regulatory.db (-2)
[   23.798235] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   23.810883] cfg80211: failed to load regulatory.db
~$ 

and

[   24.988242] ath: EEPROM regdomain: 0x809c
[   24.988243] ath: EEPROM indicates we should expect a country code
[   24.988245] ath: doing EEPROM country->regdmn map search
[   24.988246] ath: country maps to regdmn code: 0x52
[   24.988248] ath: Country alpha2 being used: CN
[   24.988249] ath: Regpair used: 0x52

Which is probably what is happening here:

~$ sudo iw reg get
global
country 00: DFS-UNSET
	(2402 - 2472 @ 40), (6, 20), (N/A)
	(2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
	(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
	(5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
	(5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
	(5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
	(5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN
	(57240 - 63720 @ 2160), (N/A, 0), (N/A)
~$ 

Maybe I am getting good reception because it is set to 00 although I doubt it.

Just to try, I have set it to my own country code and now get this;

~$ sudo iw reg get
global
country AR: DFS-FCC
	(2402 - 2482 @ 40), (N/A, 20), (N/A)
	(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
~$ 

I'll give it a run and see if it sticks and if it does, then what goes on.
If it does not work as before, then I will set it back to 00.

Thanks for your input.

Best,

A.

Properly pointed, I am getting no less than 94% signal and download speeds of 13.5 Mbps on a day when not every TD&H is on the cable.

https://en.wikipedia.org/wiki/IEEE_802. … Data_rates

Setting up WiFi is a separate big topic.
You can optimize by choosing a channel, its width, etc. depending on local conditions.

Quote from the article. If you need a browser translator-
https://github.com/FilipePS/Traduzir-paginas-web

https://habr.com/ru/articles/317220/

Regards.

Good to know, thanks.

That said, I am quite surprised with the performance of my home made tin-can waveguide antenna.
Properly pointed, I am getting no less than 94% signal and download speeds of 13.5 Mbps on a day when not every TD&H is on the cable.
That's roughly 8 / 9 mts. as the crow flies with a couple of 13cm. walls in between.

Fibre should be much better.

Thanks a lot for your input.

Best,

A.

I suspect your traffic may be routed through two or more paths, one via a system that generates timout responses and one or more that don't. So it's a matter of chance whether you get a response.

But it's not a worry because your traffic is always passed on to later sites.

Yes, seem to be less.
There is also another host.

192.168.0.1                                0.0%
???                                      100.0% 
???                                      100.0%
???                                      100.0%
???                                      100.0%
host39.181-89-51.telecom.net.ar           68.0%    # % for 450 packets / 63.1% for 700 
host246.181-13-127.telecom.net.ar          0.0%
172.67.41.55                               0.0%

Best,

A.

Regards.

In this case it does not.
Obscured puposely or crap infrastructure?

~$ traceroute dev1galaxy.org
traceroute to dev1galaxy.org (136.243.229.210), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  37.305 ms  37.240 ms  37.220 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  ae25.baires1.bai.seabone.net (195.22.220.56)  23.835 ms  26.231 ms  19.157 ms
--- snip ---

That did it.
But it does not get done consistently, if repeat the command you get * * *.

~$ traceroute -n dev1galaxy.org
traceroute to dev1galaxy.org (136.243.229.210), 30 hops max, 60 byte packets
 1  192.168.0.1  10.734 ms  10.703 ms  10.675 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  181.89.51.39  120.594 ms * *                            # this should be host39.181-89-51.telecom.net.ar    
 7  195.22.220.56  110.130 ms  31.578 ms  31.562 ms
 8  * * 195.22.211.209  261.653 ms
 9  213.144.184.91  261.631 ms * *
10  213.239.224.109  276.959 ms 213.239.224.181  312.183 ms 213.239.224.77  312.162 ms
11  213.239.245.110  312.146 ms 213.239.245.150  324.733 ms  324.724 ms
12  5.9.97.46  324.693 ms  324.649 ms  324.623 ms
13  136.243.229.210  324.607 ms  238.097 ms  279.641 ms

No, it does not have that feature.

No matter.
We beat the system and found the IP.  8^D

~$ ping 181.89.51.39
PING 181.89.51.39 (181.89.51.39) 56(84) bytes of data.
64 bytes from 181.89.51.39: icmp_seq=1 ttl=250 time=30.6 ms
64 bytes from 181.89.51.39: icmp_seq=2 ttl=250 time=100 ms
64 bytes from 181.89.51.39: icmp_seq=3 ttl=250 time=43.3 ms
64 bytes from 181.89.51.39: icmp_seq=4 ttl=250 time=36.4 ms
^C
--- 181.89.51.39 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 7ms
rtt min/avg/max/mdev = 30.553/52.647/100.380/27.925 ms
~$ 

~$ nslookup 181.89.51.39
39.51.89.181.in-addr.arpa	name = host39.181-89-51.telecom.net.ar.

Authoritative answers can be found from:
~$ 

Nice to learn something new every so often.

Thanks for your input.

Best,

A.

And mtr might have an option to show the IP addresses (try hovering over the name or clicking on it).

Yes, that is what it does, always with a 90% to 100% packet loss. 

I tried that but it needs the IP.

Unfortunately not.

~$ host host39.181-89-51.telecom.net.ar
Host host39.181-89-51.telecom.net.ar not found: 3(NXDOMAIN)
~$

It was just curiosity.  8^°

Thank you very much for your input.

Best,

A.

If you are really interested you could ping it and see how often it replies. But it's probably won't get you anywhere unless you ask the telco that owns it, who probably won't be interested because it's passing packets on OK.

host host39.181-89-51.telecom.net.ar should tell you it's IP address. But again that isn't likely to tell you anything useful.

I just noticed something.

Just out of curiosity ...
What about the node that does not have have ??? for its IP address?
ie:

Hostname                                   Loss  
host39.181-89-51.telecom.net.ar            97.6%

Isn't a 97.6% loss rather high?
Is it possible to improve that metric?

I take it that it is between the wireless router and host39.181-89-51.telecom.net.ar, right?
My DIY tin-can waveguide antenna affords me (given the distance/walls to the router) a nice strong ~80% signal most of the time.

Thanks in advance.

Best,

A.