> I want separate three port for using three private networks.
I would also like to do this. 3 NICs, three networks.
Here is my interfaces for using wan plus a separate bridge. They all come up for me on boot.
auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto wan iface wan inet dhcp auto lan0 iface eth0 inet manual auto lan1 iface eth0 inet manual # auto br0 iface br0 inet manual bridge_ports lan0 lan1 bridge_stp off bridge_fd 0 pre-up /sbin/ifconfig lan0 up pre-up /sbin/ifconfig lan1 up
Hope this helps.
So I’m not going crazy :-/
It’s like the Topaz chip will only operate the ports in “switch” mode and somehow over-rides the sw bridging’s usual operation. Just guessing here.
I do have a sw bridge br0 set up with lan0 & lan1 as members, and have compiled my kernel with all network/bridge related stuff enabled. Still don’t see anything. The bridging works because I have a voip phone connected through it and it works fine – I just can’t see the packets.
I’ll try a new kernel compile
I mean wireshark the traffic flowing FROM LAN0 to LAN1 not the individual ports.
I want to put this device in-line like:
w'shark ^ DEVICE ---- LAN0 --- LAN1 ---- ROUTER
Yes, it works with normal ports -USB or otherwise. However the Espressobin seems to operate all three ports in switch mode and I have not been able to see traffic passing between any of the ports – only traffic I can see is what is destined for the single port I am sniffing.
This board is interesting to me because of its price and built-in NICs, but only if I can mirror/sniff the packets crossing the LANX ports.
Interesting stuff @pacman
Now, if I could only get the ability to wireshark the traffic over the LAN0 and LAN1 interfaces – or ANY interface – this would be a useful board for me.
@pacman – I think you tell u-boot where to find this in the very initial setup described here: http://wiki.espressobin.net/tiki-index.php?page=Boot+from+removable+storage+-+Ubuntu#Setting_U-Boot_parameters_2
Specifically when you run:
Marvell>> setenv image_name boot/Image Marvell>> setenv fdt_name boot/armada-3720-community.dtb
I am running off a microSD card.
As an experiment I edited arch/arm64/boot/dts/marvell/armada-3720-community.dts to change the name of wan to wan1. I then recompiled the kernel and copied the new armada-3720-community.dtb into /boot on the espressobin. Rebooted and the interface is called wan1 now, and works fine.
Just keep in mind that the armada-3720-community.dtb is kernel-specific, so you should follow the instructions on compiling your own kernel and use the armada-3720-community.dtb and Image.
I don’t know what the other settings in the dts do though!
The dts gets compiled when you compile the kernel. The dts would be found in the kernel tree at arch/arm64/boot/dts/marvell/armada-3720-community.dts
This file also is where the interface names are set.
As for how to load it – I am pretty sure that the kernel loads the .dtb from /boot/ and it does not require loading into NVRAM specifically.
I have been having the same issue. I can’t seem to get any promiscuous capture from lan0,lan1, br0 or wan interfaces.
Really wish this had just 3 standard NICs instead of the switch.
Very interesting, thanks.
Did you/anyone find any solution to this? Espressobin is not suitable for my purpose if the two additional ports can only be used as a full switch.
Technical specification tables can not be displayed on mobile. Please view on desktop