# uname -a
Linux bpi-r2 4.14.11-00039-ga352d6b52e30 #2 SMP Thu Jan 4 11:27:02 EST 2018 armv7l GNU/Linux
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 4a:93:ae:dc:99:04 brd ff:ff:ff:ff:ff:ff
3: wan@eth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 4a:93:ae:dc:99:04 brd ff:ff:ff:ff:ff:ff
4: lan0@eth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 4a:93:ae:dc:99:04 brd ff:ff:ff:ff:ff:ff
5: lan1@eth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 4a:93:ae:dc:99:04 brd ff:ff:ff:ff:ff:ff
6: lan2@eth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 4a:93:ae:dc:99:04 brd ff:ff:ff:ff:ff:ff
7: lan3@eth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 4a:93:ae:dc:99:04 brd ff:ff:ff:ff:ff:ff
8: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:08:22:04:4c:00 brd ff:ff:ff:ff:ff:ff
9: ap0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 02:08:22:04:4c:00 brd ff:ff:ff:ff:ff:ff
LEDE for bpi-r2 have some hack in dsa core layer for allowing eth0 mapped into lan0-4, and eth1 mapped into wan. (mutliple cpu port is being utilized).
While it doesn’t do it in upstream because dsa core layer haven’t been able to support more than one cpu port at the current point. So, mt7530 dsa in upstream code still utilize just only one cpu port to follow core’s definition.
But dsa core member is designing and thinking this feature. I believe it should be supported in the near feature.
On 4.1.4, for some reason i can’t get 1000Mbps/Full?
[ 10.562987] mt7530 mdio-bus:00 lan3: Link is Up - 100Mbps/Full - flow control rx/tx
[ 11.522700] mt7530 mdio-bus:00 lan0: Link is Up - 10Mbps/Half - flow control off
[ 3378.082974] mt7530 mdio-bus:00 lan2: Link is Up - 100Mbps/Full - flow control off
I mainly use build.sh to copy kernel to sdcard because i can define name of binary in boot and this makes backup of existing kernel.
If you want to use different names you have to make sure that your new kernel gets loaded by set kernel var to name of your Kernel-binary. If you use my last uboot there are multiple kernel-vars and you can define own menu-entries (needs reload bootmenu before they appear).
Forgive my poor knowledge, the port isolation works for PHY to switch lines and thus all lan-ports are considered to carry information on NIC eth0. If this is true, does the CPU differentiate which lan port is sending the information and how does it do that?
PS- I wish to implement OVS on R2 but the port isolation does not work to parse and redirect traffic from each of the lan ports
I have your buster build and have all of the Ethernet interfaces working out of the box. The wireless connection I can't seem to get it working at all. It isn't represented when doing the "ip a" command. How do I get the wireless up and operational?