TOS6: Configuring the switch / using both eth0 and eth1

Omnia hardware Omnia HW help
1

Hi there,

as an old indiegogo user of Omnia, I certainly remember the old difficult times with configuring the internal ETH switch. Anyways, I am now running TOS6 and have the following question: my understanding of https://docs.turris.cz/hw/omnia/omnia-net.jpg is that there are two interfaces on the SoC attached to the switch, eth0 (-> Port5) and eth1(-> Port6). I wonder if I can somehow map one of these two eth ports directly to (say) the LAN4 port of the switch, while the other 4 ports will be accessed via the other eth port.

My background motivation: I replaced the eth2 WAN with a metallic SFP, and would like to use one of the LAN0-LAN4 ports for WAN via mapping it directly to eth0 or eth1

1 Like
2

While not tested myself. Have you tried …

In /etc/config/network

config interface 'wan'
    option ifname 'lan0'
    option proto 'dhcp'
    ...

config interface 'lan'
    option ifname 'lan1 lan2 lan3 lan4 eth2'
    option proto 'static'
    ...
1 Like
3

Normally you could use

ip link

To see which port is connected where. Normally it should be eth0 on lan4 and the rest of lan ports on eth1 but some update changes that so all the ports are linked to the same physical interface because its not solved yet to use DSA multi interface in OpenWRT.

4

I am on HBL but still TOS 6.0 and all ports are linked to eth1.

Edit: And with DSA you dont use eth0/eth1 at all just use lan4 for example as second interface for WAN

5

If you want to address a single port, you can use the lan0-lan4 ports as their own network devices. The DSA stuff figures out the rest for you.

1 Like
6

It seems that there was some misunderstanding. My problem is NOT called getting (say) LAN4 working as WAN and LAN0-LAN3 working as LAN (to that end, even LuCI allows to make this happen pretty easily). My problem is that from the bandwidth tests clearly my LAN and WAN now shares the same 1Gbit/s SoC<->switch connection (perhaps eth1?), and I feel there is a potential to utilize also the other SoC eth port.

7

The original question from @janvolec was different though.

According to the (no longer up to date) Turris documentation this is possible.

Anybody has any idea on how to do it?

8

Yes, this is indeed what I had in mind when talking about the old difficult times.