ethaniel

HOWTO: Receive SMS via 4G/LTE Huawei stick on Raspberry Pi 4 and forward them via Telegram

I live abroad and have only 1 sim card slot in my phone. It holds the SIM card of the country that I am in right now. But I also have another SIM card from my home country which receives my banking SMS codes. I can't afford to lose the "home" SIM card, so I decided to keep it in my house and forward the SMS messages to my main phone and computer via Telegram (just like Whatsapp, but so much better).

I also made a choice to use a 4G/LTE stick instead of 3G, because the 3G signal in my area is getting worse in worse due to operators upgrading their equipment.

Prerequisites

1. Raspberry Pi 4
2. Huawei E8372 (but can be any similar)

Step 1 - Get the Huawei card to work properly with Raspberry

ethaniel

/*

Step 1. Go to Youtube Studio.
Step 2. Open your playlist (URL looks like: https://studio.youtube.com/playlist/ID/videos)
Step 3. Run the following command in your chrome console.

*/

async function clickAllRemoveButtons(delay = 1000) {
  let buttons;

ethaniel

// Copy-paste this into your browser's console.
// WARNING: This will delete ALL DNS RECORDS that are visible on the current page one by one.
// It might take 5-10 seconds to delete one DNS record.
// Based on https://community.cloudflare.com/t/useful-script-to-bulk-delete-all-incorrectly-imported-dns-records/131144
// Valid for 11 January 2024. Might need to be redone later.

(() => {
    const deleteTopRecord = () => {

        if (document.querySelector('[data-testid="dns-delete-modal-confirm-button"]')) {

ethaniel

Why

I've noticed RX packet drops on my PCI card (InDroppedDma was too high). I suspected that it was because of a firmware problem, so I decided to try to find a way to update it.

There was no official linux firmware updater, however I found an unofficial one published some time ago, which worked well when combined with the latest firmware.

Use at your own risk, however I didn't experience any problems.

Explanation:

ethaniel

1. Get RTSP video, decode it, apply framerate and send to shared buffer. Don't forget to set shm-size to something high, because you're now dealing with decoded raw video:

gst-launch-1.0 -v rtspsrc location="rtsp://192.168.86.249/live/sala" protocols=tcp latency=1000 ! watchdog timeout=10000 ! rtph264depay ! h264parse ! avdec_h264 ! videorate ! video/x-raw,framerate=30/1 ! shmsink wait-for-connection=false socket-path=/tmp/foo shm-size=100000000

2. Note the caps in the output:

/GstPipeline:pipeline0/GstShmSink:shmsink0.GstPad:sink: caps = video/x-raw, format=(string)I420, width=(int)2560, height=(int)1440, interlace-mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1, chroma-site=(string)mpeg2, colorimetry=(string)1:0:0:0, framerate=(fraction)30/1

3. Read decoded video from shared buffer (input the width,height,format,framerate caps from above):

ethaniel

<?php

/*

Script to always have 1 deep scrub running per OSD.

## About

1. Helps with the following error: PG_NOT_DEEP_SCRUBBED HEALTH_WARN (N pgs not deep-scrubbed in time) 
2. Doesn't run scrubbing on PGs that were deep scrubbed less than 2 weeks ago, releasing

ethaniel

#!/usr/bin/env bash
#
# delete_oldest_until_threshold.sh
#
# Repeatedly deletes the oldest file in a folder until
# disk usage is below a specified threshold.
#
# Usage:
#   ./delete_oldest_until_threshold.sh -p /path/to/folder [-t threshold_in_percentage]
#

ethaniel

I needed to batch update the monitor and stop timeouts in all of my pacemaker resources. I didn't want to rely on the default values, so I wrote this oneliner:

pcs resource | awk '{print $2}' | while read RESOURCE; do pcs resource update $RESOURCE op start timeout=20s op stop timeout=200s op monitor interval=10s timeout=200s; done

ethaniel

Intro

I live in Thailand. Sometimes my internet connection is slow, because my ISP has poor international connectivity with some destinations (Europe, for instance). Sometimes routes that the ISP chooses have a lot of packet losses, or just slow. I needed a way to route SOME of the devices on my LAN another way. I decided to use NordVPN because they have a lot of servers worldwide and my ISP provides a reliable route to SOME of them (I use docker run -it trishmapow/nordvpn-tools FR --load 30 --fping | awk '{ print $NF,$0 }' | sort -k1,1 -n | cut -f2- -d' ' | head -n 10 to find the best servers with the lowest ping for instance). However, I didn't want to deal with installing a VPN client on every device, so I decided to make one inside my Raspberry (but without having the Raspberry use the VPN connection itself, because I have other services running on it).

You will need

1. Raspberry Pi wired by LAN cable
2. Through raspi-config go to Advanced options - Network Interface Names - choose No to

ethaniel

If you don't want this, then enable ONVIF on every camera in the settings (add a new ONVIF user with the privilege "Media operator"), and then change the protocol to ONVIF on the NVR side.