Public connection service is overwhelmed by requests or is fraud?

Chiming in:

You're using a free service. You're getting what you're paying for.

I can't add anything more to what TB0ne has said.

I don't know what you expect from this forum, or anyone except the provider of the service, for that matter.

@TBOne
Please do not say what I have to do, go back to the real work you said you are busy with, I have understood what you say

@scasey I cannot start again with you too, Ok I will use google

Originally Posted by P5music @TBOne Please do not say what I have to do, go back to the real work you said you are busy with, I have understood what you say

Great; so why continue to post if you've understood? You have only the choices given:

• Gather data using what's been told to you, or whatever else you can research on your own.
• Offer your expertise to "them" to get things working better
• Pay for something

What are your other choices? Can you name any? And again, what is it you're expecting anyone here, or in any forum, to be able to do for you???

I found a command ("tail -f /var/log/syslog") to have a log (see below).
I hope it has enough information about what it happens at disconnection.
I am no expert at all on this matter, and I need to assess what's going on to understand it and take action, if necessary, in both technical and legal way (I edited the log text to hide some information).
Also note that the final part is about a forced automatic reconnection performed by means of a script I run on the system.
Can you understand what is going on at the disconnection time?
Thank you in advance

Sep 30 12:23:47 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=6e:3b:6b:11:e2:0f reason=4 locally_generated=1
Sep 30 12:23:47 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Sep 30 12:23:47 pc NetworkManager[925]: <warn>  [1569839027.8538] sup-iface[0x557779cdd130,wlp2s0]: connection disconnected (reason -4)
Sep 30 12:23:47 pc NetworkManager[925]: <info>  [1569839027.8595] device (wlp2s0): supplicant interface state: completed -> disconnected
Sep 30 12:23:47 pc NetworkManager[925]: <info>  [1569839027.8596] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> disconnected
Sep 30 12:23:47 pc NetworkManager[925]: <info>  [1569839027.9626] device (wlp2s0): supplicant interface state: disconnected -> scanning
Sep 30 12:23:47 pc NetworkManager[925]: <info>  [1569839027.9627] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.8864] agent-manager: req[0x557779d8b060, :1.211/nmcli-connect/1000]: agent registered
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.8914] device (wlp2s0): disconnecting for new activation request.
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.8914] device (wlp2s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.8920] manager: NetworkManager state is now DISCONNECTING
Sep 30 12:23:48 pc whoopsie[1124]: [12:23:48] offline
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9364] audit: op="connection-activate" uuid="5a7e0c8d-768a-457d-ab38-de8f47b4489a" name="Service1 Wireless" pid=1088 uid=1000 result="success"
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9369] device (wlp2s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Sep 30 12:23:48 pc avahi-daemon[910]: Withdrawing address record for fe80::508f:6678:fa2c:797 on wlp2s0.
Sep 30 12:23:48 pc avahi-daemon[910]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::508f:6678:fa2c:797.
Sep 30 12:23:48 pc avahi-daemon[910]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
Sep 30 12:23:48 pc whoopsie[1124]: [12:23:48] Cannot reach: https://daisy.ubuntu.com
Sep 30 12:23:48 pc dbus-daemon[923]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.18' (uid=0 pid=925 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Sep 30 12:23:48 pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 30 12:23:48 pc dbus-daemon[923]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 30 12:23:48 pc systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 30 12:23:48 pc nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
Sep 30 12:23:48 pc nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9713] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 31934
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9713] dhcp4 (wlp2s0): state changed bound -> done
Sep 30 12:23:48 pc avahi-daemon[910]: Withdrawing address record for xx.xx.xx.xx on wlp2s0.
Sep 30 12:23:48 pc avahi-daemon[910]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address xx.xx.xx.xx.
Sep 30 12:23:48 pc avahi-daemon[910]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9770] manager: NetworkManager state is now DISCONNECTED
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9781] device (wlp2s0): Activation: starting connection 'Service1 Wireless' (5a7e0c8d-768a-457d-ab38-de8f47b4489a)
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9804] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9810] manager: NetworkManager state is now CONNECTING
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9822] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9827] device (wlp2s0): Activation: (wifi) connection 'Service1 Wireless' requires no security.  No secrets needed.
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9827] Config: added 'ssid' value 'Service1 Wireless'
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9828] Config: added 'scan_ssid' value '1'
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9828] Config: added 'bgscan' value 'simple:30:-80:86400'
Sep 30 12:23:48 pc NetworkManager[925]: <info>  [1569839028.9828] Config: added 'key_mgmt' value 'NONE'
Sep 30 12:23:48 pc wpa_supplicant[926]: wlp2s0: Reject scan trigger since one is already pending
Sep 30 12:23:48 pc nm-dispatcher: req:2 'down' [wlp2s0]: new request (1 scripts)
Sep 30 12:23:48 pc nm-dispatcher: req:2 'down' [wlp2s0]: start running ordered scripts...
Sep 30 12:23:49 pc kernel: [ 1312.676708] wlp2s0: authenticate with 6c:3b:6b:11:e2:0f
Sep 30 12:23:49 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz)
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.0127] device (wlp2s0): supplicant interface state: scanning -> disconnected
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.0128] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> disconnected
Sep 30 12:23:49 pc kernel: [ 1312.695003] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 1/3)
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.0329] device (wlp2s0): supplicant interface state: disconnected -> authenticating
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.0330] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> authenticating
Sep 30 12:23:49 pc kernel: [ 1312.743949] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 2/3)
Sep 30 12:23:49 pc kernel: [ 1312.883271] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 3/3)
Sep 30 12:23:49 pc wpa_supplicant[926]: wlp2s0: Trying to associate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz)
Sep 30 12:23:49 pc kernel: [ 1312.963267] wlp2s0: authenticated
Sep 30 12:23:49 pc kernel: [ 1312.967305] wlp2s0: associate with 6c:3b:6b:11:e2:0f (try 1/3)
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.3033] device (wlp2s0): supplicant interface state: authenticating -> associating
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.3033] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Sep 30 12:23:49 pc kernel: [ 1313.075883] wlp2s0: associate with 6c:3b:6b:11:e2:0f (try 2/3)
Sep 30 12:23:49 pc kernel: [ 1313.199276] wlp2s0: associate with 6c:3b:6b:11:e2:0f (try 3/3)
Sep 30 12:23:49 pc kernel: [ 1313.331284] wlp2s0: association with 6c:3b:6b:11:e2:0f timed out
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.6991] device (wlp2s0): supplicant interface state: associating -> disconnected
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.6992] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> disconnected
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.8018] device (wlp2s0): supplicant interface state: disconnected -> scanning
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.8018] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Sep 30 12:23:49 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with cc:2d:e0:c3:8c:77 (SSID='Service1 Wireless' freq=2427 MHz)
Sep 30 12:23:49 pc kernel: [ 1313.496474] wlp2s0: authenticate with cc:2d:e0:c3:8c:77
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.8458] device (wlp2s0): supplicant interface state: scanning -> authenticating
Sep 30 12:23:49 pc NetworkManager[925]: <info>  [1569839029.8458] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
Sep 30 12:23:49 pc kernel: [ 1313.511288] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 1/3)
Sep 30 12:23:50 pc kernel: [ 1313.675376] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 2/3)
Sep 30 12:23:50 pc kernel: [ 1313.779353] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 3/3)
Sep 30 12:23:50 pc kernel: [ 1313.891346] wlp2s0: authentication with cc:2d:e0:c3:8c:77 timed out
Sep 30 12:23:50 pc NetworkManager[925]: <info>  [1569839030.2672] device (wlp2s0): supplicant interface state: authenticating -> disconnected
Sep 30 12:23:50 pc NetworkManager[925]: <info>  [1569839030.2673] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected
Sep 30 12:23:50 pc NetworkManager[925]: <info>  [1569839030.3700] device (wlp2s0): supplicant interface state: disconnected -> scanning
Sep 30 12:23:50 pc NetworkManager[925]: <info>  [1569839030.3701] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Sep 30 12:23:51 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz)
Sep 30 12:23:51 pc kernel: [ 1315.097127] wlp2s0: authenticate with 6c:3b:6b:11:e2:0f
Sep 30 12:23:51 pc kernel: [ 1315.117728] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 1/3)
Sep 30 12:23:51 pc NetworkManager[925]: <info>  [1569839031.4522] device (wlp2s0): supplicant interface state: scanning -> authenticating
Sep 30 12:23:51 pc NetworkManager[925]: <info>  [1569839031.4523] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
Sep 30 12:23:51 pc kernel: [ 1315.223459] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 2/3)
Sep 30 12:23:51 pc kernel: [ 1315.327470] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 3/3)
Sep 30 12:23:51 pc kernel: [ 1315.459514] wlp2s0: authentication with 6c:3b:6b:11:e2:0f timed out
Sep 30 12:23:51 pc NetworkManager[925]: <info>  [1569839031.8348] device (wlp2s0): supplicant interface state: authenticating -> disconnected
Sep 30 12:23:51 pc NetworkManager[925]: <info>  [1569839031.8350] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected
Sep 30 12:23:52 pc NetworkManager[925]: <info>  [1569839032.8399] device (wlp2s0): supplicant interface state: disconnected -> scanning
Sep 30 12:23:52 pc NetworkManager[925]: <info>  [1569839032.8400] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Sep 30 12:23:52 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with cc:2d:e0:c3:8c:77 (SSID='Service1 Wireless' freq=2427 MHz)
Sep 30 12:23:52 pc kernel: [ 1316.540843] wlp2s0: authenticate with cc:2d:e0:c3:8c:77
Sep 30 12:23:52 pc NetworkManager[925]: <info>  [1569839032.8901] device (wlp2s0): supplicant interface state: scanning -> authenticating
Sep 30 12:23:52 pc NetworkManager[925]: <info>  [1569839032.8902] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
Sep 30 12:23:52 pc kernel: [ 1316.555889] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 1/3)
Sep 30 12:23:52 pc kernel: [ 1316.659623] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 2/3)
Sep 30 12:23:53 pc kernel: [ 1316.763618] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 3/3)
Sep 30 12:23:53 pc kernel: [ 1316.867605] wlp2s0: authentication with cc:2d:e0:c3:8c:77 timed out
Sep 30 12:23:53 pc NetworkManager[925]: <info>  [1569839033.2511] device (wlp2s0): supplicant interface state: authenticating -> disconnected
Sep 30 12:23:53 pc NetworkManager[925]: <info>  [1569839033.2511] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected
Sep 30 12:23:54 pc NetworkManager[925]: <info>  [1569839034.2566] device (wlp2s0): supplicant interface state: disconnected -> scanning
Sep 30 12:23:54 pc NetworkManager[925]: <info>  [1569839034.2567] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with 6c:3b:6b:11:ff:6f (SSID='Service1 Wireless' freq=2442 MHz)
Sep 30 12:23:55 pc kernel: [ 1318.977894] wlp2s0: authenticate with 6c:3b:6b:11:ff:6f
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3318] device (wlp2s0): supplicant interface state: scanning -> authenticating
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3319] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
Sep 30 12:23:55 pc kernel: [ 1318.997409] wlp2s0: send auth to 6c:3b:6b:11:ff:6f (try 1/3)
Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: Trying to associate with 6c:3b:6b:11:ff:6f (SSID='Service1 Wireless' freq=2442 MHz)
Sep 30 12:23:55 pc kernel: [ 1319.001221] wlp2s0: authenticated
Sep 30 12:23:55 pc kernel: [ 1319.005196] wlp2s0: associate with 6c:3b:6b:11:ff:6f (try 1/3)
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3416] device (wlp2s0): supplicant interface state: authenticating -> associating
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3420] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: Associated with 6c:3b:6b:11:ff:6f
Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:11:ff:6f completed [id=0 id_str=]
Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 30 12:23:55 pc kernel: [ 1319.030029] wlp2s0: RX AssocResp from 6c:3b:6b:11:ff:6f (capab=0x421 status=0 aid=2)
Sep 30 12:23:55 pc kernel: [ 1319.030159] wlp2s0: associated
Sep 30 12:23:55 pc kernel: [ 1319.030767] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3699] device (wlp2s0): supplicant interface state: associating -> completed
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3699] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Service1 Wireless"
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3700] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> completed
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3711] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3719] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Sep 30 12:23:55 pc NetworkManager[925]: <info>  [1569839035.3771] dhcp4 (wlp2s0): dhclient started with pid 1146
Sep 30 12:23:55 pc avahi-daemon[910]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::8bbb:81c7:991:352a.
Sep 30 12:23:55 pc avahi-daemon[910]: New relevant interface wlp2s0.IPv6 for mDNS.
Sep 30 12:23:55 pc avahi-daemon[910]: Registering new address record for fe80::8bbb:81c7:991:352a on wlp2s0.*.
Sep 30 12:23:55 pc dhclient[1146]: DHCPREQUEST for xx.xx.xx.xx on wlp2s0 to 255.255.255.255 port 67 (xid=0x53b98d71)
Sep 30 12:23:57 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-80 noise=-91 txrate=11000
Sep 30 12:23:59 pc dhclient[1146]: DHCPREQUEST for xx.xx.xx.xx on wlp2s0 to 255.255.255.255 port 67 (xid=0x53b98d71)
Sep 30 12:23:59 pc systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Sep 30 12:24:03 pc dhclient[1146]: DHCPREQUEST for xx.xx.xx.xx on wlp2s0 to 255.255.255.255 port 67 (xid=0x53b98d71)
Sep 30 12:24:09 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-82 noise=-91 txrate=6500
Sep 30 12:24:09 pc dhclient[1146]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x8f7a555e)
Sep 30 12:24:12 pc kernel: [ 1335.766779] Bluetooth: hci0: corrupted ACL packet
Sep 30 12:24:12 pc dhclient[1146]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 8 (xid=0x8f7a555e)
Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz)
Sep 30 12:24:17 pc kernel: [ 1340.875693] wlp2s0: disconnect from AP 6c:3b:6b:11:ff:6f for new auth to 6c:3b:6b:11:e2:0f
Sep 30 12:24:17 pc kernel: [ 1340.888611] wlp2s0: authenticate with 6c:3b:6b:11:e2:0f
Sep 30 12:24:17 pc kernel: [ 1340.902962] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 1/3)
Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Sep 30 12:24:17 pc NetworkManager[925]: <info>  [1569839057.2359] device (wlp2s0): supplicant interface state: completed -> authenticating
Sep 30 12:24:17 pc NetworkManager[925]: <info>  [1569839057.2359] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> authenticating
Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: Trying to associate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz)
Sep 30 12:24:17 pc kernel: [ 1340.949268] wlp2s0: authenticated
Sep 30 12:24:17 pc kernel: [ 1340.949760] wlp2s0: associate with 6c:3b:6b:11:e2:0f (try 1/3)
Sep 30 12:24:17 pc NetworkManager[925]: <info>  [1569839057.2871] device (wlp2s0): supplicant interface state: authenticating -> associating
Sep 30 12:24:17 pc NetworkManager[925]: <info>  [1569839057.2872] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Sep 30 12:24:17 pc kernel: [ 1340.969644] wlp2s0: RX ReassocResp from 6c:3b:6b:11:e2:0f (capab=0x421 status=0 aid=5)
Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: Associated with 6c:3b:6b:11:e2:0f
Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:11:e2:0f completed [id=0 id_str=]
Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 30 12:24:17 pc kernel: [ 1340.969896] wlp2s0: associated
Sep 30 12:24:17 pc NetworkManager[925]: <info>  [1569839057.3121] device (wlp2s0): supplicant interface state: associating -> completed
Sep 30 12:24:17 pc NetworkManager[925]: <info>  [1569839057.3122] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> completed
Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-51 noise=-90 txrate=6500
Sep 30 12:24:20 pc dhclient[1146]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 19 (xid=0x8f7a555e)
Sep 30 12:24:21 pc dhclient[1146]: DHCPOFFER of xx.xx.xx.xx from zz.zz.zz.zz
Sep 30 12:24:21 pc dhclient[1146]: DHCPREQUEST for xx.xx.xx.xx on wlp2s0 to 255.255.255.255 port 67 (xid=0x5e557a8f)
Sep 30 12:24:21 pc dhclient[1146]: DHCPACK of xx.xx.xx.xx from zz.zz.zz.zz (xid=0x8f7a555e)
Sep 30 12:24:21 pc NetworkManager[925]: <info>  [1569839061.9881] dhcp4 (wlp2s0):   address xx.xx.xx.xx
Sep 30 12:24:21 pc NetworkManager[925]: <info>  [1569839061.9882] dhcp4 (wlp2s0):   plen 23 (255.255.254.0)
Sep 30 12:24:21 pc NetworkManager[925]: <info>  [1569839061.9883] dhcp4 (wlp2s0):   gateway yy.yy.yy.yy
Sep 30 12:24:21 pc NetworkManager[925]: <info>  [1569839061.9883] dhcp4 (wlp2s0):   lease time 1224
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839061.9884] dhcp4 (wlp2s0):   nameserver '192.168.1.101'
Sep 30 12:24:22 pc whoopsie[1124]: [12:24:21] Cannot reach: https://daisy.ubuntu.com
Sep 30 12:24:22 pc avahi-daemon[910]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address xx.xx.xx.xx.
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839061.9884] dhcp4 (wlp2s0):   nameserver '192.168.1.102'
Sep 30 12:24:22 pc avahi-daemon[910]: New relevant interface wlp2s0.IPv4 for mDNS.
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839061.9885] dhcp4 (wlp2s0):   domain name 'domain.it'
Sep 30 12:24:22 pc avahi-daemon[910]: Registering new address record for xx.xx.xx.xx on wlp2s0.IPv4.
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839061.9885] dhcp4 (wlp2s0): state changed unknown -> bound
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839061.9935] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839061.9950] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839061.9954] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839061.9962] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 30 12:24:22 pc dhclient[1146]: bound to xx.xx.xx.xx -- renewal in 496 seconds.
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839062.0863] manager: NetworkManager state is now CONNECTED_SITE
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839062.0874] policy: set 'Service1 Wireless' (wlp2s0) as default for IPv4 routing and DNS
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839062.0888] device (wlp2s0): Activation: successful, device activated.
Sep 30 12:24:22 pc NetworkManager[925]: <info>  [1569839062.0906] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 30 12:24:22 pc dbus-daemon[923]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.18' (uid=0 pid=925 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Sep 30 12:24:22 pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 30 12:24:22 pc whoopsie[1124]: [12:24:22] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/3
Sep 30 12:24:22 pc whoopsie[1124]: [12:24:22] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/3
Sep 30 12:24:22 pc whoopsie[1124]: [12:24:22] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/3
Sep 30 12:24:22 pc dbus-daemon[923]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 30 12:24:22 pc systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 30 12:24:22 pc nm-dispatcher: req:1 'up' [wlp2s0]: new request (1 scripts)
Sep 30 12:24:22 pc nm-dispatcher: req:1 'up' [wlp2s0]: start running ordered scripts...
Sep 30 12:24:22 pc nm-dispatcher: req:2 'connectivity-change': new request (1 scripts)
Sep 30 12:24:22 pc whoopsie[1124]: [12:24:22] online
Sep 30 12:24:22 pc systemd-resolved[891]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 30 12:24:22 pc systemd-resolved[891]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 30 12:24:22 pc nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
Sep 30 12:24:26 pc systemd-resolved[891]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 30 12:24:27 pc systemd-resolved[891]: message repeated 2 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.]
Sep 30 12:24:28 pc colord[984]: failed to get session [pid 917]: No data available
Sep 30 12:24:32 pc systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Sep 30 12:25:50 pc rtkit-daemon[1524]: Supervising 18 threads of 9 processes of 1 users.
Sep 30 12:25:50 pc rtkit-daemon[1524]: message repeated 3 times: [ Supervising 18 threads of 9 processes of 1 users.]
Sep 30 12:25:50 pc rtkit-daemon[1524]: Successfully made thread 5314 of process 5275 owned by '1000' RT at priority 10.
Sep 30 12:25:50 pc rtkit-daemon[1524]: Supervising 19 threads of 10 processes of 1 users.
Sep 30 12:25:50 pc rtkit-daemon[1524]: Successfully made thread 5315 of process 5275 owned by '1000' RT at priority 10.
Sep 30 12:25:50 pc rtkit-daemon[1524]: Supervising 20 threads of 10 processes of 1 users.
Sep 30 12:27:40 pc rtkit-daemon[1524]: message repeated 4 times: [ Supervising 20 threads of 10 processes of 1 users.]
Sep 30 12:27:40 pc rtkit-daemon[1524]: Successfully made thread 10645 of process 10619 owned by '1000' RT at priority 10.
Sep 30 12:27:40 pc rtkit-daemon[1524]: Supervising 21 threads of 11 processes of 1 users.
Sep 30 12:27:40 pc rtkit-daemon[1524]: Successfully made thread 10646 of process 10619 owned by '1000' RT at priority 10.
Sep 30 12:27:40 pc rtkit-daemon[1524]: Supervising 22 threads of 11 processes of 1 users.

