I am a victim of a relentless man in the middle situation. I am sorry for the dramatic terminology but I think it describes my situation. I value any help in figuring out how to secure at least equipment that runs Fedora.
I am experiencing this in all computing equipment and smart phones. I have been trying to figure out a solution with the lap top that was my main device, and although I have been experimenting with Fedora, I am still subject to somebody monitoring all of my online activities. I will provide the evidence I have been able to gather as I describe some of the symptoms.
I have only access to the wireless connection of an Android Phone. The phone is a little over a year old, and I bought it directly from Google thinking that their Pixel line would be the most secure phone; I stand corrected. I mention this to highlight that I have absolutely no access to a wired connection.
My problems began more than a year ago, but I will jump to the current state of affairs which has to do with Fedora.
I’ve installed various versions of Fedora into an HP Envy 17. But no matter what version or OS, before it was Ubuntu, I continue to experience online surveillance and odd behavior from the OS. I’ve also experimented with VPN services and a variety of clients, and this only creates more problems (connectivity issues. I won’t be able to load webpages et all, constantly get ERR_TIME_OUT, and other problems).
Right now, I am using a live media DVD Fedora 31.1 I am using no VPN, just hte HotSpot from the Android and when I visit the website ipleak.net this is what I see:
But when I visit ipleak.net with my phone, I get: https://i.ibb.co/L05hZ42/Screenshot-20200726-030356.jpg
[liveuser@localhost-live ~]$ sudo traceroute ipleak.net
traceroute to ipleak.net (18.104.22.168), 30 hops max, 60 byte packets 1 _gateway (192.168.43.177) 5.491 ms 5.441 ms 5.452 ms 2 13.sub-66-174-19.myvzw.com (22.214.171.124) 36.995 ms 48.767 ms 48.483 ms 3 * * * 4 * * * 5 99.sub-69-83-15.myvzw.com (126.96.36.199) 53.752 ms 53.498 ms 53.827 ms 6 * * * 7 134.sub-69-83-3.myvzw.com (188.8.131.52) 40.603 ms 57.762 ms 57.954 ms 8 131.sub-66-174-18.myvzw.com (184.108.40.206) 52.078 ms 52.372 ms 51.902 ms 9 et-1-0-2.GW2.BOS30.ALTER.NET (220.127.116.11) 57.808 ms 34.821 ms 34.857 ms 10 0.ae2.BR2.NYC4.ALTER.NET (18.104.22.168) 55.350 ms 55.690 ms 56.364 ms 11 verizon.com.customer.alter.net (22.214.171.124) 56.283 ms 56.074 ms 45.331 ms 12 if-ae-18-49.tcore2.l78-london.as6453.net (126.96.36.199) 116.862 ms if-ae-2-39.tcore2.l78-london.as6453.net (188.8.131.52) 129.326 ms if-ae-32-2.tcore2.ldn-london.as6453.net (184.108.40.206) 135.382 ms 13 * if-ae-15-2.tcore2.l78-london.as6453.net (220.127.116.11) 117.429 ms * 14 if-ae-11-2.tcore1.ad1-amsterdam.as6453.net (18.104.22.168) 122.665 ms 148.140 ms 120.303 ms 15 if-ae-11-2.tcore1.ad1-amsterdam.as6453.net (22.214.171.124) 107.230 ms 126.96.36.199 (188.8.131.52) 125.218 ms 184.108.40.206 (220.127.116.11) 131.526 ms 16 18.104.22.168 (22.214.171.124) 120.006 ms 126.96.36.199 (188.8.131.52) 122.939 ms 184.108.40.206 (220.127.116.11) 128.545 ms 17 * 18.104.22.168 (22.214.171.124) 118.312 ms 112.865 ms 18 * 126.96.36.199 (188.8.131.52) 125.370 ms 125.373 ms
[liveuser@localhost-live ~]$ sudo tracepath ipleak.net
1?: [LOCALHOST] pmtu 1500 1: _gateway 2.800ms 1: _gateway 2.162ms 2: _gateway 3.356ms pmtu 1428 2: 13.sub-66-174-19.myvzw.com 59.467ms 3: no reply 4: no reply 5: 99.sub-69-83-15.myvzw.com 74.929ms 6: no reply 7: 134.sub-69-83-3.myvzw.com 63.192ms 8: 131.sub-66-174-18.myvzw.com 54.733ms asymm 9 9: et-1-0-2.GW2.BOS30.ALTER.NET 61.144ms 10: 0.ae1.BR2.NYC4.ALTER.NET 61.607ms asymm 13 11: verizon.com.customer.alter.net 69.617ms asymm 13 12: if-ae-32-2.tcore2.ldn-london.as6453.net 163.484ms asymm 19 13: if-ae-15-2.tcore2.l78-london.as6453.net 137.571ms asymm 19 14: if-ae-11-2.tcore1.ad1-amsterdam.as6453.net 140.483ms asymm 15 15: if-ae-11-2.tcore1.ad1-amsterdam.as6453.net 148.168ms 16: 184.108.40.206 156.270ms 17: 220.127.116.11 169.277ms asymm 16 18: 18.104.22.168 146.089ms asymm 16 19: 22.214.171.124 150.569ms reached Resume: pmtu 1428 hops 19 back 17
Also, I am experiencing connectivity problems, and I lost part of what I had written, so I will continue in parts.
I started nmcli before I connected to the internet. If you scroll down, you’ll notice the intermittent full and limited connectivity
[liveuser@localhost-live ~]$ nmcli monitor
Networkmanager is not running (waiting for it) lo: device created wlo1: device created Networkmanager is now in the 'disconnected' state NetworkManager has started lo: unmanaged Hostname set to 'localhost-live' Connectivity is now 'none' p2p-dev-wlo1: device created p2p-dev-wlo1: unavailable p2p-dev-wlo1: disconnected wlo1: disconnected wlo1: using connection 'CriminalsRWatchingOurWiFis' wlo1: connecting (prepare) Networkmanager is now in the 'connecting' state wlo1: connecting (configuring) wlo1: connecting (need authentication) wlo1: connecting (prepare) wlo1: connecting (configuring) wlo1: connecting (getting IP configuration) wlo1: connecting (checking IP connectivity) wlo1: connecting (starting secondary connections) wlo1: connected Networkmanager is now in the 'connected (local only)' state Networkmanager is now in the 'connected (site only)' state 'CriminalsRWatchingOurWiFis' is now the primary connection Connectivity is now 'limited' Networkmanager is now in the 'connected' state Connectivity is now 'full' Networkmanager is now in the 'connected (site only)' state Connectivity is now 'limited' Networkmanager is now in the 'connected' state Connectivity is now 'full' Networkmanager is now in the 'connected (site only)' state Connectivity is now 'limited' Networkmanager is now in the 'connected' state Connectivity is now 'full' Networkmanager is now in the 'connected (site only)' state Connectivity is now 'limited' Networkmanager is now in the 'connected' state Connectivity is now 'full' Networkmanager is now in the 'connected (site only)' state Connectivity is now 'limited' Networkmanager is now in the 'connected' state Connectivity is now 'full'