arnaudf

Hello, After several days of debug I put the finger on a very strange issue using integrated Ethernet. I use my Rockpro64 mostly as a Samba and DNS server. In my network context I implement 2 vlans as vlan interfaces (eth0.10 and eth0.20). Each of these interfaces needs to use a specific mac address that differs from physical eth0 mac address (it is an important point). If I use only the physical mac my router is not be able to route correctly between vlans (probably an ivl/svl issue). Under this context I first noticed that when I bring down eth0.20 although using vlan 10 (so eth0.10) connectivity is lost. I then write a script to gather all needed information (ie. ip link/addr/route/rule/neigh, ping, arping, netstat, ...) ==> no peculiar problem I then add a background tcpdump and, guess what, the connectivity loss didn't occur anymore ! After thinking a bit, I made the assumption that the main difference is the use of promiscuous mode during tcpdump. ==> and "bingo" : setting 'promisc' flag on eth0 acts as a workaround. Also if I do not set a specific mac for vlan and use physical mac leads to no connectivity issue, despite the wrong routing. The key point seems that bringing down a vlan interface unregisters all macaddress from listening process instead only the needed, so the connectivity problem. I don't know if it's a hardware limitation, a driver bug or Armbian issue, but I am open to any fix or at least, any debug hint that helps to narrow down the root cause. Regards.

Hello, I wonder if there other improvements. Indeed I did some changes to have thing working better. (Using Armbian 23.8.1 on Rockpro64) For example : - In journald.conf : had to set Storage as "volatile" instead of "auto". If not there is truncation of journald content at every midnight log rotation. I saw that some armbian-ramlog script steps depends on "volatile" Storage value. EDIT 23/01/2024 : in fact with "volatile" journal logs are never flushed to persistent storage. So I returned back to "auto" but needed to amend postrotate (see below). - In armbian-ramlog postrotate, I have done these changes : postrotate) cd /var/log.hdd/ #find . -type f -print | grep -E -v "(\.gz|\.xz|\.[0-9]|armbian-ramlog)" | while IFS= read -r file find . -type f -printf '%P\n' | grep -E -v "(\.gz|\.xz|\.[0-9]|armbian-ramlog)" | while IFS= read -r file do dest="/var/log/$file" # Fix: journal path exclusion if [[ "$dest" == */journal* ]] && [ -L $RAM_LOG/journal ]; then continue; fi # Fix: create full directory path if not exists if [ ! -d ${dest%/*} ]; then mkdir -p ${dest%/*}; fi cat $file > $dest done ;; So basically : - slightly modified the find action ( -printf '%P\n') to remove the leading dot - test and skip current file if $dest contains "/journal" and $RAM_LOG/journal is a link (to /var/log.hdd/journal). This leads to not overwrite journal files, so no truncation - added an mkdir -p so the full path is created if needed (if not there could be some errors with "deep" paths) I could submit a PR if needed. Also in armbian-truncate-log I see this line : [ -d /var/log.hdd/journal ] && find /var/log.hdd/journal -ctime 1 \( -name '*@*' -o -name '*~' \) -delete Why is it needed/done ? IMHO this could lead to delete history on ssd (permanent) storage although this truncation script seems to be purported for cleaning in-memory log partition. The path should be /var/log/ instead of /var.log.hdd, I assume (?)

Hello, For later reference : I found a (the?) solution. Basically it consisted in putting Bookworm repo links in sources.list. Then I upgraded a bunch of packages (more than 400). Don't know if there is any side-effect. The only issue I faced was the name of network interface that changed from eth0 to end0. The workaround was to put a "rename" statement in /etc/network/interfaces. Repo links : https://gist.github.com/ishad0w/7665cde882aa7dc3eec99613802e61e4

