Problem in the trunk passing through the wireless link

[chpmotry]

hi guys.

I have several local networks that are far from each other and separate from each other. Mikrotik radio is used in all of them to communicate with the units that are less than a hundred meters away from the main rack room. When I put the communication port of the switches that are connected to the wireless link in the trunk state, the clients of the units that are connected to the network with the radio get the IP address from the switch, but the ping of the radios is interrupted. As soon as I put the switch port that is connected to the radio link in access mode and in vlan 2, the ping of the radios is established.

Why does this happen and what is the solution?

[Flavio Miranda]

@chpmotry 

 Seems to me the Mikrotik does not undestand vlan tag (trunk).

 If you are configuring IP address and route on the Mikrotik, why dont you configure it as layer3 instead layer2 and route the traffic?

I would not use "ip default-gateway" on the switch but static route instead.

[chpmotry]

thank you flavio for your reply

i have many links with mikrotik radio such as basebox 5 and dynadish 5 that with the same configuration ,They passed the trunk traffics from cisco switches such as 2960x and cbs350 and 2960G

[Flavio Miranda]

I dont doubt that, after all 802.1q is a very common and supported protocol but, sticking with the decription you provided, that seems to me you have a problem with tag.

 In your diagram we can see trunk with native vlan 2. Does that work?

[chpmotry]

it doesn't work. in this state , Clients get ip from DHCP of core switch  , but there is no news from ping of wireless link radios.

[Flavio Miranda]

It is the core switch the one I highlighted?

[chpmotry]

The core switch is the one where the dhcp pool is defined.

The switch that you highlited it is only for troubleshooting the network

[Flavio Miranda]

Ok but If client is able to get DHCP when the switch is in trunk mode, this means the communication is happening. The bridge is actually understanding tag for user traffic.

 It seems then the bridge management interface does not understand tag.

 This also happen with Cisco AP. But with Cisco we can fix by using Native vlan.

[amikat]

Hi,

I can see both sides using the same int vlan 3 address (192.168.3.1/24) at your diagram. When configuring trunk I suggest to delete int vlan 3 interface at the 2960G box.

Best regards,

Antonin

[chpmotry]

Thank you @amikat.

It is only a Inadvertent mistake in prepare the picture of network schematic.