Originally Posted by P5music I found a command ("tail -f /var/log/syslog") to have a log (see below). I hope it has enough information about what it happens at disconnection. I am no expert at all on this matter, and I need to assess what's going on to understand it and take action, if necessary, in both technical and legal way (I edited the log text to hide some information).

Yes, I'm sure your 'legal team' is anxious to bring suit against the *FREE WIFI PROVIDER* for not giving you better service.

Also note that the final part is about a forced automatic reconnection performed by means of a script I run on the system. Can you understand what is going on at the disconnection time? Sep 30 12:23:47 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=6e:3b:6b:11:e2:0f reason=4 locally_generated=1 Sep 30 12:23:47 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Sep 30 12:23:47 pc NetworkManager[925]: <warn> [1569839027.8538] sup-iface[0x557779cdd130,wlp2s0]: connection disconnected (reason -4) Sep 30 12:23:47 pc NetworkManager[925]: <info> [1569839027.8595] device (wlp2s0): supplicant interface state: completed -> disconnected Sep 30 12:23:47 pc NetworkManager[925]: <info> [1569839027.8596] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> disconnected Sep 30 12:23:47 pc NetworkManager[925]: <info> [1569839027.9626] device (wlp2s0): supplicant interface state: disconnected -> scanning Sep 30 12:23:47 pc NetworkManager[925]: <info> [1569839027.9627] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.8864] agent-manager: req[0x557779d8b060, :1.211/nmcli-connect/1000]: agent registered Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.8914] device (wlp2s0): disconnecting for new activation request. Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.8914] device (wlp2s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.8920] manager: NetworkManager state is now DISCONNECTING Sep 30 12:23:48 pc whoopsie[1124]: [12:23:48] offline Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9364] audit: op="connection-activate" uuid="5a7e0c8d-768a-457d-ab38-de8f47b4489a" name="Service1 Wireless" pid=1088 uid=1000 result="success" Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9369] device (wlp2s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Sep 30 12:23:48 pc avahi-daemon[910]: Withdrawing address record for fe80::508f:6678:fa2c:797 on wlp2s0. Sep 30 12:23:48 pc avahi-daemon[910]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::508f:6678:fa2c:797. Sep 30 12:23:48 pc avahi-daemon[910]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Sep 30 12:23:48 pc whoopsie[1124]: [12:23:48] Cannot reach: https://daisy.ubuntu.com Sep 30 12:23:48 pc dbus-daemon[923]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.18' (uid=0 pid=925 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Sep 30 12:23:48 pc systemd[1]: Starting Network Manager Script Dispatcher Service... Sep 30 12:23:48 pc dbus-daemon[923]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Sep 30 12:23:48 pc systemd[1]: Started Network Manager Script Dispatcher Service. Sep 30 12:23:48 pc nm-dispatcher: req:1 'connectivity-change': new request (1 scripts) Sep 30 12:23:48 pc nm-dispatcher: req:1 'connectivity-change': start running ordered scripts... Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9713] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 31934 Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9713] dhcp4 (wlp2s0): state changed bound -> done Sep 30 12:23:48 pc avahi-daemon[910]: Withdrawing address record for xx.xx.xx.xx on wlp2s0. Sep 30 12:23:48 pc avahi-daemon[910]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address xx.xx.xx.xx. Sep 30 12:23:48 pc avahi-daemon[910]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9770] manager: NetworkManager state is now DISCONNECTED Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9781] device (wlp2s0): Activation: starting connection 'Service1 Wireless' (5a7e0c8d-768a-457d-ab38-de8f47b4489a) Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9804] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9810] manager: NetworkManager state is now CONNECTING Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9822] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9827] device (wlp2s0): Activation: (wifi) connection 'Service1 Wireless' requires no security. No secrets needed. Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9827] Config: added 'ssid' value 'Service1 Wireless' Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9828] Config: added 'scan_ssid' value '1' Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9828] Config: added 'bgscan' value 'simple:30:-80:86400' Sep 30 12:23:48 pc NetworkManager[925]: <info> [1569839028.9828] Config: added 'key_mgmt' value 'NONE' Sep 30 12:23:48 pc wpa_supplicant[926]: wlp2s0: Reject scan trigger since one is already pending Sep 30 12:23:48 pc nm-dispatcher: req:2 'down' [wlp2s0]: new request (1 scripts) Sep 30 12:23:48 pc nm-dispatcher: req:2 'down' [wlp2s0]: start running ordered scripts... Sep 30 12:23:49 pc kernel: [ 1312.676708] wlp2s0: authenticate with 6c:3b:6b:11:e2:0f Sep 30 12:23:49 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz) Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.0127] device (wlp2s0): supplicant interface state: scanning -> disconnected Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.0128] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> disconnected Sep 30 12:23:49 pc kernel: [ 1312.695003] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 1/3) Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.0329] device (wlp2s0): supplicant interface state: disconnected -> authenticating Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.0330] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> authenticating Sep 30 12:23:49 pc kernel: [ 1312.743949] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 2/3) Sep 30 12:23:49 pc kernel: [ 1312.883271] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 3/3) Sep 30 12:23:49 pc wpa_supplicant[926]: wlp2s0: Trying to associate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz) Sep 30 12:23:49 pc kernel: [ 1312.963267] wlp2s0: authenticated Sep 30 12:23:49 pc kernel: [ 1312.967305] wlp2s0: associate with 6c:3b:6b:11:e2:0f (try 1/3) Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.3033] device (wlp2s0): supplicant interface state: authenticating -> associating Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.3033] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating Sep 30 12:23:49 pc kernel: [ 1313.075883] wlp2s0: associate with 6c:3b:6b:11:e2:0f (try 2/3) Sep 30 12:23:49 pc kernel: [ 1313.199276] wlp2s0: associate with 6c:3b:6b:11:e2:0f (try 3/3) Sep 30 12:23:49 pc kernel: [ 1313.331284] wlp2s0: association with 6c:3b:6b:11:e2:0f timed out Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.6991] device (wlp2s0): supplicant interface state: associating -> disconnected Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.6992] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> disconnected Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.8018] device (wlp2s0): supplicant interface state: disconnected -> scanning Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.8018] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning Sep 30 12:23:49 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with cc:2d:e0:c3:8c:77 (SSID='Service1 Wireless' freq=2427 MHz) Sep 30 12:23:49 pc kernel: [ 1313.496474] wlp2s0: authenticate with cc:2d:e0:c3:8c:77 Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.8458] device (wlp2s0): supplicant interface state: scanning -> authenticating Sep 30 12:23:49 pc NetworkManager[925]: <info> [1569839029.8458] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating Sep 30 12:23:49 pc kernel: [ 1313.511288] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 1/3) Sep 30 12:23:50 pc kernel: [ 1313.675376] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 2/3) Sep 30 12:23:50 pc kernel: [ 1313.779353] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 3/3) Sep 30 12:23:50 pc kernel: [ 1313.891346] wlp2s0: authentication with cc:2d:e0:c3:8c:77 timed out Sep 30 12:23:50 pc NetworkManager[925]: <info> [1569839030.2672] device (wlp2s0): supplicant interface state: authenticating -> disconnected Sep 30 12:23:50 pc NetworkManager[925]: <info> [1569839030.2673] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected Sep 30 12:23:50 pc NetworkManager[925]: <info> [1569839030.3700] device (wlp2s0): supplicant interface state: disconnected -> scanning Sep 30 12:23:50 pc NetworkManager[925]: <info> [1569839030.3701] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning Sep 30 12:23:51 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz) Sep 30 12:23:51 pc kernel: [ 1315.097127] wlp2s0: authenticate with 6c:3b:6b:11:e2:0f Sep 30 12:23:51 pc kernel: [ 1315.117728] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 1/3) Sep 30 12:23:51 pc NetworkManager[925]: <info> [1569839031.4522] device (wlp2s0): supplicant interface state: scanning -> authenticating Sep 30 12:23:51 pc NetworkManager[925]: <info> [1569839031.4523] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating Sep 30 12:23:51 pc kernel: [ 1315.223459] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 2/3) Sep 30 12:23:51 pc kernel: [ 1315.327470] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 3/3) Sep 30 12:23:51 pc kernel: [ 1315.459514] wlp2s0: authentication with 6c:3b:6b:11:e2:0f timed out Sep 30 12:23:51 pc NetworkManager[925]: <info> [1569839031.8348] device (wlp2s0): supplicant interface state: authenticating -> disconnected Sep 30 12:23:51 pc NetworkManager[925]: <info> [1569839031.8350] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected Sep 30 12:23:52 pc NetworkManager[925]: <info> [1569839032.8399] device (wlp2s0): supplicant interface state: disconnected -> scanning Sep 30 12:23:52 pc NetworkManager[925]: <info> [1569839032.8400] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning Sep 30 12:23:52 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with cc:2d:e0:c3:8c:77 (SSID='Service1 Wireless' freq=2427 MHz) Sep 30 12:23:52 pc kernel: [ 1316.540843] wlp2s0: authenticate with cc:2d:e0:c3:8c:77 Sep 30 12:23:52 pc NetworkManager[925]: <info> [1569839032.8901] device (wlp2s0): supplicant interface state: scanning -> authenticating Sep 30 12:23:52 pc NetworkManager[925]: <info> [1569839032.8902] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating Sep 30 12:23:52 pc kernel: [ 1316.555889] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 1/3) Sep 30 12:23:52 pc kernel: [ 1316.659623] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 2/3) Sep 30 12:23:53 pc kernel: [ 1316.763618] wlp2s0: send auth to cc:2d:e0:c3:8c:77 (try 3/3) Sep 30 12:23:53 pc kernel: [ 1316.867605] wlp2s0: authentication with cc:2d:e0:c3:8c:77 timed out Sep 30 12:23:53 pc NetworkManager[925]: <info> [1569839033.2511] device (wlp2s0): supplicant interface state: authenticating -> disconnected Sep 30 12:23:53 pc NetworkManager[925]: <info> [1569839033.2511] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected Sep 30 12:23:54 pc NetworkManager[925]: <info> [1569839034.2566] device (wlp2s0): supplicant interface state: disconnected -> scanning Sep 30 12:23:54 pc NetworkManager[925]: <info> [1569839034.2567] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with 6c:3b:6b:11:ff:6f (SSID='Service1 Wireless' freq=2442 MHz) Sep 30 12:23:55 pc kernel: [ 1318.977894] wlp2s0: authenticate with 6c:3b:6b:11:ff:6f Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3318] device (wlp2s0): supplicant interface state: scanning -> authenticating Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3319] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating Sep 30 12:23:55 pc kernel: [ 1318.997409] wlp2s0: send auth to 6c:3b:6b:11:ff:6f (try 1/3) Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: Trying to associate with 6c:3b:6b:11:ff:6f (SSID='Service1 Wireless' freq=2442 MHz) Sep 30 12:23:55 pc kernel: [ 1319.001221] wlp2s0: authenticated Sep 30 12:23:55 pc kernel: [ 1319.005196] wlp2s0: associate with 6c:3b:6b:11:ff:6f (try 1/3) Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3416] device (wlp2s0): supplicant interface state: authenticating -> associating Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3420] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: Associated with 6c:3b:6b:11:ff:6f Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:11:ff:6f completed [id=0 id_str=] Sep 30 12:23:55 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Sep 30 12:23:55 pc kernel: [ 1319.030029] wlp2s0: RX AssocResp from 6c:3b:6b:11:ff:6f (capab=0x421 status=0 aid=2) Sep 30 12:23:55 pc kernel: [ 1319.030159] wlp2s0: associated Sep 30 12:23:55 pc kernel: [ 1319.030767] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3699] device (wlp2s0): supplicant interface state: associating -> completed Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3699] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Service1 Wireless" Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3700] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> completed Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3711] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3719] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) Sep 30 12:23:55 pc NetworkManager[925]: <info> [1569839035.3771] dhcp4 (wlp2s0): dhclient started with pid 1146 Sep 30 12:23:55 pc avahi-daemon[910]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::8bbb:81c7:991:352a. Sep 30 12:23:55 pc avahi-daemon[910]: New relevant interface wlp2s0.IPv6 for mDNS. Sep 30 12:23:55 pc avahi-daemon[910]: Registering new address record for fe80::8bbb:81c7:991:352a on wlp2s0.*. Sep 30 12:23:55 pc dhclient[1146]: DHCPREQUEST for xx.xx.xx.xx on wlp2s0 to 255.255.255.255 port 67 (xid=0x53b98d71) Sep 30 12:23:57 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-80 noise=-91 txrate=11000 Sep 30 12:23:59 pc dhclient[1146]: DHCPREQUEST for xx.xx.xx.xx on wlp2s0 to 255.255.255.255 port 67 (xid=0x53b98d71) Sep 30 12:23:59 pc systemd[1]: NetworkManager-dispatcher.service: Succeeded. Sep 30 12:24:03 pc dhclient[1146]: DHCPREQUEST for xx.xx.xx.xx on wlp2s0 to 255.255.255.255 port 67 (xid=0x53b98d71) Sep 30 12:24:09 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-82 noise=-91 txrate=6500 Sep 30 12:24:09 pc dhclient[1146]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x8f7a555e) Sep 30 12:24:12 pc kernel: [ 1335.766779] Bluetooth: hci0: corrupted ACL packet Sep 30 12:24:12 pc dhclient[1146]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 8 (xid=0x8f7a555e) Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: SME: Trying to authenticate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz) Sep 30 12:24:17 pc kernel: [ 1340.875693] wlp2s0: disconnect from AP 6c:3b:6b:11:ff:6f for new auth to 6c:3b:6b:11:e2:0f Sep 30 12:24:17 pc kernel: [ 1340.888611] wlp2s0: authenticate with 6c:3b:6b:11:e2:0f Sep 30 12:24:17 pc kernel: [ 1340.902962] wlp2s0: send auth to 6c:3b:6b:11:e2:0f (try 1/3) Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Sep 30 12:24:17 pc NetworkManager[925]: <info> [1569839057.2359] device (wlp2s0): supplicant interface state: completed -> authenticating Sep 30 12:24:17 pc NetworkManager[925]: <info> [1569839057.2359] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> authenticating Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: Trying to associate with 6c:3b:6b:11:e2:0f (SSID='Service1 Wireless' freq=2427 MHz) Sep 30 12:24:17 pc kernel: [ 1340.949268] wlp2s0: authenticated Sep 30 12:24:17 pc kernel: [ 1340.949760] wlp2s0: associate with 6c:3b:6b:11:e2:0f (try 1/3) Sep 30 12:24:17 pc NetworkManager[925]: <info> [1569839057.2871] device (wlp2s0): supplicant interface state: authenticating -> associating Sep 30 12:24:17 pc NetworkManager[925]: <info> [1569839057.2872] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating Sep 30 12:24:17 pc kernel: [ 1340.969644] wlp2s0: RX ReassocResp from 6c:3b:6b:11:e2:0f (capab=0x421 status=0 aid=5) Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: Associated with 6c:3b:6b:11:e2:0f Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:11:e2:0f completed [id=0 id_str=] Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Sep 30 12:24:17 pc kernel: [ 1340.969896] wlp2s0: associated Sep 30 12:24:17 pc NetworkManager[925]: <info> [1569839057.3121] device (wlp2s0): supplicant interface state: associating -> completed Sep 30 12:24:17 pc NetworkManager[925]: <info> [1569839057.3122] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> completed Sep 30 12:24:17 pc wpa_supplicant[926]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-51 noise=-90 txrate=6500 Sep 30 12:24:20 pc dhclient[1146]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 19 (xid=0x8f7a555e) Sep 30 12:24:21 pc dhclient[1146]: DHCPOFFER of xx.xx.xx.xx from zz.zz.zz.zz Sep 30 12:24:21 pc dhclient[1146]: DHCPREQUEST for xx.xx.xx.xx on wlp2s0 to 255.255.255.255 port 67 (xid=0x5e557a8f) Sep 30 12:24:21 pc dhclient[1146]: DHCPACK of xx.xx.xx.xx from zz.zz.zz.zz (xid=0x8f7a555e) Sep 30 12:24:21 pc NetworkManager[925]: <info> [1569839061.9881] dhcp4 (wlp2s0): address xx.xx.xx.xx Sep 30 12:24:21 pc NetworkManager[925]: <info> [1569839061.9882] dhcp4 (wlp2s0): plen 23 (255.255.254.0) Sep 30 12:24:21 pc NetworkManager[925]: <info> [1569839061.9883] dhcp4 (wlp2s0): gateway yy.yy.yy.yy Sep 30 12:24:21 pc NetworkManager[925]: <info> [1569839061.9883] dhcp4 (wlp2s0): lease time 1224 Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839061.9884] dhcp4 (wlp2s0): nameserver '192.168.1.101' Sep 30 12:24:22 pc whoopsie[1124]: [12:24:21] Cannot reach: https://daisy.ubuntu.com Sep 30 12:24:22 pc avahi-daemon[910]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address xx.xx.xx.xx. Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839061.9884] dhcp4 (wlp2s0): nameserver '192.168.1.102' Sep 30 12:24:22 pc avahi-daemon[910]: New relevant interface wlp2s0.IPv4 for mDNS. Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839061.9885] dhcp4 (wlp2s0): domain name 'domain.it' Sep 30 12:24:22 pc avahi-daemon[910]: Registering new address record for xx.xx.xx.xx on wlp2s0.IPv4. Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839061.9885] dhcp4 (wlp2s0): state changed unknown -> bound Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839061.9935] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839061.9950] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839061.9954] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839061.9962] manager: NetworkManager state is now CONNECTED_LOCAL Sep 30 12:24:22 pc dhclient[1146]: bound to xx.xx.xx.xx -- renewal in 496 seconds. Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839062.0863] manager: NetworkManager state is now CONNECTED_SITE Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839062.0874] policy: set 'Service1 Wireless' (wlp2s0) as default for IPv4 routing and DNS Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839062.0888] device (wlp2s0): Activation: successful, device activated. Sep 30 12:24:22 pc NetworkManager[925]: <info> [1569839062.0906] manager: NetworkManager state is now CONNECTED_GLOBAL Sep 30 12:24:22 pc dbus-daemon[923]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.18' (uid=0 pid=925 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Sep 30 12:24:22 pc systemd[1]: Starting Network Manager Script Dispatcher Service... Sep 30 12:24:22 pc whoopsie[1124]: [12:24:22] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/3 Sep 30 12:24:22 pc whoopsie[1124]: [12:24:22] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/3 Sep 30 12:24:22 pc whoopsie[1124]: [12:24:22] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/3 Sep 30 12:24:22 pc dbus-daemon[923]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Sep 30 12:24:22 pc systemd[1]: Started Network Manager Script Dispatcher Service. Sep 30 12:24:22 pc nm-dispatcher: req:1 'up' [wlp2s0]: new request (1 scripts) Sep 30 12:24:22 pc nm-dispatcher: req:1 'up' [wlp2s0]: start running ordered scripts... Sep 30 12:24:22 pc nm-dispatcher: req:2 'connectivity-change': new request (1 scripts) Sep 30 12:24:22 pc whoopsie[1124]: [12:24:22] online Sep 30 12:24:22 pc systemd-resolved[891]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 30 12:24:22 pc systemd-resolved[891]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 30 12:24:22 pc nm-dispatcher: req:2 'connectivity-change': start running ordered scripts... Sep 30 12:24:26 pc systemd-resolved[891]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 30 12:24:27 pc systemd-resolved[891]: message repeated 2 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Sep 30 12:24:28 pc colord[984]: failed to get session [pid 917]: No data available Sep 30 12:24:32 pc systemd[1]: NetworkManager-dispatcher.service: Succeeded. Sep 30 12:25:50 pc rtkit-daemon[1524]: Supervising 18 threads of 9 processes of 1 users. Sep 30 12:25:50 pc rtkit-daemon[1524]: message repeated 3 times: [ Supervising 18 threads of 9 processes of 1 users.] Sep 30 12:25:50 pc rtkit-daemon[1524]: Successfully made thread 5314 of process 5275 owned by '1000' RT at priority 10. Sep 30 12:25:50 pc rtkit-daemon[1524]: Supervising 19 threads of 10 processes of 1 users. Sep 30 12:25:50 pc rtkit-daemon[1524]: Successfully made thread 5315 of process 5275 owned by '1000' RT at priority 10. Sep 30 12:25:50 pc rtkit-daemon[1524]: Supervising 20 threads of 10 processes of 1 users. Sep 30 12:27:40 pc rtkit-daemon[1524]: message repeated 4 times: [ Supervising 20 threads of 10 processes of 1 users.] Sep 30 12:27:40 pc rtkit-daemon[1524]: Successfully made thread 10645 of process 10619 owned by '1000' RT at priority 10. Sep 30 12:27:40 pc rtkit-daemon[1524]: Supervising 21 threads of 11 processes of 1 users. Sep 30 12:27:40 pc rtkit-daemon[1524]: Successfully made thread 10646 of process 10619 owned by '1000' RT at priority 10. Sep 30 12:27:40 pc rtkit-daemon[1524]: Supervising 22 threads of 11 processes of 1 users.

Yes, we understand, the free wifi is dropping you; either because you've been connected too long, are doing something the network deems unsafe, or they're moving you from one node to another. Since, AGAIN, we know nothing about the network, speculation is all there is. You are STILL left with your original three choices:

• Live with the level of service you're getting for FREE
• PAY FOR something better
• Use the good amount of information you've been given and gather your own data for your 'legal team'.

Based on this thread, you won't even talk to others around you to see if they have similar issues, so I'm having a hard time imagining any lawyer taking this seriously, since it's based on someone who (by their own admission), doesn't have the technical expertise to make any sort of determination, and who doesn't have any other data.

@TB0ne
I was tempted not to reply to you, but it seems that you are helping now.
I read that you explicitly confirm the fact that "they" are dropping me. How to prove it definitively?
Can you (or someone else) point out the lines where it is visible, and why?

Originally Posted by P5music @TB0ne I was tempted not to reply to you, but it seems that you are helping now.

Reply or not; doesn't matter to anyone here.

I read that you explicitly confirm the fact that "they" are dropping me. How to prove it definitively? Can you (or someone else) point out the lines where it is visible, and why?

The word "disconnected" would be a good one to look for...that's your clue that you're disconnected. And **AGAIN**, since you still don't appear to be listening or understanding:

• "They" can drop you for whatever reason they want.
• This is a FREE SERVICE; if you want better, then PAY FOR IT
• You *STILL* don't say what you're doing, since it could very well be YOUR BEHAVIOR that is causing the network to drop you.
• You *STILL* won't talk to anyone around you, to see if they have similar issues.

Any argument you make is totally invalid, since you provide no details, and nothing is known about the network. Seem like you just want to whine about how bad the free service is, but won't actually pay for something more reliable.

@TB0ne

I can answer to all your concerns.

I am doing nothing strange with the network.
Sometimes I just turn on my notebook and it automatically connects to one of the two networks (they have different name but share the same infrastructure) and suddenly I realize that the very first operation I attempted, like opening email, has already failed because of the disconnection, but the wifi is connected apparently (rarely the disconnection shows itself as wifi disconnection).

I do not think that they are enforcing their right to disconnect me for "whatever reason they want" because it is a random event and it happens very often. The service is so unuseable and forms and sites always timeout. Few minutes of connection is the best scenario.

You can trust me, I have polled the people in the surroudings at least two times, and they said things like:
"apparent connection" or "it hangs" and so on.

It is not a "free service" like you can find in some shops. It is an important public service, intended for students, scholars, library users.

It is possible that only some devices are disconnected, for example because of some firmware issue, but it has to be fixed, they have to acknowledge the problem and not neglect a large group of users. Note that my computer works well with other networks.

It is important to assess whether it is evident from the log that "they" are disconnecting my computer or refusing some important data like dns, dhcp and so on.
With "they" I mean the wifi network system at same level, like router, gateway, and so on.

Originally Posted by P5music @TB0ne I can answer to all your concerns.

I have no concerns regarding your connectivity at all.

I am doing nothing strange with the network.

Again, you are just not listening or understanding; you claim to have 'important data transactions', yet won't pay for a reliable service, and choose to whine about occasional disconnects? Still not sure what anyone, on any forum, is going to be able to tell you. AGAIN, videos/bittorrent/etc., may not be 'strange', but they COULD very well be throttled and/or dropped as non-essential, to give OTHERS access to better network speeds. AGAIN, this is up to the network administrators.

Sometimes I just turn on my notebook and it automatically connects to one of the two networks (they have different name but share the same infrastructure) and suddenly I realize that the very first operation I attempted, like opening email, has already failed because of the disconnection, but the wifi is connected apparently (rarely the disconnection shows itself as wifi disconnection).

Great; so you had a weak signal, and your system did what it should do...connect to another node. Why is this surprising?

I do not think that they are enforcing their right to disconnect me for "whatever reason they want" because it is a random event and it happens very often. The service is so unuseable and forms and sites always timeout. Few minutes of connection is the best scenario.

THEN PAY FOR SOMETHING BETTER

You can trust me, I have polled the people in the surroudings at least two times, and they said things like: "apparent connection" or "it hangs" and so on.

And before you said you could not do a 'poll'...but now we can trust you that you did ask? AGAIN: it's free; either pay for something better or live with it.

It is not a "free service" like you can find in some shops. It is an important public service, intended for students, scholars, library users.

Oh? Not free? Then how much do you pay for it? If the answer is "nothing, because it's a public/community network", then it IS FREE. Again, as you said yourself, most people use their OWN networking, that they pay for.

It is possible that only some devices are disconnected, for example because of some firmware issue, but it has to be fixed, they have to acknowledge the problem and not neglect a large group of users. Note that my computer works well with other networks. It is important to assess whether it is evident from the log that "they" are disconnecting my computer or refusing some important data like dns, dhcp and so on. With "they" I mean the wifi network system at same level, like router, gateway, and so on.

AGAIN, since you are still not listening/understanding; without knowing the rules of the network and how it's managed, there is ABSOLUTELY NOTHING we can tell you, do you not understand this??? All you're EVER going to see is a disconnect event.

Why don't you talk to your 'legal team', and see what they can suggest?? Since this is such an 'important case in the public interest', I'm sure they'd be happy to hire teams of techs to do research for you.

@TB0ne

I read your answers and I see that in alternating lines you seem lucid, so I answer to those.

I did not mean you are concerned about my problem but instead you seems to deal with the way I write my posts here that you say lack important information. So although I see that many of your concerns are unreasonable and maybe you are a troll (I reported your conduct on another thread) still I try to complete my writing so it can be exhaustive, at least for other people reading this thread that would hopefully chime in to help.

Before I put the script for re-connection on my system I used my personal phone to connect. Now the script is helping me not to use my data because they are limited. Yes I pay for them but why not use a public service intended to support people? Note that it is free just for the single user, while it it is expensive for the public institution that pays for it.

I wrote very clearly that disconnections happens at the very beginning of the connection, and doing nothing strange or dangerous but trying to open emails.
The problem is not only with this Ubuntu system but also with Windows, and both with fresh installations.

I do not have weak signal. Many tests of mine were performed in a room where the wi-fi router is visible on the wall.

Quoting myself answers the next point in your answer:
[QUOTE]
Asking other people, who by the way nowadays mainly rely on their private 3G/4G connection is not useful, unless it is a real poll.
However it's the next thing to do. Checking the connection in a more technical manner is the first step I think to gather some information.
I do not understand how you do not agree that a public service has to work as intended, at least according to minimum common-sense standard like not causing me a disconnection while I am paying something online or applying to a job offer.
[QUOTE]

They do not acknowledge the problem so they do not collaborate. The legal issue is to be assessed.
This is why I ask for a more technical help here.
Maybe you do not understand that the main reason I am here is to get helped.

@the other users
I see that this thread is read by a lot people. Maybe many are amused, I think.
I want to apologize for this exhausting exchange, but I ensure you that I am not "feeding the troll". I really need help for the disconnection problem. Thanks in advance for your suggestions.

Originally Posted by P5music @TB0ne I read your answers and I see that in alternating lines you seem lucid, so I answer to those. I did not mean you are concerned about my problem but instead you seems to deal with the way I write my posts here that you say lack important information. So altough I see that many of your concerns are unreasonable and maybe you are a troll (I reported your conduct on another thread) but still I try to complete my writing so it can be exaustive, at least for other people reading this thread that would hopefully chime in to help.

Again, report whatever you want; the only troll seems to be you. You keep whining about a free service not being better, and seem to keep harping on a 'legal team' in the 'public interest'. **AGAIN**, since you seem to not pay attention, you have two choices:

• Use the free service
• PAY FOR YOUR OWN

Pick one. Can't be more clear. AGAIN, without knowing ANYTHING about the network, no one, anywhere, is going to be able to tell you anything. Do you not understand that??? The network admins may have their own rules that you don't know about, and CANNOT KNOW if you don't ask THEM. Asking us won't get you anything. And if writing is so 'exhaustive' for you, then feel free to NOT post back here. That would be best.

Before I put the script for reconnection on my system I used my personal phone to connect. Now the script is helping me not to use my data because they are limited. Yes I pay for them but why not use a public service intended to support people? Note that it is free just for the single use, while it it is expensive for the public institution that pays for it.

So AGAIN...you are whining about a FREE SERVICE, right??? Again, take your complaints about the network performance to someone at the 'public institution'. There is *STILL* nothing anyone here can do for you.

I wrote very clearly that disconnections happen at the very beginning of the connection, and doing nothing strange or dangerous but trying to open emails. The problem is not only with this Ubuntu system but also with Windows, and both with fresh installations. I do not have weak signal. Many tests of mine were performed in a room where the wifi router is visible on the wall. Quoting myself answers the next point in your answer: "Asking other people, who by the way nowadays mainly rely on their private 3G/4G connection is not useful, unless it is a real poll." However it's the next thing to do. Checking the connection in a more technical manner is the first step I think to gather some information. I do not understand how you do not agree that a public service has to work as intended, at least according to minimum common-sense standard like not causing me a disconnection while I am paying something online or applying to a job offer. They do not acknowledge the problem so they do not collaborate. The legal issue is to be assessed. This is why I ask for a more technical help here. Maybe you do not understand that the main reason I am here is to get helped.

Great; so again, take your extensive tests to your legal team, the people running the network, or whomever you want....there isn't anything anyone on a forum can do to help you. Go raise your 'legal issue'...this isn't a legal forum, so nothing we can do there.

And AGAIN: if it's critical, PAY FOR SOMETHING BETTER. Otherwise, quit whining about it, or take your complaints to someone who runs the network. Not sure what problem you're having with comprehension, but here it is again, very simply and plainly, and is bolded for emphasis only:

Take your network complaints to those who run the network. There is **ABSOLUTELY NOTHING** we can tell you, help you with, etc., since the REMOTE NETWORK IS DISCONNECTING YOU.

If they won't help you, what do you expect us to do? Call them for you?

@the other users I see that this thread is read by a lot people. Maybe many are amused, I think. I want to apologize for this exhausting exchange, but I ensure you that I am not "feeding the troll". I really need help for the disconnection problem. Thanks in advance for your suggestions. Please help me.

Yes, folks are amused, but most probably by you and your lack of understanding what you're told.

The help you need won't come from a technical forum.

@TB0ne
Sorry for your severe condition, but I asked for technical questions here. All further information was asked by you and I gave them because you seem to have serious lack of metacognitive competence. You are making a joke of yourself. Being good at shell scripting makes not you capable of high level human communication.

Originally Posted by P5music @TB0ne Sorry for your severe condition, but I asked for technical questions here. All further information was asked by you and I gave them because you seem to have serious lack of metacognitive competence. You are making a joke of yourself. Being good at shell scripting makes not you capable of high level human communication.

Guess a simple sentence was too much for you to understand. You are obviously not comprehending what you're being told, and folks here just can't make it as simple as you need it to be.

Seek help.