Hello, I'm facing a weird issue. After removing Samba version 4.17 I'm not able to install anymore Samba 4.13 (I would like to use this version for libnss-wins compat'). I'm checked some web ressources with no success. You will see below the output of many (interesting?) command. If anyone could help me on this issue it could be nice. Sorry for the big post. root@rockpro64:~# cat /etc/os-release PRETTY_NAME="Armbian 23.8.1 bullseye" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian 23.8.1 bullseye root@rockpro64:~# cat /etc/apt/sources.list deb http://deb.debian.org/debian bullseye main contrib non-free #deb-src http://deb.debian.org/debian bullseye main contrib non-free deb http://deb.debian.org/debian bullseye-updates main contrib non-free #deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free deb http://deb.debian.org/debian bullseye-backports main contrib non-free #deb-src http://deb.debian.org/debian bullseye-backports main contrib non-free deb http://deb.debian.org/debian-security bullseye-security main contrib non-free #deb-src http://security.debian.org/ bullseye-security main contrib non-free root@rockpro64:~# apt install python3-samba samba-common-bin libwbclient0 samba-libs Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-samba : Depends: python3-ldb (>= 2:2.1.0) but it is not going to be installed Depends: libpython3.9 (>= 3.9.1) but it is not installable Depends: python3-talloc (>= 2.3.1~) but it is not going to be installed samba-libs : Depends: libavahi-client3 (>= 0.6.16) but it is not installable Depends: libavahi-common3 (>= 0.6.16) but it is not installable Depends: libcups2 (>= 1.7.0) but it is not going to be installed Depends: libpython3.9 (>= 3.9.1) but it is not installable Depends: python3-ldb (>= 2:2.1.0) but it is not going to be installed Depends: python3-talloc (>= 2.3.1~) but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@rockpro64:~# whereis python python: /usr/bin/python3.9 /usr/lib/python2.7 /usr/lib/python3.9 /etc/python3.9 /usr/local/lib/python3.9 root@rockpro64:~# sudo apt-cache policy samba python3-samba samba-common-bin libwbclient0 samba-libs samba: Installed: (none) Candidate: 2:4.13.13+dfsg-1~deb11u5 Version table: 2:4.17.12+dfsg-0+deb12u1~bpo11+1 100 100 http://deb.debian.org/debian bullseye-backports/main arm64 Packages 100 /var/lib/dpkg/status 2:4.13.13+dfsg-1~deb11u5 500 500 http://deb.debian.org/debian-security bullseye-security/main arm64 Packages python3-samba: Installed: (none) Candidate: 2:4.13.13+dfsg-1~deb11u5 Version table: 2:4.17.12+dfsg-0+deb12u1~bpo11+1 100 100 http://deb.debian.org/debian bullseye-backports/main arm64 Packages 2:4.13.13+dfsg-1~deb11u5 500 500 http://deb.debian.org/debian-security bullseye-security/main arm64 Packages samba-common-bin: Installed: (none) Candidate: 2:4.13.13+dfsg-1~deb11u5 Version table: 2:4.17.12+dfsg-0+deb12u1~bpo11+1 100 100 http://deb.debian.org/debian bullseye-backports/main arm64 Packages 2:4.13.13+dfsg-1~deb11u5 500 500 http://deb.debian.org/debian-security bullseye-security/main arm64 Packages libwbclient0: Installed: (none) Candidate: 2:4.13.13+dfsg-1~deb11u5 Version table: 2:4.17.12+dfsg-0+deb12u1~bpo11+1 100 100 http://deb.debian.org/debian bullseye-backports/main arm64 Packages 2:4.13.13+dfsg-1~deb11u5 500 500 http://deb.debian.org/debian-security bullseye-security/main arm64 Packages samba-libs: Installed: (none) Candidate: 2:4.13.13+dfsg-1~deb11u5 Version table: 2:4.17.12+dfsg-0+deb12u1~bpo11+1 100 100 http://deb.debian.org/debian bullseye-backports/main arm64 Packages 2:4.13.13+dfsg-1~deb11u5 500 500 http://deb.debian.org/debian-security bullseye-security/main arm64 Packages apt-get install -y libavahi-client3 Reading package lists... Done Building dependency tree... Done Reading state information... Done Package libavahi-client3 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source root@rockpro64:~# aptitude install samba The following NEW packages will be installed: libldb2{a} libtalloc2{a} libtdb1{a} libtevent0{a} libwbclient0{a} samba{b} tdb-tools{a} The following packages are RECOMMENDED but will NOT be installed: samba-dsdb-modules samba-vfs-modules 0 packages upgraded, 7 newly installed, 0 to remove and 2 not upgraded. Need to get 1727 kB of archives. After unpacking 18,7 MB will be used. The following packages have unmet dependencies: samba : Depends: python3-dnspython which is a virtual package and is not provided by any available package Depends: python3-samba but it is not installable Depends: samba-common-bin (= 2:4.13.13+dfsg-1~deb11u5) but it is not installable Depends: libpython3.9 (>= 3.9.1) which is a virtual package and is not provided by any available package Depends: samba-libs (= 2:4.13.13+dfsg-1~deb11u5) but it is not installable The following actions will resolve these dependencies: Keep the following packages at their current version: 1) samba [Not Installed]