All Activity

Arhhh still no good. PC1 still can NOT ping 10.10.10.2 root@rpi4b:~# ip route show default via 192.168.100.254 dev eth0 proto static metric 101 10.10.10.0/24 dev enp4s0 proto kernel scope link src 10.10.10.1 metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.101 metric 101 root@rpi4b:~#

Hi there, Not sure about the syntax of `firewall-cmd`, but you should only masquerade on the NIC connected to the 10.10.10.0/24 network, as masquerading does have some performance impact to/from that NIC. Seems you need to check which `zones` are defined and create a `zone` to only cover NIC2 on 'rocky linux'. For the `route` command, you can use the "new" `ip route` way: # type on PC1 sudo ip route add 10.10.10.0/24 via 192.168.100.101 This will tell PC1 to throw packets that are destined to reach the 10.10.10.0/24 network towards 'rocky linux''s NIC1. No, masquerading is done on the destination address of the IP packet, it will not change any source/destination port number. Masquerade here uses NAT, port is not translated. Groetjes,

I have also installed firewalld any ports or routing i should allow ? eg : sudo firewall-cmd --zone=public --add-masquerade ?

@Nick A I fixed the wifi issue after warm reboot for x98h with this patch:

root@rpi4b:~# sudo route add -net 10.10.10.0/24 gateway 192.168.100.101 sudo: route: command not found root@rpi4b:~# Do i need to add dev eth0 or enp4s0 ?

Hi there, Ah that diagram changes things a little. You would need to add a route to PC1, so that it knows to send packets for device 1 via 'rocky linux'. sudo route add -net 10.10.10.0/24 gateway 192.168.100.101 That will make sure packets with destination 10.10.10.0/24 will be sent to 'rocky linux'. Then on 'rocky linux' the forwarding should handle forwarding those packages from NIC1 to NIC2. You will have NIC2 masquerade outgoing packets as 10.10.10.1 instead of the real source address 192.168.100.102, so 'device 1' will respond to 10.10.10.1 instead of 192.168.100.102 - as 'device 1' has no default route. Then on 'device 1', packets will arrive from "masqueraded" NIC2 10.10.10.1 and it should respond accordingly. Then on 'rocky linux' responses from 'device 1' will be received on NIC2, conntrack will know where the packet originally came from and send stuff back to 'PC1' This should work, but this is a little messy 🙂 Do ping back here! Groetjes,

Hi all. Thank you all for helping on this. I have created a diagram. - Armbian not rocky. the red box is what I CAN NOT change - no access. I do have access to the Linux box - so I want to be able to ping from PC 1 to Device 1 on 10.10.10.2. Device 1 - do have access to it and configure whatever it needs.

Hi everyone, I need to enable the csi camera and i2c port on my zero3 development board. When I click on the management overlay, an error occurs. Is there any solution?

Hi there, The `net.ipv4.ip_forward=1` will make the packets coming in on NIC1 be routed/sent to NIC2 due to the destination fitting in the network, but the device on NIC2 will not know how to send return packets to 192.168.100.*/24 as it does not have any fitting directly connected networks. Usually you could use default gateway/route to point them back to the Pi, but you said you cannot configure that. Try the following on the Pi: sudo iptables -t nat -A POSTROUTING -j MASQUERADE -o enp4s0 That should enable NAT on NIC2, which will masquerade any packet sent from NIC2 with "source address" 10.10.10.*/24 which it does know how to talk to. Btw, can you confirm the following was indeed the output of `ip route`: 10.10.10.10/24 dev enp4s0 proto kernel scope link src 10.10.10.2 metric 100 One would expect 10.10.10.0/24 as network instead of 10.10.10.10/24. Groetjes,

Dear Armbians, I'm thrilled to announce the launch of this digest for our amazing community. For newcomers, Armbian is a lightweight Linux distribution that breathes life into ARM-based single-board computers, transforming tiny, affordable boards into powerful servers, workstations, and IoT devices. This newsletter is our way of keeping you in the loop, sharing the latest releases, celebrating community contributions, and diving into the technical insights that power your projects. Whether you're a tech enthusiast or just getting started with your first Orange Pi, there's something here for you. Thanks for being part of this incredible journey! Igor Armbian project manager View the full article

moved

Hi all, I’m running Armbian 24.5 (Ubuntu Jammy CLI) on an Orange Pi 3 LTS with kernel 6.6.y, trying to use a CH341A Mini Programmer to flash an SPI EEPROM chip. But I’m stuck, the programmer isn’t detecting the chip at all. Connected the module to the chip using the correct pins (CS, MOSI, MISO, CLK). Powered the chip at 3.3V to match Armbian’s logic level. Used flashrom on Armbian (via terminal) to detect the chip, but it returns “no device” or similar errors. Tried different USB ports, different cables , same result. Do I need to match some specific SPI mode or speed for Armbian or for specific EEPROMs? Is there an issue with voltage levels or pull-up / pull-down resistors that often catches beginners? Any recommended OS commands/logs to check so I can see what’s going wrong (e.g. permissions, USB detection, lsusb output)? Thanks in advance for your help!

tag adjusted

Hi Werner I apologize for radxa zero, as I do not know which tag to choose. I have a board based on OK3568 from Forlinx. Logs https://paste.armbian.com/ohokuhozab

