NanoPi R4S-RK3399 is a great new OpenWrt device

There is only one patch needed for 1GB, there is no reason not to use it? Why wouldn't we want full support for all versions?

I didn't mean that, i mean that we should not keep the 4gb version out of stable just cause no body will PR the patchs needed to make the 1GB work properly.

I am not against openwrt having support for the 1GB version, but i am against not giving the stable release of openwrt to the 4GB version(when that one is fully working already) just cause the 1GB is not working yet.

The r4s will be part of the next major stable release (22.xy.0) just naturally, as being part of master now, before it branches off. Chances for this device (regardless of 1 GB RAM or 4 GB RAM variants) to 21.02.x are unlikely at best, given the required kernel config additions and feature selects strictly speaking against the backporting rules for stable releases to begin with. Perhaps you can still convince an OpenWrt developer, but chances are low.

2 Likes

Guys, which Dockers are you running on the R4S? I'd appreciate ideas to put mine to a better use than just routing (Name + What it does). Thanks in advance!

ghcr.io/linuxserver/unifi-controller to handle my wifi.

i could move my AAR stack from my pi but i prefer my plex, AAR stack to be moveable.

ghcr.io/linuxserver/plex - Plex Media server
ghcr.io/linuxserver/radarr - Movie indexer
ghcr.io/linuxserver/sonarr - TV series indexer
ghcr.io/linuxserver/lidarr - Music indexer

https://wiki.servarr.com/

2 Likes

ghcr.io/zoneminder-containers/zoneminder-base:1.36.12 - Zoneminder: security camera motion detection + recording
lscr.io/linuxserver/unifi-controller:latest - Unifi Controller to manage unifi access points

Both are limited to cpus 4-5.

1 Like

Hello,

How do you create your openwrt firmware ?
I tried the snapshot from february 4th but I needed to replace firewall4 to firewall to have banIP & docker working. And I tried lscr.io/linuxserver/unifi-controller:latest but the container didn't start.

Do you know what I missed ?
Thank you

There are build instructions on the wiki. Or you can try one of the builds I posted earlier in this thread, they include docker and banip but not firewall4.

I am using the following docker-compose.yml to install and run the Unifi Controller. You could start with this and customize as needed.

version: "2.1"
services:
  unifi-controller:
    image: lscr.io/linuxserver/unifi-controller
    container_name: unifi-controller
    cpuset: 4-5
    mem_limit: '1024M'
    environment:
      - PUID=998
      - PGID=998
    volumes:
      - /mnt/docker-unifi/unifi:/config
    ports:
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080
      - 8443:8443
#      - 1900:1900/udp #optional
      - 8843:8843 #optional
      - 8880:8880 #optional
      - 6789:6789 #optional
      - 5514:5514/udp #optional
    restart: always

You can compile it yourself or use the image builder or the web version of the image builder:

https://asu.aparcar.org/

You can change the packages here:

But i am pretty sure that you need to compile openwrt yourself to revert the changes from firewall to firewall4(https://github.com/openwrt/openwrt/commit/08d9f6e3020b4a149b2007b6ed7d684c49af9bbf), or you can try just changing the packages to see what happens or someone else can have a better insight into this question.

But its better to just use this build: https://github.com/anaelorlinski/OpenWrt-NanoPi-R2S-R4S-Builds

Its stable openwrt instead of snapshots, just wait until the next major version of openwrt so we get the oficial stable version so you can invest your time into learning how to compile it yourself thats what noob me will do :smiley:

Should be enough just to change "firewall4" in the customize field to "firewall" and then add docker, docker-compose, dockerd, luci-app-dockerman, banip, luci-app-banip, and whatever else is needed. For docker you may also want shadow-utils for managing user accounts and block-mount for mounting USB storage.

1 Like

https://github.com/anaelorlinski/OpenWrt-NanoPi-R2S-R4S-Builds include docker. and i think are firewall not firewall4 (i'm still running the xmas build not his more recent jan build.)

Yes, it includes docker and firewall instead of firewall4 cause its stable openwrt and not snapshot.

My ISP requires VLAN tagging on the WAN port.
Is the VLAN issue a hardware limitation or could this potentially be addressed with an updated driver/patch? Or is it possible to choose which port is LAN/WAN and use the interface that does support VLAN?

What do you mean by VLAN issue? Have you tried to set it up?
LAN/WAN can be switched. Just replace eth1 with eth0 and eth0 with eth1 in network config.

hi,

I experienced the same issue, I think it's described in one of my previous messages in this thread.

VLAN is not handled by the nic attached to original wan: the interface must be set in promiscuous mode or else no vlan tagged packet are seen.

Two alternatives I didn't tested so far (but I will someday when I'll reuse back my r4s as wan router)

  1. either switch the use you do of wan and lan ports of r4s, as you explained (it's just names)

  2. or use a managed switch able to tag/untag vlan trafic between your wan input and the r4s

Also I had an issue too with the in-ability of the wan port to set a larger MTU value (my config for french ISP called 'Free': 1) all vlan tagged packets + 2) ipv4 packets are encapsulated in IPv6 packets that need higher mtu set).

More info for french guys here: https://lafibre.info/materiel-informatique/degager-la-freebox-serveur-routeur-wifi-firewall-que-me-conseillez-vous/msg795377/#msg795377

There must be some driver issue, because this device seems to support VLAN on RK3399 internal NIC

As a workaround you can also use USB3.0 NIC.

This Reddit user says VLAN tagging on the WAN port works fine on the R4S with the quintus-lab build: https://r.nf/qkw3xm

Maybe the changes made in order to fix this can be ported to the snapshot, isn't it?

You guys should report the issue on the openwrt github.

Is this a NanoPi R4S only issue or its any device using openwrt on the last snapshot? Cause right now the NanoPi R4S only has access to snapshot builds officially.

The only builds that use stable openwrt for the NanoPi R4S are the following:

  • https://github.com/anaelorlinski/OpenWrt-NanoPi-R2S-R4S-Builds - Can you try this build? i think vlan tagging on the wan works here too.

  • FriendlyArm own build - But i think it has the same issue with vlan as the snapshots do, cause on another forum and from a user trying to set up a Load Balance on the NanoPi R4S using a managed switched before the nanopi R4S, he could not set vlan on the wan interface on the snapshots or in the friendly arm build, but on @anaelorlinski build it worked.

Has anyone installed RTC battery inside R4S case, is there enough space?