RUT360 VLAN interface & routing Next

Teltonika Networks
1

Continuing this issue. I note, VLAN Routing on a 955 or RUT11 worked fine long ago using separate LAN ports.

360 only has one LAN port.

OS upgraded and tried again: RUT36X_R_00.07.07.1_WEBUI

Different configurations in this version, did not seem complete.

WAN: DHCP, no issues

LAN:
Default: 10.20.1.1/24, NO TAG, eth0, works fine, NO DHCP

VLAN 11:

 Add VLAN11, 802.1AD, eth0

Interface:

Add VLAN11 as interface, eth0, 10.20.2.1/24, all traffic TAGGED, No DHCP

Tagged traffic from 10.20.2.0 is not routed to the WAN interface and traffic to the 10.20.2.0 network does not reach the attached LAN Network.

Cannot ping the 10.20.2.1 from any VLAN 11 TAGGED device, but most of time can ping from the upstream Cisco’s on 10.20.1.0.

ARP tables show as incomplete

Tried static route from 10.20.2.0 to 10.20.1.0 and that did not get packets routed to the LAN interface.

All VLAN Default traffic works well.

If this has to be done in CLI can you send me some examples [please include firewall sections].

Many thanks

2

Hello,
I think you could try to disable VLAN filtering in /etc/config/network, then you will get all tag’s to CPU (eth0) port

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '0'
3

Tried the attached, before rebooting, checked URL Firewall, failure to load many variables, so I deleted the switch entry. It does not look right in any case, VLAN 0 is default and VLAN 11 is the new VLAN.

There is no upload facility on this, so below

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2024.05.21 18:27:40 =~=~=~=~=~=~=~=~=~=~=~=
cat network

config interface ‘loopback’
option device ‘lo’
option proto ‘static’
option ipaddr ‘127.0.0.1’
option netmask ‘255.0.0.0’
option area_type ‘lan’

config globals ‘globals’
option ula_prefix ‘fd6f:1f73:f3db::/48’

config device ‘br_lan’
option name ‘br-lan’
option type ‘bridge’
list ports ‘eth0’
option stp ‘0’

config interface ‘lan’
option device ‘br-lan’
option area_type ‘lan’
option proto ‘static’
option netmask ‘255.255.255.0’
option ip6assign ‘60’
option igmp_snooping ‘0’
option delegate ‘1’
option force_link ‘1’
option ipaddr ‘10.20.1.1’

config interface ‘wan’
option device ‘eth1’
option proto ‘dhcp’
option metric ‘1’
option area_type ‘wan’

config interface ‘wan6’
option device ‘eth1’
option proto ‘dhcpv6’
option metric ‘2’
option area_type ‘wan’

config interface ‘mob1s1a1’
option proto ‘wwan’
option modem ‘1-1’
option metric ‘3’
option sim ‘1’
option dhcpv6 ‘0’
option pdptype ‘ipv4v6’
option method ‘nat’
option auth ‘none’
option auto_apn ‘1’
option area_type ‘wan’

config device ‘1’
option name ‘VLAN11’
option ifname ‘eth0’
option vid ‘11’
option type ‘8021ad’

config interface ‘ifLan1’
option proto ‘static’
option netmask ‘255.255.255.0’
option area_type ‘lan’
option ipaddr ‘10.23.1.1’
option name ‘VLAN11’
option delegate ‘1’
option force_link ‘1’
option device ‘VLAN11’

config switch
option name ‘switch0’
option reset ‘1’
option_enable_vlan ‘0’
e]0;root@RUT360: /etc/configaroot@RUT360:/etc/config#

4

Issue solved

Returning all to Amazon (they have to go back to line Amazon in 4-5 countries, arg).

All 200+ units of the 260 and 360 for defects in software.

Return approvals were granted, that is what is great about buying form Amazon.

We will replace with units RUT units with separate LAN ports.

Cheers

5

Wow…
Which units you’ll be going for instead? Do you know already?

6

Simonas, I just tried to call you to go over what has been proposed to us for Routers and Switches to avoid these types of returns.

I assume it is you replying to these messages still?

7

This topic was automatically closed after 15 days. New replies are no longer allowed.