problem with vlan configuration

RouterOS Beginner Basics
1

Hi, I have this vlans configuration on a mikrotik router ( not switch ). Why does the computer connected to port vlan10-eth1 not see the computer in vlan10-eth2 and ping to address 192.168.10.2 does not work ?

Computers with vlan-id=10 are connected to ports vlan10-eth1 and vlan10-eth2.

/interface vlan
add name=vlan10-eth1 vlan-id=10 interface=ether1
add name=vlan20-eth1 vlan-id=20 interface=ether1

/interface vlan
add name=vlan10-eth2 vlan-id=10 interface=ether2
add name=vlan20-eth2 vlan-id=20 interface=ether2

/ip address
add address=192.168.10.1/24 interface=vlan10-eth1
add address=192.168.20.1/24 interface=vlan20-eth1

/ip address
add address=192.168.10.2/24 interface=vlan10-eth2
add address=192.168.20.2/24 interface=vlan20-eth2
2

everything is wrong, start from:
https://help.mikrotik.com/docs/spaces/ROS/pages/103841826/Basic+VLAN+switching

3

I don’t want to use birdge. I want it to work in layer 3. This configuration is on the router side, not the switch side

4

to answer your question:
Why does the computer connected to port vlan10-eth1 not see the computer in vlan10-eth2 and ping to address 192.168.10.2 does not work ?

ARP ← without layer 2 there is no layer 3 / simple logic

5

But I can ping address 192.168.10.1/24 on interface vlan10-eth1. If it were as you write I wouldn’t be able to ping the interface vlan10-eth1

6

If you want answers provide more complete information starting with
/export file=anynameyouwish (minus router serial number, any public WANIP information, keys etc.)

THe config is interrelated showing what you thing we need to see is NOT helpful.
By the way, a bridge is not absolutely required but its kinda how the ROS was designed to work most efficiently.
Once the config is shown, an optimal config based on your requirements can be designed.

7

@martimk - if you know better, why do you ask?

on the computer do arp -a
you will see an entry for 192.168.10.1
but not for: 192.168.10.2

you can divide the /24 network into 2x /25 then it will work L3

8

my config file:

/interface ethernet
set [ find default-name=ether1 ] disable-running-check=no
set [ find default-name=ether2 ] disable-running-check=no
set [ find default-name=ether3 ] disable-running-check=no
set [ find default-name=ether4 ] disable-running-check=no
/interface vlan
add interface=ether1 name=vlan10-eth1 vlan-id=10
add interface=ether2 name=vlan10-eth2 vlan-id=10
add interface=ether1 name=vlan20-eth1 vlan-id=20
add interface=ether2 name=vlan20-eth2 vlan-id=20
/disk
set slot1 media-interface=none media-sharing=no slot=slot1
set slot2 media-interface=none media-sharing=no slot=slot2
set slot3 media-interface=none media-sharing=no slot=slot3
set slot4 media-interface=none media-sharing=no slot=slot4
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/iot lora servers
add address=eu.mikrotik.thethings.industries name=TTN-EU protocol=UDP
add address=us.mikrotik.thethings.industries name=TTN-US protocol=UDP
add address=eu1.cloud.thethings.industries name="TTS Cloud (eu1)" protocol=\
    UDP
add address=nam1.cloud.thethings.industries name="TTS Cloud (nam1)" protocol=\
    UDP
add address=au1.cloud.thethings.industries name="TTS Cloud (au1)" protocol=\
    UDP
add address=eu1.cloud.thethings.network name="TTN V3 (eu1)" protocol=UDP
add address=nam1.cloud.thethings.network name="TTN V3 (nam1)" protocol=UDP
add address=au1.cloud.thethings.network name="TTN V3 (au1)" protocol=UDP
/interface bridge port
add bridge=*13 frame-types=admit-only-untagged-and-priority-tagged interface=\
    ether2 pvid=20
add bridge=*13 frame-types=admit-only-untagged-and-priority-tagged interface=\
    ether3 pvid=30
add bridge=*17 interface=*14
add bridge=*17 interface=ether1
/interface bridge vlan
add bridge=*13 tagged=*13 vlan-ids=20
add bridge=*13 tagged=*13 vlan-ids=30
/ip address
add address=192.168.99.1/24 interface=*14 network=192.168.99.0
add address=30.0.0.1/24 interface=*15 network=30.0.0.0
add address=192.168.10.1/24 interface=vlan10-eth1 network=192.168.10.0
add address=192.168.20.1/24 interface=vlan20-eth1 network=192.168.20.0
add address=192.168.10.2/24 interface=vlan10-eth2 network=192.168.10.0
add address=192.168.20.2/24 interface=vlan20-eth2 network=192.168.20.0
/system gps
set set-system-time=no
/system note
set show-at-login=no
9

that’s not what I mean. The question is why the microtik does not forward traffic between eth1 and eth2 port
i must use 192.168.10.0 network but without bridge. is it possible ?

10

Before anything else, if you check your configuration, you will find several instances of * (asterisk) followed by a (hex) number.
This basically means that there was something there that was renamed/deleted/moved/changed in such a way that the RoS can’t find it properly anymore, so it places there a sort of placeholder.
bridge *13 and *17, interface *14, etc. in the best case do nothing, in the worse they prevent the switching or routing.
You need to correct them before going on.

11

You’ve set 192.168.10.1/24 to one interface and 192.168.10.2/24 to the other interface. Every normal device will assume these two addresses are in same subnet and hence directly accessible without explicitly using router. And bridge is here to pass traffic from ether1 to ether2 (with appropriate VLAN headers attached).

If you want to force devices, connected to ether1, to use router when talking to devices, connected to ether2, then you have to make two distinct IP networks as already suggested by @panisk0

I’m feeling a XY problem here … so why don’t you explain the task you want to do in plain English words without thinking of ROS configuration.