OpenWRT can be installed on physical machine, virtual machines, also docker environment. This post summarizes some steps how to get OpenWRT running into your docker environment. 

Topology

Create macvlan Network

Create macvlan configuration :

Create macvlan network:

Command line:

docker network create -d macvlan --subnet=192.168.2.0/24 --gateway=192.168.2.1 -o parent=wlan0 macnet

Check the network created for Docker environment:

root@ubuntu:/etc# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
0f5799ba3db3        bridge              bridge              local
ad41a2fa3a8a        host                host                local
af9991f302ea        macnet              macvlan             local
7a6c6991d92b        macvlan             null                local
74f1375fb8c1        none                null                local

Pull Image and Create Container

From Portainer:

Other configuration :

network - choose macnet

Restart policy - Never (for testing)

Runtime & Resources - Privileged mode enable

If you had an already running container that you wanted to change the restart policy for, you could use the docker update command to change that:

docker update --restart unless-stopped container_id

docker pull sulinggg/openwrt:latest
docker run --restart always --name openwrt -d --network macnet --privileged sulinggg/openwrt:latest /sbin/init

After deployed the dock, check the ip address allocated from network macnet. You will need to manually set this ip into docker's /etc/config/network file. 

bash-5.0# cd /etc/config
bash-5.0# nano network 
bash-5.0# cat network

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd7d:334c:6108::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0'
        option proto 'static'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option ipaddr '192.168.2.96'
        option gateway '192.168.2.1'
        option dns '8.8.8.8'

config interface 'vpn0'
        option ifname 'tun0'
        option proto 'none'

bash-5.0# 

Now you should be able to access your OpenWRT web gui from http://192.168.2.96

Note：

Ubuntu has systemd-resolved listening on port 53 by default. In case you want to run your own DNS server, you can't because port 53 is already in use, so you'll get an error similar to this: "listen tcp 0.0.0.0:53: bind: address already in use".

You have systemd-resolved enabled as the local DNS server. You can disable it by setting DNSStubListener=no in /etc/systemd/resolved.conf and then restart the systemd-resolved service. It will then start without binding to port 53, allowing dnsmasq to bind instead.


[Resolve] DNS=1.1.1.1 #FallbackDNS= #Domains= #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=no DNSStubListener=no #ReadEtcHosts=yes

This post is to collect some of packages using on my OpenWRT router. The list is still adding. Once more packages tested and used, they will be added in this post for future reference. 

Terminal integration in LUCI: luci-app-ttyd

This package intigrates ttyd in LUCI. Two packages to install, ttyd and luci-app-ttyd. 

luci-theme-argon

You will have to use TTYD to do installation. 

For openwrt official 19.07 Snapshots LuCI master

opkg install luci-compat
wget --no-check-certificate https://github.com/jerrykuku/luci-theme-argon/releases/download/v2.2.5/luci-theme-argon_2.2.5-20200914_all.ipk
opkg install luci-theme-argon*.ipk

DNS based ad/abuse domain blocking - Adblock

My home network is a flat network, one ISP Wireless Router connecting to a modem for Internet connection. Internally, a switch is connecting to this wireless router to provide more LAN ports for internal devices. 

The wireless router was provided by ISP. Performance and coverage is ok for my home. But since it is ISP router, lots of settings have been locked down or customized, I wont be able to do much. Since I am also lazy to make big change to my home network, I found OpenWRT can be used as a single arm router for my home network to make me have better control to the network traffic. Only thing you will need to do is to spin up a virtual machine and install OpenWRT in it. Of course, you might need to change the DHCP settings to let your clients to send traffic to OpenWRT rather than directly to Wireless router. 

Topology

Before

After:

Download OpenWRT OVA 

You can find out the OVA link from https://ift.tt/3o9nAJU if you do not want to convert it from image. 

Here is directly downloading link. The file size is only 18MB. 

Installation Steps

Double click the download file (OpenWRT_x86_64_19.07.05.ova) will trigger VMWare Workstation Import Virtual Machine wizard:

Follow the wizard to get it imported. After imported, you can edit the configuration to change Memory or processors. One thing you wont be able to change is Hard Disk (IDE) size, which is only 256MB. There is only way to DD this 256MB hard drive to another one. But it will be on different post to discuss. 

After VM started, that is how it looks like:

By default, it will use dhcp, but you might want to change it to static ip.

• Login via SSH
• Edit /etc/config/network directly
• Run /etc/init.d/network restart
• Done!

After that, you can use browser to access OpenWRT Luci Web UI:

By default it is using Luci bootstrap theme. You might want to try another theme by installing it from software window. I am using luci-theme-material theme here. 

Client IPv4 Setting Change

It also can be observed the route change from tracert command. 192.168.2.4 becomes the first hop for the test machine.

C:\Users\test>tracert www.google.ca

Tracing route to www.google.ca [172.217.164.227]
over a maximum of 30 hops:

  1     9 ms     3 ms     7 ms  OpenWrt.lan [192.168.2.4]
  2     6 ms     4 ms     5 ms  PORTAL-FDF4 [192.168.2.1]
  3    20 ms    17 ms    21 ms  160.32.196.33
  4     *       17 ms    17 ms  104.171.62.122
  5  3727 ms     *        *     204.197.190.245
  6    19 ms    18 ms    18 ms  135.0.199.97
  7    22 ms    19 ms    19 ms  72.14.203.42
  8    18 ms    23 ms    18 ms  74.125.244.161
  9    18 ms    17 ms    19 ms  216.239.42.61
 10    24 ms    20 ms    17 ms  yyz12s05-in-f3.1e100.net [172.217.164.227]

Trace complete.

References

• OpenWrt on VMware HowTo

 Adblock software in OpenWRT is a script running in your OpenWRT gateway to sort out those DNS queries that ask for the resources recrds of ad servers and return a simple 'NSDOMAIN'. This action will make your browser not able to show those ads on the page you are surfing. 

Topology

Prerequisites

• OpenWrt, tested with the stable release series (19.07.x) and with the latest rolling snapshot releases. On turris devices it has been successfully tested with TurrisOS 5.1.x
• A download utility with SSL support: 'wget', 'uclient-fetch' with one of the 'libustream-*' ssl libraries, 'aria2c' or 'curl' is required
• Option: DNS Reporting, TCPDUMP or TCPDUMP-Mini installed
• Client DNS pointing to OpenWRT

Installation Steps

From OpenWRT Luci Web GUI:

• Click Update Lists from OpenWRT Web GUI - System - Software

• Install adblock and luci-app-adblock
• Install wget / Curl 
• Reboot OpenWRT
• Browse to OpenWRT Web GUI - Services - Adblock

From Console or SSH Session:

• Update your local opkg repository (opkg update)
• Install 'adblock' (opkg install adblock). The adblock service is enabled by default
• Install the LuCI companion package 'luci-app-adblock' (opkg install luci-app-adblock)
• It's strongly recommended to use the LuCI frontend to easily configure all aspects of adblock, the application is located in LuCI under the 'Services' menu
• Update from a former adblock version is easy. During the update a backup is made of the old configuration '/etc/config/adblock-backup' and replaced by the new config - that's all

References

• OpenWRT Wiki - Ad blocking
• DNS based ad/abuse domain blocking