Given less voyeurism, testing bandwidth can also be done this way and with less side effects. Set desired bandwidth with e.g. -L 12M for 12mbps and send them a constant stream with they pipe into /dev/null like this:
pv -r -L 32M /dev/urandom | ssh user@my.testserv.er "cat > /dev/null"
On Gentoo pipe view pv is available as sys-apps/pv.
KVM - easy Network card NIC PCI pass through with virt-manager
with virt-manager, it is a breeze to select the PCI device (in this case enp3s0 NIC) for pass through to guest vm, in case the vm shall get it’s very own dedicated nic:
notice: the passed NIC dissapears from the ip -c a list of NICs on the server
https://serverfault.com/questions/446658/assign-individual-nic-to-kvm-guest
#linux #gnu #gnulinux #opensource #administration #sysops #kvm #nic #networking
Originally posted at: https://dwaves.de/2022/01/09/kvm-easy-network-card-nic-pci-pass-through-with-virt-manager/
First and foremost, Wi-Fi Certified 6 Release 2 offers greater uplink capacity. It adds support for uplink multi-user MIMO, allowing multiple devices to upload content concurrently to an access point (AP). It supports transfer speeds of up to 9.6Gbps, which is more than double the maximum speed supported by Wi-Fi 5.
New features introduced in Wi-Fi 6 Release 2 will work across all three bands — 2.4GHz, 5GHz, and 6GHz — supported by the Wi-Fi 6 standard. The new release comes as the adoption of Wi-Fi 6 continues to grow by leaps and bounds. According to the Wi-Fi Alliance, nearly 2 billion Wi-Fi 6 devices are set to enter the market in 2022.
So it will be great for on-premise gaming, backups to NAS devices, mesh networking etc, but no residential WAN connections come anywhere near this performance. Even though I have a Wi-Fi 5 device at home, I still find the good old 2.4 GHz is more reliable and has better range, even if it is a bit slower.
See https://www.xda-developers.com/wi-fi-6-release-2-faster-upload-speeds/
#Blog, #networking, #technology, #wifi
This sounds a bit like an advert, but I have tried to avoid use of Cloudflare (mainly because of how they intercept end-to-end SSL to speed up hosted services), but like it or not, I have seen a dramatic thing happen. Since moving to a new hosting service, the webpages there which I administer, take 30 to 60 seconds usually to load. I’ve tried different DNS providers as well as using my ExpressVPN and even changing browsers, but even other webpages were sluggish, taking a good few seconds to load.
So I saw this YouTube reviewer speaking about his experience with Cloudflare WARP, and I thought, what have I got to lose by just trying it as it costs nothing. For Manjaro (Arch based) Linux, I installed the warp-cli binary from AUR, and did the three or four steps to activate it. Well just wow, the same long loading pages now jumped up in about 1 second! Yes, WARP is technically a VPN, but I would not recommend it for privacy or security, just speed (if it helps you). I still have my ExpressVPN (and there is ProtonVPN) if you want to be more sure of privacy.
This may also help me try to pinpoint why I was getting such exceptionally bad load times before, as I can see the problem was not distance, nor my ISP link, computer or browser. It is likely some DNS or configuration issue. At least it shows it is not my new hosting that I moved to, or the docker setup I’m using.
See Announcing WARP for Linux and Proxy Mode
#technology #networking #DNS #cloudflare #Linux
Starting today Cloudflare WARP is available for Linux and comes with the ability to run as a local proxy.
https://gadgeteer.co.za/cloudflare-warp-has-dramatically-sped-up-my-webpage-loading-on-linux/
but I only learned about it a few minutes ago. :-)
#internet #outage #Google #Cloud #Networking
https://www.zerohedge.com/markets/everythings-down-100s-major-websites-offline
the most fundamental networking settings are ever changing it used to be /etc/resolv.conf where nameservers are set systemd is doing it's own thing /etc/systemd/resolved.conf and Ubuntu (based on Debian) is doing (again) it's entirely own thing (netplan) frankly: this sucks X-D annoys[...]
#linux #gnu #gnulinux #opensource #administration #sysops #dns #google #debian #ubuntu #config #networking #network
Originally posted at: https://dwaves.de/2021/10/13/gnu-linux-network-config-madness-the-ever-changing-basics-how-to-try-to-set-fixed-dynamic-ip-dns-per-interface/
This is my last post on this pod. As announced, Framasphère is to be switched off this week. I remain with the same administrator, for he is very good. Thus I will continue posting on diaspora-fr.
"Tor is a fantastic networking and privacy technology that makes private and anonymous browsing available to millions. Despite this, it is unfortunately seen by some people as a system that solely exists to facilitate an illegal criminal underground,
However, to take a literal view, Tor is just a networking tool, and it can be used in any way that you want. The features that enable privacy and anonymity are also extremely useful for many of the tasks carried out by Network Engineers and Systems Administrators on a daily basis. For example:
Testing IP address based access rules
Testing internally-hosted services from an external perspective
Making reliable external DNS lookups when operating in a split-horizon DNS environment
Bypassing blocked outbound ports
Exposing services when behind NAT or CGNAT
"
https://www.jamieweb.net/blog/tor-is-a-great-sysadmin-tool/
#tor #sysadmin #networking
Manchmal braucht es Umwege: Wer zu schüchtern ist, um bei Praktika aktiv zu werden, kann einfach seinem Gefühl folgen – und kommt auch ans Ziel. #networking http://www.taz.de/Kontakten-kann-so-schoen-sein/!5788156/ #taz #tazgezwitscher #tageszeitung #Praktikum #Netzwerk
Dear #Fediverse admins, is your server #IPv6 ready? #Hetzner, one of the bigger hosting companies in #Germany, raised prices for IPv4, they also say in the future they anticipate further rising prices due to the #IPv4 shortage.
So is your service IPv6 ready?
#Networking #Friendica #Mastodon #Pleroma #Diaspora #Funkwhale #Hubzilla #Misskey #Mobilizon #Nextcloud #Peertube #Pixelfed #Plume #SocialHome #WordPress #WriteFreely #ActivityPub
TIL: wenn eine Firma "Skriptsprachen" nennt (in PR, Stellenbeschreibung, o.ä.), dann meint sie nicht bash, sondern eher "obskure Kommandozeile die wir nicht automatisiert haben" von ihrer historischen Hardware.
Oft bedeutet das ganz einfach, dass sie netmiko nicht kennen. Das abstrahiert nämlich ganz hervorragend von den Ideosynkrasien der Hersteller.
If you run a local cable or DSL modem, or router/WiFi, you should check to see if your device can run OpenWRT, or consider replacing it with one that will. Installation can be a bit of an adventure, but if you're even modestly versed with bash prompt in Linux or MacOS, you should consider it.
The project has just released its latest update (the first in about six months), mostly consisting of security updates.
https://openwrt.org/releases/18.06/notes-18.06.4
Someone had asked at Hacker News what are the benefits? My answer:
Vastly more power and flexibility, with a highly usable Web interface (LUCI) and console access.
Regular updates.
Excellent documentation: https://openwrt.org/docs/start
And a whole set of packed applications and tools. There are about 6,000 packages in total, ranging from device-specific and kernel support to advanced applications such as media servers. Link below is just the larger apps.
https://openwrt.org/docs/guide-user/services/start
Re-romming my DSL modem (500 Mhz dual-core CPU, 64 MB RAM, 8 MB Flash), as advantages over stock vendor firmware, I get:
adblock
SSH access, rather than periodically-enabled telnet
remote logging capabilities. The ability to go back to see what went wrong and when can be incredibily useful.
Performance and activity monitoring.
Consistent interface with my router (also running OpenWRT).
Full-featured shell tools rathee than barebones Busybox versions, if I like.
Remote filesystems / additional storage.
Depending on your device(s) and capabilities, your modem, router, or other hardware can serve as a home server: NAS, UuuNextCloud, Webserver, VOIP services, media server, PXEBoot (useful for testing images/deployments), guest network(s), VPN, proxy servers, email, mesh networks, messaging, captive portals, and far more.
I also run a Turris Omnia WiFi Router, also running a version of OpenWRT. That's slightly more expensive than a most stock routers, at about US$300, though it's not much off comparably specced systems, and offers advanced features, most notably that it self-updates regularly, something OpenWRT doesn't otherwise do (and virtually no OEM vendors presently support). You can also add an mSATA hard drive (up to 500 GB storage), or build out an optional NAS enclosure (2 disks), or in conjunction with an external NAS offer backups and other services to your local network, as well as provide services either privately or publicly. I'm looking at media serving and a space to stash a growing research library.
Another bit of craptacular consumer tech gets the boot.
Ever since picking up a new DSL modem a ways back I'd been wanting to get OpenWRT up and running on it. That process turned out to be ... involved. Though with a bit of path-smoothing it could have gone far better.
The major pitfalls encountered were:
OpenWRT's documentation is excellent -- far better in detail, substance, and quantity than Netgear's DM200 offerings. But as with most FOSS projects, the fact that it attempts to cover a great deal of territory means that there's possible confusion as well.
The Netgear DM200 ADSL modem is a modest, US$60 unit capable of 100 Mbps speeds -- a service ceiling I'm unfortunately at no risk of exceeding. It sports 64 MB RAM, 8 MB Flash storage, and is built on the Lantiq XWAY VRX220 SoC, with a 500 MHz dual-core MIPS 34Kc V5.6 CPU. Yeah, I've got a multiprocessor modem.... Connectivity is a 10/100 Mb RJ-45 Ethernet port and an ADSL/VDSL RJ-11 port. Power is 12V 0.5A, size is roughly an old multi-disk CD jewel box. Nothing fancy, but sufficient to task. OpenWRT supports the device well, including the ADSL/VDSL2 modem.
TL;DR: for installation onto a system already running a vendor's OEM firmware, the factory install method. This relies on the (generally) built in firmware-updating capabilities of networking kit, and is pretty sane.
The OpenWRT Netgear DM200 page will point you at the current downloads. Again, factory firmware is what you're looking for. The "sysupgrade" image is for use with systems already running OpenWRT. You're not there yet.
In the best Sorcerer's Apprentice tradition, it helps tremendously to know how to get back to the status quo ante after you've been stretching your wizardly ambitions. For most modern network kit, you can use a TFTP client to send a firmware image to the device at boot time.
This is pretty clean and no-fuss, once you have the parts and process together.
You will need:
A tftp client. I prefer command-line tools (they're scriptable), though there are GUI clients as well. Linux, OSX/MacOS, and Windows all have the BSD tftp utility available. Your distro's repos -- apt, yum, ports, Homebrew, etc., will provide this if it's not already installed.
Your vendor's OEM firmware image. You'll need to download this BEFORE you go cutting off your Internet connection, along with a few other details (like all the documentation you'll need).
The device's default IP address. For the DM200, that's 192.168.5.1, a fact Netgear's own KB misstates, just sayin'....
An Ethernet cable. This is a wired-access process.
A device that can talk to the modem. A desktop or laptop system, which can accept an Ethernet cable. Your Smartphone, tablet, or no-ports super-skinny notebook computer may not cut it.
Note that this is client-side stuff -- you don't need to get fancy-pants with TFTP daemons, BOOTP, DHCP servers, or any of that jazz.
I wrote a brief script to manage the process of bringing down my network connection, bringing it back up, then sending over the files:
sudo ifconfig eth0 down
sudo ifconfig eth0 192.168.5.10 netmask 255.255.255.0 up
/sbin/ifconfig # to verify settings
tftp 192.168.5.1 <<EOF
verbose
binary
#trace
status
put DM200-V1.0.0.61.img
status
quit
EOF
(Mac users will probably use en0 rather than eth0 for their network device.)
You should see the put command, and then the bytes transferred and seconds elapsed (~30s or so). A timeout means tftp couldn't find the modem.
If things aren't working as intended, you can try uncommenting the "trace" line for additional debugging info.
The modem will take a few minutes (generally ~4) to receive, load, and boot the new image. When it does so, the power LED will shine constant green, and you should be able to down and up your interface, this time under DHCP, to talk to the modem again:
sudo ifconfig eth0 down
sudo dhclient eth0
I don't have NetworkManager (a/k/a NetworkMangler) running on this system, you may need to shut that down to regain full control of your senses network, on systemd afflicted based Linux systems.
A saved OEM system configuration will allow you to restore settings from the backup, so that's another good preparatory step.
As noted, the key item for PPoE configuration was setting the MTU to 1492 rather than 1500. Ideally, OpenWRT would take care of this itself, but presently it does not.
After the first failure at getting DSL configured, in which I did not have much of the OpenWRT documentation locally accessible, I opened up multiple pages in browser tabs, and saved several as PDF or HTML format. The fact that OpenWRT doesn't have a single PDF- or ePub-formatted documentation set to download is actually slightly annoying. I've been exploring various web-based archival tools, and might try to mirror the site (or similar projects) using tools such as HTTrack or wget in future.
End result: some pain, some lessons learned, and a working system.
So what does this buy me?
I'd had a few frustrations with the stock Netgear OEM image.
Out of the box, OpenWRT gives regular updates, SSH, remote syslogging, a vastly better designed and more responsive Web interface, and a less that handles arbitrarily-sized terminals. I'm exploring other packages and built-in features as well. The limited size and power of the modem suggest keeping aspirations limited, but having options is useful.
The other issue has been occasional service issues -- some local/internal wiring, some ISP-related. Having a more powerful, flexible, and shell-addressable (via SSH) set of tools may be useful with these if (!) they occur in future.
And -- with a Turris Omnia router, I've got another OpenWRT-based device and standardising on the toolset seems useful. The Omnia is far more powerful and has much more memory (2 GB) and storage (8 GB), the latter of which is further expandable with either internal or external storage. A nice set-up, actually.
So I'll be looking into the options and opportunities here for a while.
But if you're running the DM200 or similar kit and would prefer a Real Operating System on it, well, here's a quarter.
#linux #gnulinux #gnu @trisquel #ubuntu #shield #nvidia #networking #mount
I was not able to WRITE to my external hard drives that are connected to my NVIDIA SHIELD TV from my Linux Mint notebook over my network.
I would get a "dropped connection" error. With the release and improvement of Trisquel in version 8.0, i decided to give it a shot.
I was able to write to the drives connect to the NVIDIA SHIELD. I am not however able to download torrents directly to them. When I try to set the download location in Transmission, the NVIDIA shield does not appear in the "Computer" section.
Interesting to note that Linux Mint would not even write to them in the file explorer but Trisquel had no problem.
Trisquel is FLOSS and contains not even binar blobs of proprietary code in the linux kernel and is often criticized for lack of multimedia support and extra features that are only available with proprietary software.....so its very nice to see it working better out of the box than linux mint!!!
If anyone could help me with this, it would be very much appreciated.
Crypto reward for anyone who can successfully help.
Thank you.
What if any options are there for running Federated social networking tools on or through #OpenWRT or related router systems on a single-user or household basis?
I'm trying to coordinate and gather information for #googleplus (and other) users looking to migrate to Fediverse platforms, and I'm aware that OpenWRT, #Turris (I have a #TurrisOmnia), and several other router platforms can run services, mostly #NextCloud that I'm aware.
Is #diaspora itself viable on these systems? I'm thinking that may be ambitious.
If not, what are considerations for running a small node through a router? Primary considerations would be capacity planning, bandwidth and load impacts, and configuration and security considerations.
Hoping there's some expertise here.