dumischbaenger

Thank you! It worked. It would probably more convenient to change the UUID on the root fs of my backup card. I guess I'll try it next time.

First - sorry for my late reaction, but I thought the system would mail me if somebody answers my question. Second - stupid me - I use normally old style device names or labels in fstab, so I didn't thought of the partitions UUID. Is it enough to change the file armbianEnvt.txt or is there a second step to make it active?

Hello, I would like to recover my Armbian root file system on a second sd card. On the second sd card there is a slightly older Armbian version installed. Unfortunately my efforts ended up in a boot loop with the second card. Here is what I did: backup current Armbian tar czpf ~/tmp/backupArm.tgz --exclude=dev/* --exclude=proc/* --exclude=run/* --exclude=tmp/* --exclude=mnt/* . restore backup on second card tar xvzf ~/tmp/backupArm.tgz Both cards use MBR partition style. Partition starts at sector 2048. Here are my SD cards details: current (source) fdisk -l /dev/sde Disk /dev/sde: 29.3 GiB, 31440502784 bytes, 61407232 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc6a8c537 Device Boot Start End Sectors Size Id Type /dev/sde1 2048 60793151 60791104 29G 83 Linux second (target) fdisk -l /dev/sde Disk /dev/sde: 28.8 GiB, 30908350464 bytes, 60367872 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x72530afd Device Boot Start End Sectors Size Id Type /dev/sde1 2048 59160511 59158464 28.2G 83 Linux Any idea is welcome. Regards, Bernhard

Has anybody tried 5.31? It seems to be the last Armbian we will get - the board is marked as phased out. I made a quick test yesterday. Looks like the switch behavior changed again.

I wrote an email to Florian Fainelli. He commented on the "Drop support for Lamobo R1" thread at Github. I asked him if he would mind to answer some questions about R1 switch configuration but he pointed me to the Github discussion.

First, the configuration was originally from BrUser. Honor goes to him. Second, I tried at the beginning exactly what you want - a very basic simple switch configuration, but I had no luck. Every time I tried it, network packages disappeared somewhere in the network stack. If you have such a kind of configuration please report here. I think BrUser tried it too. Please read the thread. Unfortunately there is no "manual" for the br53 driver. Documentation from other producer like Melanox (see below) do not always apply. That means documented ip and link configs do not work on our switchboard. Third, the DSA driver for br53 tries to offload the work to the hardware. I find this paper useful to understand the driver hardware relation: https://people.netfilter.org/pablo/netdev0.1/slides/Hardware-accelerating-Linux-network-functions.pdf Further IMHO interesting documents: https://www.kernel.org/doc/Documentation/networking/dsa/dsa.txt https://www.kernel.org/doc/Documentation/networking/switchdev.txt https://github.com/Mellanox/mlxsw/wiki/Switch-Port-Configuration https://github.com/Mellanox/mlxsw/wiki/Bridge http://events.linuxfoundation.org/sites/events/files/slides/LinuxConJapan2014_makita_0.pdf

Sorry for my late answer, but I didn't realized your question. At the moment I use the standard interface file that just starts up eth0 with dhcp. After boot I start my script manually. In the last days I tried to contact the driver developer in order to get more information on the switch configuration, perhaps working examples, some explanations, ... but he was not interested to support me.

I guess you mean my test with a VLANless network configuration don't you?

Now I made a test with your config. I copied a 6GB file via nfs and it worked without problems. Pings are okay too. I made two minor changes to your script: added "bridge vlan del ... master" commands to remove all rules with VID 1 commented "ip link set dev br0 type bridge stp_state 0" out because it resulted in an error assigned a IP address and route set -xue ip link set eth0 down ip addr flush eth0 ip link set eth0 up ip link add link eth0 name eth0.101 type vlan id 101 ip link set eth0.101 up ip link add link eth0 name eth0.102 type vlan id 102 ip link set eth0.102 up ip link add link eth0 name eth0.103 type vlan id 103 ip link set eth0.103 up ip link add link eth0 name eth0.104 type vlan id 104 ip link set eth0.104 up ip link add link eth0 name eth0.105 type vlan id 105 ip link set eth0.105 up ip link add br0 type bridge #ip link set dev br0 type bridge stp_state 0 # BCM53125 ports 4, 0, 1, 2, 3 ip link set lan1 master br0 ip link set lan2 master br0 ip link set lan3 master br0 ip link set lan4 master br0 ip link set wan master br0 bridge vlan add vid 101 dev lan1 pvid untagged bridge vlan del dev lan1 vid 1 self bridge vlan del dev lan1 vid 1 master bridge vlan add vid 102 dev lan2 pvid untagged bridge vlan del dev lan2 vid 1 self bridge vlan del dev lan2 vid 1 master bridge vlan add vid 103 dev lan3 pvid untagged bridge vlan del dev lan3 vid 1 self bridge vlan del dev lan3 vid 1 master bridge vlan add vid 104 dev lan4 pvid untagged bridge vlan del dev lan4 vid 1 self bridge vlan del dev lan4 vid 1 master bridge vlan add vid 105 dev wan pvid untagged bridge vlan del dev wan vid 1 self bridge vlan del dev wan vid 1 master ip link set eth0.101 master br0 ip link set eth0.102 master br0 ip link set eth0.103 master br0 ip link set eth0.104 master br0 ip link set eth0.105 master br0 ip addr add 192.168.178.2/24 broadcast 192.168.178.255 dev br0 ip route add default via 192.168.178.1 ip link set br0 up ip link set lan1 up ip link set lan4 up ip link set lan2 up ip link set lan3 up ip link set wan up Congratulation - I think you found a working configuration!

How can I check this? I will try your config tomorrow.

I tried it, but I can't get it to work. I wrote this script: set -xue dmesg -C #BD remove default settings ip link set eth0 down ip addr flush eth0 ip link set eth0 up #show status ip link ip addr #create bridge without vlan filter ip link add br0 type bridge echo 0 > /sys/class/net/br0/bridge/vlan_filtering bridge vlan del vid 1 dev br0 self #attach ports to bridge and del VID 1 filtering rules for i in {1..4} ; do ip link set lan$i master br0 ip link set lan$i up bridge vlan del vid 1 dev lan$i bridge vlan del vid 1 dev lan$i self done #set ip ip addr add 192.168.178.2/24 broadcast 192.168.178.255 dev br0 sleep 10 #show status cat /sys/class/net/br0/bridge/vlan_filtering ip link ip addr bridge vlan dmesg At the end the bridge is up and running, the connected port is up too, IP address is assigned, route is added, but I can't ping hosts on the network. I also can't see ethernet packets with tcpdump on eth0, lan2 (connected port) and br0.

Are you sure that it's necessary to create five different VLANs? User badrianiulian posted here https://github.com/igorpecovnik/lib/issues/511 on the 5 of February a configuration with one VLAN. # ======================================= # Setup interfaces and VLANs # ======================================= ip link set eth0 up # Create VLAN 101 on interface eth0: eth0.101 ip link add link eth0 name eth0.101 type vlan id 101 # Create bridge br0 with STP(0) on VLAN 101 with interfaces/tagged: lan1 untag lan2 untag lan3 untag lan4 untag wan untag wlan0 untag eth0.101 tag ip link add br0 type bridge ip link set dev br0 type bridge stp_state 0 ip link set lan1 master br0 bridge vlan add vid 101 dev lan1 pvid untagged bridge vlan add vid 101 dev lan1 pvid untagged self ip link set lan1 up ip link set lan2 master br0 bridge vlan add vid 101 dev lan2 pvid untagged bridge vlan add vid 101 dev lan2 pvid untagged self ip link set lan2 up ip link set lan3 master br0 bridge vlan add vid 101 dev lan3 pvid untagged bridge vlan add vid 101 dev lan3 pvid untagged self ip link set lan3 up ip link set lan4 master br0 bridge vlan add vid 101 dev lan4 pvid untagged bridge vlan add vid 101 dev lan4 pvid untagged self ip link set lan4 up ip link set wan master br0 bridge vlan add vid 101 dev wan pvid untagged bridge vlan add vid 101 dev wan pvid untagged self ip link set wan up ip link set wlan0 master br0 bridge vlan add vid 101 dev wlan0 pvid untagged bridge vlan add vid 101 dev wlan0 pvid untagged self ip link set wlan0 up ip link set eth0.101 master br0 bridge vlan add vid 101 dev eth0.101 pvid untagged bridge vlan add vid 101 dev eth0.101 pvid untagged self ip link set eth0.101 up I tested it on 5.26. It is possible to get the interfaces up and acquire a IP address but the network is not reliable. If I ping a host I have lots of packets lost. So I extinguished my bonfire. I've read a lot during the last two or three weeks on bridges and switches. Here are some of my favorites: https://www.kernel.org/doc/Documentation/networking/dsa/dsa.txt https://www.kernel.org/doc/Documentation/networking/switchdev.txt https://github.com/Mellanox/mlxsw/wiki/Switch-Port-Configuration https://github.com/Mellanox/mlxsw/wiki/Bridge http://events.linuxfoundation.org/sites/events/files/slides/LinuxConJapan2014_makita_0.pdf Some Questions come to my mind: -Is it really obligatory to use VLANs if I use the R1 just as switch? At the beginning of my research I tried to get it working without VLANs. I turned off VLAN filtering, set ports to untagged, ... It was a complete fail. The earlier mentioned bridge article from Mellanox stated "Port netdevs can only be enslaved to a VLAN-aware bridge." Ok - but why? -The R1 configurations use some form of "bridge vlan add ..." command but so far I can see vlan_filtering is not enabled on this bridges? -How can I better trace network traffic. I use tcpdump to monitor interfaces but sometimes I wonder why a packet does not arrive at the bridge I created. Is there a simple to use tool to follow network packet through the network stack? -The "bridge vlan" command shows there exists a VID 1. Can't I use this default VLAN to enables switching? The complete bridging and switching topic on bc53 is opaque and confusing to me. Perhaps I have next weekend time to do some further research. By the way is your network configuration reliable? No problems with packet loss?

Here is my housing! An here is a special cable to solve the HD power issue: With this configuration it is possible to supply the HD directly with energy. Although I do understand the criticism of tkaiser I think it would be a pity for me and perhaps others to drop support. I use it as a simple desktop switch and home server. With Armbian 5.24 it runs stable here. With 5.25 I was unfortunately not able to get the switch switchting till now.

I tried this script but some commands do not work at all: + ip link set lan1 master eth0.102 RTNETLINK answers: Operation not supported

Tido wrote: > I am looking for a recommendation(s), in which Forum shall I register to ask questions in regards to DSA (Distributed Switch Architecture) ? Do you know about this thread? https://github.com/igorpecovnik/lib/issues/511 In the audience is the user ffainelli the author of the b53 driver. There is also a comment from user wiesl with a lengthy bash script from 29 Dec 2016. I think I will try this one. User badrianiulian seems to have a working setup on 5.25. See his statement from 5 Feb.