Installation and configuration notes
(Very thin documentation on the CM4 baseboard used, nothing about the USB3 network port, but some info on the RTC, fan control and display and camera interfaces)
Internet of Things – a techie’s viewpoint
(I used mainly the beginning of chapter 36 for the first good enough solution I found on how to switch the interfaces so that eth0 will be used for WAN and eth1 for LAN)
Get the latest (stable) version of OpenWrt (I use “Factory (EXT4)”), write it to a MicroSD-card the usual way, insert into slot on CM4 board and boot up.
Note: Before booting the SD-card, you might want to resize the Linux partition and file system on it. Do this with another Linux-based system:
Insert the SD-card into a reader/card slot and check end of ‘dmesg’ output which device was assigned the card:
root@DS1517:~# dmesg |tail [13376.702534] sd 10:0:0:1: [sdr] 61849600 512-byte logical blocks: (31.6 GB/29.4 GiB) [13376.714483] sdr: sdr1 sdr2
In this case (on my Synology NAS), the card readers’ slot was assigned ‘sdr’.
Resize the partition with ‘parted’:
root@DS1517:~# parted /dev/sdr GNU Parted 3.2 Using /dev/sdr Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p p Model: TS-RDF8 SD Transcend (scsi) Disk /dev/sdr: 31.7GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 4194kB 71.3MB 67.1MB primary boot, lba 2 75.5MB 173MB 104MB primary (parted) resizepart 2 -1 ... (parted) q
Resize the file system with ‘resize2fs /dev/sdr2’
The default is to use eth0 for LAN, which I didn’t like (with the possibility that the other USB3-based interface might be less stable, and is using kernel drivers for the incorrect model).
To fix this I used the guide mentioned above, the beginning of chapter 36, with some modifications to fit my network.
(section 36.4 in IoT guide)
The later distributions of OpenWrt starts up as logged in as root on the console, which makes it easier to do the initial adjustments to the network settings. As the guide mentions, if your home network is on the 192.168.1.0/24 subnet, you can access the shell by SSH (root without password) to do the modifications.
Change the lan section of /etc/config/network to:
config interface 'lan' option ifname 'eth0' option proto 'dhcp'
Reboot the Pi, and you will get IP by DHCP (handed out by your old router). Either find that IP in the old router or just do a “ifconfig” command on the console.
Installing the kernel module for the USB3 network port
(section 36.5 in IoT guide)
To get the second network port working, you need to install the correct kernel module for the chipset it is using. In the case of the CM4 base board, the chip is rtl8153. Unfortenately there is no exact match or that chip (yet/ever ?), but rtl8152 will work fine. Use ‘opkg’ to install the module:
opkg update opkg install usbutils opkg install kmod-usb-net-rtl8152
For further configuration, I also add a more user-friendly text editor than ‘vi’:
opkg install nano
Verify by ‘ifconfig eth1’ that the second network adapter shows up.
Switching the eth0 / eth1 interfaces to have eth0 for WAN
Now that we have both interfaces visible, we can switch their usage as described in the IoT guide. For my network (LAN side) I use a network mask of /16, so I cannot be on that same IP range for the network on the inside of the CM4 router.
For the inside, I choose (from the private IP-series) 172.16.3.0/24, and will give my CM4 router the IP address 172.16.3.1.
Change the old ‘lan’ section to ‘wan’ and add a new “lan” section in /etc/config/network:
config interface 'wan' option ifname 'eth0' option proto 'dhcp' config interface 'lan' option proto 'static' option ifname 'eth1' option ipaddr '172.16.3.254' option netmask '255.255.255.0' option gateway '192.168.1.254' option type 'bridge'
(I don’t think the “gateway” config is needed in ‘lan’, but have to check that)
Configure DHCP on the LAN interface
Add a “dhcp” section for eth1 in /etc/config/dhcp:
config dhcp 'eth1' option start '100' option leasetime '12h' option limit '150' option interface 'eth1'
Reboot the CM4 router, connect your uplink cable to eth0 and a computer to eth1. When the CM4 router has started, and if everything works well, and the computer should get an IP address on the 172.16.3 network (in the range from .100 to .250).
LuCI confusion by manual configuration
Access the web interface on http://172.16.3.254, set a password for the web interface.
When you first access the web interface for your manually configured CM4 router, LuCI will ask to update the configuration to the new format (for using ‘br-lan’ instead of “option type ‘bridge'”) and using the ‘br-lan’ device instead of the manually entered ‘ifname’ in the lan section. Allow these changes, and the GUI is ready for use.
The first step is to go to System/Software in the menu and click the “Update lists” button to refresh/create the list of available plugins for OpenWrt. Then use the many OpenWrt guides online for additional configuration ideas.
If you during setup have your CM4 router behind another router on the local network, change the firewall setting for WAN to allow inbound access (unless you’re happy with accessing it from a computer on that routers’ LAN interface).
You find that setting under “Network/Firewall”:
You can after this change access the web interface and SSH over the WAN side IP. Do not forget to change back if this router is put on a public network!
That’s it for the basics and getting started with OpenWrt on a Pi4 with dual ethernet interfaces (either with the used CM4 baseboard or a separate USB3 dongle). I have probably missed some of my steps as this guide was written some time after I completed the setup.
Add and configure (accept default settings) the package named ‘luci-app-statistics’ to get graphs for CPU usage and network traffic.
Add the module ‘collectd-mod-thermal’ to get graph for CPU temperature.
Ivacy VPN settings
Get the OpenVPN-Configs.zip file from here:
or (any of the non-Mac and non-Windows files) here:
Follow the guide
Ivacy-VPN related content in /etc/config/openvpn (as created by LuCI)
For easier configuration, skip the steps in the guide which explains how to configure the VPN connection using LuCI, just add the connection and then hit “Save & Apply” on the basic settings page, then edit the /etc/config/openvpn file directly:
config openvpn 'Ivacy' option dev 'tun' option nobind '1' option comp_lzo 'yes' option verb '1' option persist_tun '1' option client '1' option auth_user_pass '/etc/openvpn/userpass.txt' option resolv_retry 'infinite' option auth 'SHA1' option cipher 'AES-256-CBC' option mute_replay_warnings '1' option tls_client '1' option ca '/etc/openvpn/ca.crt' option tls_auth '/etc/openvpn/tls-auth.key' option auth_nocache '1' option remote_cert_tls 'server' option key_direction '1' option proto 'udp' option port '53' list remote 'usny2-ovpn-udp.dns2use.com' option enabled '1'