Juul

   OpenRC 0.42.1.788529e388 is starting up Linux 5.8.0-kindle4+nt-12013-g4ccf5377d7ae-dirty (armv7l)

 * /proc is already mounted
 * Mounting /run ... * /run/openrc: creating directory
 * /run/lock: creating directory
 * /run/lock: correcting owner
 * Caching service dependencies ... [ ok ]
 * Clock skew detected with `(null)'
 * Adjusting mtime of `/run/openrc/deptree' to Fri Mar 26 07:58:52 2021

Juul

Install wireguard

To install wireguard do:

opkg update
opkg install kmod-wireguard wireguard-tools

Juul

To /etc/config/firewall add:

config rule                                     
        option name             Allow-SSH-WAN   
        option src              wan             
        option proto            tcp             
        option dest_port        22              
 option target ACCEPT 

Juul

First ensure your ethernet isn't managed by network-manager by adding the following to `/etc/NetworkManager/NetworkManager.conf`:

```
[keyfile]
unmanaged-devices=mac:00:11:22:33:44
```

Replacing the MAC address with that of your ethernet device. 

Then run:

Juul

git pull <papazoga repo>
cd qemu/
git checkout ni-mite

git add remote upstream https://github.com/qemu/qemu

git fetch origin upstream (?)

Juul

Xiaomi Mi WiFi R3Gv2

Also known as "R4A Gigabit". On the back it just says "R4A" but plugging into ethernet can verify that it's the gigabit edition.

Click through initial setup wizard in chinese accepting defaults. When asked for a wifi password know that this will also be the admin password. If connected through wifi you will be disconnected at the end of the wizard since the wifi now has a password. Reconnect and go to the web admin again. Type in the wifi pass in the text box and once you're logged in the stok will be in the address bar.

The latest OpenWRTInvasion repo has both stock firmware and working openwrt images. The stock firmware version from the repo miwifi_r4a_firmware_72d65_2.28.62.bin works fine.

Don't use the latest version of OpenWRTInvasion. It does not seem to work. Instead use the v0.0.1 version.

Juul

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQGNBF7LOWQBDACv1M8bZUiiEFKJ0ITmVyKH3U1ixKnJ2HV2KzPlSMnlV8doyfYx
ydv0Udu7WSeAfIpk9nMrwlzIqRSJx0sOsO0ZpiVdo+loKehBjoQiCiBzwmt0UOHL
/knFEwBC1Sh33D+GfjUG+8cVZgEwx0ySt/w8boGS86384AQtwZ8CS2AGgIMZO7ld
XPIIUr2uHPvZzT8We4+VhqBRwHKmIwDnPkJBs1LtLuRbgmPu3yJBSe38J6J6X4au
53bNKdE7kQmqzraawFJjVb14/fU6UoqBMkwOiTQ/1N/0JVUr+DOUTSI74RwnGPr8
6qbQYbEY5SRDCsOAy9FhoEjf75nCTNQ+GQNa5Vih9tpVrEqikPRN+eouTD5YfnJv
QcxJI8RORHsTCSGNGC8OmX+GM5NPS0jRwixeoGWEJBLIKjEP9HpIOLWYR3RNWTGe
IwtJdWxXPYo8uDR4GAnTaTRbu5NTyQe65hORl7gZsrtALjojXmCZTyWlmuYRGHn/

Juul

This is a brief guide on how to configure an SSH reverse tunnel that automatically establishes on boot and will continuously attempt to re-connect when it fails.

It is very useful if you are deploying a device somewhere without a public IP, e.g. behind a NAT, and need to be able to SSH into it from the wider internet.

Let's refer to the NAT'ed device as the client. This guide assumes that the client is able to create outgoing SSH connections to at least destination port 443.

You will need root access to a server with a static IP on the internet which runs an openssh server.

On my-server.example.com add the following to /etc/ssh/sshd_config, changing tunnel-user to whichever username you want to use (this will be a new user, not an exising user) and changing the PermitOpen line:

Juul

Check which version of chocolate-doom your distro has:

apt-cache show chocolate-doom|grep "Version:"

If it's version 3.0.0 or above then install it:

sudo apt install chocolate-doom

Juul

#!/bin/bash

# Show total memory usage of all processes matching the supplied grep arguments

if [ "$#" -lt "1" ]; then
  echo "Usage: $0 <grep arguments>" >&2
  exit 1
fi

function humanize() {