F8 20A fuse blown on Ford Mondeo MK4 2L TDCI

Car stalled at the middle of the road. F8 20A fuse blown. Crappy Ford's user manual says: Powertrain control module. Brief and straight to the point.

After diagnosis it turned out the problem is on ECU Delphi DCM3.5 black connector line. Brown and grey connectors are OK. Test was very simple - 12V 40W lamp connected to F8 fuse contacts. When car door is opened, car activated and lamp glows, when door is shut, after a while PCM relay turns off the lamp. Something shorts F8 line when car is active. If you try ignition to crank car, lamp or fuse will burn. 

Looks like sophisticated electrical problem? Almost all connectors were checked but lamp glows. Finally air filter was removed, headlight was removed and broken wires were found. Modern engineering at it's best. Weak protection against rubbing and stupid location. Looks like one wire broke, shorted and burned few other wires. Here is the lesson: do not mess with electronics before checking physical lines.

Very fortunate that this damage happened on low speed in the city. On highway such thing may be lethal.  Overall Mondeo 4 is good car but engineering decisions on horn and ECU location, shitty wire isolation, absence of mechanical lock on passenger door, non-serviceable diodes in tail lights are annoying. Ave enshittification, morituri te salutant.

KNKA CS06 dehumidifier disassemble and repair

3 screws at the bottom. 4 screws behind water tray. Pull case bottom gently, remove top cover and unscrew 2 screws under it.

Privacy, telemetry, data collection

https://librewolf.net/

LibreWolf — privacy enhanced Firefox gets much better results on https://coveryourtracks.eff.org

sudo apt update && sudo apt install extrepo -y

sudo extrepo enable librewolf && sudo extrepo update librewolf

sudo apt update && sudo apt install librewolf -y

Any program that uses web UI via web-server may leak internal LAN IP-address of the device, for example IP Webcam for Android does this in Referrer. F12 > Dev Tools > Network > check what requests app makes. Any API is potential channel for leaking user data. Be cautions when using proprietary apps in sensitive environment. FOSS is better in such cases, else decompile, modify, rebuild.

https://www.privoxy.org/user-manual/quickstart.html

https://docs.searxng.org/

sudo ufw enable

sudo apt install tor

torsocks --version

sudo systemctl enable tor      // start on boot

sudo systemctl start tor          // start now

sudo systemctl status tor       // check if running

torsocks curl https://check.torproject.org

CLI browsers are not safe browsers. Using w3m/lynx to “avoid JS” doesn’t make sense for anonymity; you’re trading usability and security for terminal UI. CLI inside a Tor-based system is safe way: Whonix, Tails (easiest).

Ordinary goofy will say that he has nothing to hide, but he do not take into account regime change, idiotic laws and limitations that may be in future... The less data you share, the better. Nobody has right to poke nose in your LAN, hardware, behavior, business...

KTorrent not seeding and not downloading

Forward only 6881 for tcp and udp in router or choose another port. Paste it for TCP, mtp, DHT, apply and other ports will be changed automatically.

sudo ufw enable

sudo ufw allow 6881/tcp

sudo ufw allow 6881/udp

sudo ufw reload

netstat -plunt | grep ktorrent

tcp        0      0 PC_IP:6881              0.0.0.0:*       LISTEN       60908/ktorrent

udp        0      0 PC_IP:6881             0.0.0.0:*                           60908/ktorrent

udp        0      0 PC_IP:UDPtrackers 0.0.0.0:*                           60908/ktorrent

udp        0      0 PC_IP:UDP_DHT    0.0.0.0:*                           60908/ktorrent

Shrink disk size partition in terminal with parted resize

The Victory Lap: 851GB shrinked drive (Stable), 323GB 4256-sector slop (Webcam Trash), screaming shrinked 978GB 2005-sector zombie (Torrent Sacrifice). Successfully built "Post-Apocalyptic" Storage Array out of pure e-waste. It's chatty, it spams errors - but it's moving 110MB/s and cost $0.

KGet download and upload limit not working

nano ~/.bashrc

alias slowget='aria2c -c -x 16 -s 16 --file-allocation=prealloc --max-download-limit=1024K -o'

source ~/.bashrc

cd /desired/folder

slowget "file_0.avi" "URL"

If download fails:

slowget "file_0.avi" "NEW_URL" // to resume

Alternatives for using KGet:

E: Package 'trickle' has no installation candidate

sudo apt install firejail // 28.5 MB

firejail --net=eth0 --bandwidth=kget:1500:1500 kget

sudo wondershaper eth0 1500 1500 // NIC limit

GA-970A-DS3P FX wake on lan not working on Lubuntu

Looks like WOL is Enabled by default, if Erp Disabled, and MB is made solely for Windows, where WOL is enabled in driver. Enabled Power On By Mouse, Power On By Keyboard just in case... No lights on LAN port but 2.5W power draw... If CPU Turbo mode is enabled, 3.5W power draw...

https://www.gigabyte.com/Motherboard/GA-970A-DS3P-FX-rev-21

Windows 8 Features > Other OS

CSM Support > Never

Boot Mode Selection > UEFI and Legacy

LAN PXE Boot Option ROM > Disabled

Storage Boot Option Control > Disabled

Network stack > Disabled

IOMMU Controller > Enabled

ON REMOTE/TARGER/HOST/SERVER PC:

sudo nano /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

GRUB_CMDLINE_LINUX_DEFAULT=""

sudo update-grub

sudo apt install openssh-server -y

sudo systemctl enable --now ssh

ip link

sudo ethtool enp3s0 | grep Wake

        Supports Wake-on: pumbg

        Wake-on: d

sudo ethtool -s enp3s0 wol g

sudo ethtool enp3s0 | grep Wake

        Supports Wake-on: pumbg

        Wake-on: g

BUT IF sudo reboot > Wake-on: d > sudo poweroff > Wake-on: d

nmcli connection show

sudo nmcli connection modify "Wired connection 1" 802-3-ethernet.wake-on-lan magic

sudo nmcli connection down "Wired connection 1" && sudo nmcli connection up "Wired connection 1"

Alternatives:

Option A — NetworkManager

Create a dispatcher script:

sudo nano /etc/NetworkManager/dispatcher.d/99-wol

Put:

#!/bin/sh

ethtool -s eth0 wol g

Make executable:

sudo chmod +x /etc/NetworkManager/dispatcher.d/99-wol

Reboot and check:

ethtool eth0 | grep Wake

Option B — systemd service

sudo nano /etc/systemd/system/wol.service

[Unit]

Description=Enable Wake-on-LAN

[Service]

Type=oneshot

ExecStart=/usr/sbin/ethtool -s eth0 wol g

[Install]

WantedBy=multi-user.target

sudo systemctl enable wol.service

ON CLIENT PC:

sudo apt install wakeonlan

wakeonlan [MAC_ADDRESS]