Hi there, the 2 NICs are on my RPi Armbian. ip route output. > modified it abit to match but concept is below. default via 10.10.10.254 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.10 metric 101 10.10.10.10/24 dev enp4s0 proto kernel scope link src 10.10.10.2 metric 100 I have only PC1 connected to NIC1 with 192.168.100.101 GW - 192.168.100.254 This PC1 can NOT be changed. Device1 on NIC2 10.10.10.100/24 < this have no Gateway as its only a slave device. I need to reach Device1 on NIC2 from the PC1 on NIC1..how is this achieved? I tried /etc/sysctl.conf net.ipv4.ip_forward=1 still missing something… I failed to mention is that I can only modify settings within the Linux box containing the 2 NICs. I need some sort of interlinking NIC1 on 192.168 to forward packets to 10.10 network…

Can't say I know much about X11, but after playing around with the Cinnamon version I did get a desktop by: created file:/etc/X11/xorg.conf Section "Device" Identifier "Device0" Driver "fbdev" Option "Device" "/dev/dri/card0" EndSection So I figure something in the configuration or driver related ?. And that goes for all Debian flavors I tested. All gave the same error.

Hi there, Not sure if your question is complete, are both NIC1 and NIC2 in the same PC1 ? (NIC being network interface controller/card.) If NIC1 and NIC2 are both in the same computing node, the routes should be there already, if the configuration is plain and not something funky. Can you share the output of `ip a s` and `ip route` ? Also, do you have any firewall enabled? Gr,

Currently yes. A replacement for this package / service needs to be found and implement - in case you want to get involved. This isn't completely true. Armbian still does utilize CPUMIN/CPUMAX from /etc/default/cpufrequtils if present to set corresponding frequencies via the Armbian script armbian-hardware-optimization (packages/bsp/common/usr/lib/armbian/armbian-hardware-optimization). This script I believe runs at every system startup. So even without the cpufrequitls package installed, there is still some functionality in this area. Functionally that no one has likely touched or looked at in years.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Radxa Zero has a different soc: https://radxa.com/products/zeros/zero/ Double-check what hw you actually have

I am using kernel 6.12.45 with rk3568 , everything is displayed on my monitor. A colleague's computer does not work on 3 of the 4 monitors. the error is the same as in the theme / kernel: rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes , since it seems that no one is watching that topic, I decided to raise this issue. Has anyone encountered such a problem?

Each attached memory disk must have its own unique UUID. This is its essence. This depends on the platform (BROM bootloader flashed into the chip) and possibly the switch soldered to the board.

Hello all, I succeed to boot on sata usb by seting the UUID of the armbian_root from mmcblk1p1 to sda1 I tested several M2 SSD enclosures both NVME and NGFF most of the time, one in the middle, has a USB Hub and micro SDCARD port. Now if the USB enclosures is not connected, we are stuck in initramfs stage because the UIID partition given in /boot/ArmbianEnv.txt does not exist. I changed the UUID of emmc armbian_root (mmcblk1p1) thinking it would be overmapped with partition of S2 usb enclosure (sda1). It is not the case, it will only boot on emmc , ignoring S2 enclosures when mmcblk1p1 and sda1 shares the same UUID. I suggest USB enclosures should comes in higher boot priority than emmc after a bootable sdcard is present or not, so the end user is not lost in initramfs jungle.

``` root@opi5 /etc/apt/sources.list.d# apt-get update Hit:1 http://deb.debian.org/debian trixie-backports InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://security.debian.org trixie-security InRelease Hit:5 https://github.armbian.com/configng stable InRelease Hit:6 http://mirror.vinehost.net/armbian/apt trixie InRelease Reading package lists... Done W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details N: Missing Signed-By in the sources.list(5) entry for 'http://deb.debian.org/debian' ``` ``` root@opi5 /etc/apt/sources.list.d# apt-get update --audit Hit:1 http://deb.debian.org/debian trixie-backports InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://security.debian.org trixie-security InRelease Hit:5 https://github.armbian.com/configng stable InRelease Hit:6 http://mirror.vinehost.net/armbian/apt trixie InRelease Reading package lists... Done W: https://github.armbian.com/configng/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details A: https://github.armbian.com/configng/dists/stable/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding signature at time 2025-09-08T18:12:20Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature. N: Missing Signed-By in the sources.list(5) entry for 'http://deb.debian.org/debian' ``` **/etc/apt/sources.list.d/armbian-config.sources** ``` Types: deb URIs: https://github.armbian.com/configng Suites: stable Components: main Signed-By: /usr/share/keyrings/armbian.gpg ``` **/etc/apt/sources.list.d/armbian.sources** ``` Types: deb URIs: http://apt.armbian.com/ Suites: trixie Components: main trixie-utils trixie-desktop Signed-By: /etc/apt/trusted.gpg.d/armbian.gpg ``` **/etc/apt/sources.list.d/debian-backports.sources** ``` # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie-backports Components: main contrib non-free non-free-firmware Signed-By: ``` **/etc/apt/sources.list.d/debian.sources** ``` # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie-updates Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://security.debian.org/ Suites: trixie-security Components: main contrib non-free non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg ``` How to fix it?

Currently yes. A replacement for this package / service needs to be found and implement - in case you want to get involved. Thank you! It's a work of many people, impossible for me to poke into every issue or feature that exists