On TO 3.x.x I had set some VLAN on my Turris Omnias (by following instructions in documentation), but after fresh installation to 4.x and later to 5.x, there is no possibility to set VLAN in LuCI and there is no instruction how to proceed.
My question is, it is possible just to edit network, dhcp and firewall according to files from 3.x.x to enable VLAN on TOS 4.x/5.x?
network TOS 5.x How I should edit this config file?
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fde4:1bc5:f8d1::/48'
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
option bridge_empty '1'
list ifname 'lan0'
list ifname 'lan1'
list ifname 'lan2'
list ifname 'lan3'
list ifname 'lan4'
config interface 'wan'
option ifname 'eth2'
option proto 'dhcp'
option hostname 'Router'
option ipv6 '0'
option type 'bridge'
config interface 'guest_turris'
option enabled '1'
option type 'bridge'
option proto 'static'
option ipaddr '10.111.222.1'
option netmask '255.255.255.0'
option bridge_empty '1'
config interface 'wan6'
option ifname '@wan'
option proto 'none'
Further I would like to set connection on one of LAN ports with some proxy, to be able watching videos from abroad right on TV (e.g. watching TV archives from Czech in Slovakia) - just by swiching cable between these ports. But I don´t know if this will be possible.
Well maybe I have not understand it. What I want, is some simple example, how should new network, dhcp and firewall config files look like. There is no such example (at least I have not found it) in this forum.
I am just asking how to edit config switch , config switch_vlan and other parts of files (which were working in TOS3.x) to get working simple vlan (in TOS4.x/5.x), but nobody could answer this (maybe simple) question yet. So, if you know how to do it, please, write here some tutorial.
There is no Config Switch anymore. Furthermore, in your TOS3 example I don’t see any VLAN used on user side [beside of the default split ports 0 - 3 and port 4].
In my case, I use tagged VLAN2 on lan0 port, and separate network on lan1 port [no need to create VLAN since TOS4]. You can remove IPv6 related stuff if not using it.
config zone
option name 'vlan'
list network 'vlan'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
But device connected to separated network (vlan) cannot reach internet. It obtains IP from correct range, but I think, I have bad firewall rule or there is missing something…
Hi!
I have been reading the entire message to try to understand how to reconfigure the turris omnia router in TOS 4.x / 5.x versions. unable to use swconfig.
I have seen that the Vlan are now controlled with the DSA switch, but I do not see enough information about it to understand it. How can I transfer this configuration to Dsa Switch?
This is my configuration for Turris Omnia that I have been using for 2-3 years Turris OS version 3.xx with 15.05 (Chaos Calmer), with Lan eth0.1, Iptv eth1.2 (incoming tv traffic), Voip eth1.3, Tvlan eth0.4 (isolated tv so it doesn’t flood traffic with mcproxy), wan eth1.6:
Well, it goes bit beyond my knowledge. I can say, you will create VLAN only by assigning a physical network interface with .x, such as lan0.1. Therefore if you set it is lan0 it goes out untagged, when lan0.1 then it goes out tagged as VLAN1
This VLAN config works. There are a lot of interface in differt VLANS. Now you can set the client to use a particular VLAN and it get an IP and works just fine.
Where I am stuck is how can I say VLAN3 interface lan10.3 is tagged and hands hands dhacp instead of LAN10. On interface LAN10 I always get dhcp from VLAN0. How can I change that ?
The DHCP Service needs to get an idea of the networks structure. The OpenWrt DHCP Service enables for the definition of multiple subnets AND to bind them to a specific network interface.
DHCP is working if you set the client to the desired vlan, client side tagging.
All interfaces default to VLAN1 (tagged) all the other VLANS are not tagged. What I like to do is to move the interface tag from lan1 to lan1.8 for example.