Community discussions

MikroTik App
 
JdccDevel
just joined
Topic Author
Posts: 4
Joined: Mon Mar 07, 2022 6:38 pm

VLAN IP not responding

Fri Sep 06, 2024 5:57 pm

I'm experiencing strange behaviour when trying to configure a Management VLAN interface on a switch.

I'm hoping I just missed something simple in the config?

I've included an modified sample config which exhibits the problem. (Note: device specific details removed.)

VLAN 2048 tagged traffic is passing through the switch (i.e. devices on either side can talk to each other) but none of them can see the IP that's configured on that VLAN interface on the switch. (192.168.1.10 in this config)

That is, UNTIL the switch performs an outgoing ping. Then it (just that device that was pinged) can talk to the Switch on the Vlan IP.

To reproduce the issue:
(Note: All packets tagged using vlan 2048, 192.168.1.1 connected to sfp-sfpplus16, 192.168.1.2 connected to sfp-sfpplus12)
1) 192.168.1.1 pings 192.168.1.2 => Success
2) 192.168.1.1 pings 192.168.1.10 => Fails
3) 192.168.1.10 (Switch) pings 192.168.1.1 => Success
4) 192.168.1.1 pings 192.168.1.10 => Now success
5) 192.168.1.2 pings 192.168.1.10 => Still Fails.

It looks to me to be some sort of ARP issue? From what I can see, the switch never responds to an ARP request for its IP on VLAN 2048. Pinging out updates the arp cache on the target device, so it can ping back.

To summarize:
Devices on vlan 2048 (192.168.1.0/24 subnet) cannot ping the switch on the IP 192.168.1.10
Untagged and/or Vlan 101 traffic can ping the switch on the IP 192.168.0.60 just fine.

Model: CRS317-1G-16S+
ROS Software version: 7.15.3
You do not have the required permissions to view the files attached to this post.
 
JdccDevel
just joined
Topic Author
Posts: 4
Joined: Mon Mar 07, 2022 6:38 pm

Re: VLAN IP not responding

Fri Sep 06, 2024 7:28 pm

Looks like it was something simple, perhaps the issue is that it worked at all?

I had forgot to add the Bridge interface itself into my VLAN config as a tagged port.

The VLAN interface is attached to the bridge, and the bridge needs to be a member of the VLAN for the tagged packets to be recognized by the VLAN interface.

I confirmed on a second switch. Adding the Bridge to the VLAN config as a tagged port, under Bridge->Vlans seems to have fixed my issue.

Note, I'd previously tried adding the Vlan interface to the Vlan bridge config as a tagged port and that hadn't worked.

Who is online

Users browsing this forum: No registered users and 54 guests