[SOLVED] Asking for connectivity savers for Terminals
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Here, my Chromium browser is moderately accelerated under the few ad-blockers, cache and history blockers, the data saver by Google itself etc ... however where are the ‘‘connectivity savers’’ (like ones for Chromium) optimized for Terminals? I have researched PLENTY related (REGARDLESS slightly or tightly) keywords but been given ALMOST NOTHING.
Here, my Chromium browser is moderately accelerated under the few ad-blockers, cache and history blockers, the data saver by Google itself etc ... however where are the ‘‘connectivity savers’’ (like ones for Chromium) optimized for Terminals? I have researched PLENTY related (REGARDLESS slightly or tightly) keywords but been given ALMOST NOTHING.
I'd say for one (carefully and after data backups of course) have a look at
Code:
cat /etc/sysctl.conf
if we knew what operating system( ie distro )...
assuming you mean net connectivity in a terminal, otherwise they have tweaks of their own?
Have fun!
Last edited by jamison20000e; 05-28-2017 at 09:25 PM.
Reason: added caution
Hi.I'd say for one (carefully and after data backups of course) have a look at
Code:
# cat /etc/sysctl.conf
if we knew what operating system( ie distro )...
assuming you mean net connectivity in a terminal, otherwise they have tweaks of their own?
Have fun!
Yes network connectivity done under a terminal session, and the distro are F26 and LMDE thanks? Here, how to start tweaking thanks?
Code:
[hdscania@dnf ~]$ sudo cat /etc/sysctl.conf
# sysctl settings are defined through files in
# /usr/lib/sysctl.d/, /run/sysctl.d/, and /etc/sysctl.d/.
#
# Vendors settings live in /usr/lib/sysctl.d/.
# To override a whole file, create a new file with the same in
# /etc/sysctl.d/ and put new settings there. To override
# only specific settings, add a file with a lexically later
# name in /etc/sysctl.d/ and put new settings there.
#
# For more information, see sysctl.conf(5) and sysctl.d(5).
[hdscania@dnf ~]$ cd /usr/lib/sysctl.d
[hdscania@dnf sysctl.d]$ ls -la
total 24
drwxr-xr-x. 2 root root 4096 May 21 12:54 .
dr-xr-xr-x. 55 root root 4096 May 21 13:56 ..
-rw-r--r--. 1 root root 293 Feb 28 17:22 00-system.conf
-rw-r--r--. 1 root root 1810 May 5 18:17 10-default-yama-scope.conf
-rw-r--r--. 1 root root 521 Mar 16 17:20 50-coredump.conf
-rw-r--r--. 1 root root 1318 Mar 16 17:20 50-default.conf
[hdscania@dnf sysctl.d]$
XXXX@XXXXX:~$ cat /etc/sysctl.conf
#
# /etc/sysctl.conf - Configuration file for setting system variables
# See /etc/sysctl.d/ for additional system variables.
# See sysctl.conf (5) for information.
#
#kernel.domainname = example.com
# Uncomment the following to stop low-level messages on console
#kernel.printk = 3 4 1 3
##############################################################3
# Functions previously found in netbase
#
# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
# Turn on Source Address Verification in all interfaces to
# prevent some spoofing attacks
#net.ipv4.conf.default.rp_filter=1
#net.ipv4.conf.all.rp_filter=1
# Uncomment the next line to enable TCP/IP SYN cookies
# See http://lwn.net/Articles/277146/
# Note: This may impact IPv6 TCP sessions too
#net.ipv4.tcp_syncookies=1
# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.ip_forward=1
# Uncomment the next line to enable packet forwarding for IPv6
# Enabling this option disables Stateless Address Autoconfiguration
# based on Router Advertisements for this host
#net.ipv6.conf.all.forwarding=1
###################################################################
# Additional settings - these settings can improve the network
# security of the host and prevent against some network attacks
# including spoofing attacks and man in the middle attacks through
# redirection. Some network environments, however, require that these
# settings are disabled so review and enable them as needed.
#
# Do not accept ICMP redirects (prevent MITM attacks)
#net.ipv4.conf.all.accept_redirects = 0
#net.ipv6.conf.all.accept_redirects = 0
# _or_
# Accept ICMP redirects only for gateways listed in our default
# gateway list (enabled by default)
# net.ipv4.conf.all.secure_redirects = 1
#
# Do not send ICMP redirects (we are not a router)
#net.ipv4.conf.all.send_redirects = 0
#
# Do not accept IP source route packets (we are not a router)
#net.ipv4.conf.all.accept_source_route = 0
#net.ipv6.conf.all.accept_source_route = 0
#
# Log Martian Packets
#net.ipv4.conf.all.log_martians = 1
#
###################################################################
# Magic system request Key
# 0=disable, 1=enable all
# Debian kernels have this set to 0 (disable the key)
# See https://www.kernel.org/doc/Documentation/sysrq.txt
# for what other values do
#kernel.sysrq=1
###################################################################
# Protected links
#
# Protects against creating or following links under certain conditions
# Debian kernels have both set to 1 (restricted)
# See https://www.kernel.org/doc/Documentation/sysctl/fs.txt
#fs.protected_hardlinks=0
#fs.protected_symlinks=0
#
vm.swappiness = 11
Here, I must NOT be a , and I have confirmed which Chromium has been ‘‘biting’’ my data too much, so I have now tried few lightweight browsers,
Code:
# dnf install -y tor midori qupzilla --nogpgcheck
But under Tor I have been experiencing a froze,
Code:
bash-4.4$ sudo dnf reinstall -y --nogpgcheck tor && tor
Last metadata expiration check: 0:04:10 ago on Thu Jun 01 08:49:13 2017 CST.
Dependencies resolved.
===============================================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================================
Reinstalling:
tor x86_64 0.2.9.10-1.fc26 fedora 2.4 M
Transaction Summary
===============================================================================================================================================================
Total download size: 2.4 M
Downloading Packages:
[MIRROR] tor-0.2.9.10-1.fc26.x86_64.rpm: Status code: 503 for http://mirrors.ustc.edu.cn/fedora/development/26/Everything/x86_64/os/Packages/t/tor-0.2.9.10-1.fc26.x86_64.rpm
tor-0.2.9.10-1.fc26.x86_64.rpm 1.7 MB/s | 2.4 MB 00:01
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 1.0 MB/s | 2.4 MB 00:02
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Running scriptlet: None 1/1
Preparing : 1/1
Running scriptlet: tor-0.2.9.10-1.fc26.x86_64 1/2
Reinstalling : tor-0.2.9.10-1.fc26.x86_64 1/2
Running scriptlet: tor-0.2.9.10-1.fc26.x86_64 1/2
Running scriptlet: tor-0.2.9.10-1.fc26.x86_64 2/2
Erasing : tor-0.2.9.10-1.fc26.x86_64 2/2
Running scriptlet: tor-0.2.9.10-1.fc26.x86_64 2/2
Verifying : tor-0.2.9.10-1.fc26.x86_64 1/2
Verifying : tor-0.2.9.10-1.fc26.x86_64 2/2
Reinstalled:
tor.x86_64 0.2.9.10-1.fc26
Complete!
Jun 01 08:53:42.539 [notice] Tor 0.2.9.10 (git-1f6c8eda0073f464) running on Linux with Libevent 2.0.22-stable, OpenSSL 1.1.0e-fips and Zlib 1.2.11.
Jun 01 08:53:42.539 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 01 08:53:42.539 [notice] Read configuration file "/etc/tor/torrc".
Jun 01 08:53:42.542 [notice] Opening Socks listener on 127.0.0.1:9050
Jun 01 08:53:42.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jun 01 08:53:42.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jun 01 08:53:42.000 [notice] Bootstrapped 0%: Starting
Jun 01 08:53:43.000 [notice] Bootstrapped 5%: Connecting to directory server
Jun 01 08:53:43.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Jun 01 08:53:45.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection
Jun 01 08:53:46.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus
Jun 01 08:53:46.000 [notice] Bootstrapped 25%: Loading networkstatus consensus
Jun 01 08:53:57.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Jun 01 08:53:57.000 [notice] Bootstrapped 40%: Loading authority key certs
Jun 01 08:53:58.000 [notice] Bootstrapped 45%: Asking for relay descriptors
Jun 01 08:53:58.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7059, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
Jun 01 08:53:59.000 [notice] Bootstrapped 50%: Loading relay descriptors
Jun 01 08:54:02.000 [notice] Bootstrapped 57%: Loading relay descriptors
Jun 01 08:54:04.000 [notice] Bootstrapped 63%: Loading relay descriptors
Jun 01 08:54:04.000 [notice] Bootstrapped 68%: Loading relay descriptors
Jun 01 08:54:59.000 [notice] No circuits are opened. Relaxed timeout for circuit 5 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. 3 guards are live.
Jun 01 08:55:06.000 [notice] Bootstrapped 75%: Loading relay descriptors
Jun 01 08:55:08.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Jun 01 08:55:08.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Jun 01 08:55:12.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jun 01 08:55:12.000 [notice] Bootstrapped 100%: Done
Finally, I have been researching for few Google related extensions for Midori and Qupzilla.
It seems ... NO extensions could be plugged in under ‘‘Links’’, and I have a concern if there are extensions of the Google and Firefox services and the mail clients available for Midori and Qupzilla, or any similar LIGHTWEIGHT browsers.
However, why a high-degree encryption of web browsers is slowing your connectivity down?
Tor Browser is slower for me and 8Gb Ram on an i5, even with Debian\Sid... it wraps data in math (kinda ) adding more steps tho some newer cryptography methods are faster than old ones like PCs.
My hardware system is worse than you by i3-2367 of x64 processor and 3.72GiB RAMs, but is Tor (if just working) to be much more slowing down than your hardware system?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.