I have neighbors problem

Hello there;
I have a problem. I’m having a problem with my AC devices running as a client. At any time, it stops data transmission between the wireless and the Ethernet interface. I checked the log and there are no errors.

I noticed that I could not ping the ethernet and connected devices in my neighbors.

But when I close the bridge that I combine wireless and ethernet; I can see ethernet connected neighbors and I can ping.

What is my problem? I need your help.

I apologize for the bad translation.

I’m not 100% sure you have a problem without some more detail. When the bridge is active, you should be trying to ping your ethernet connected devices by specifying the bridge as the target, not the ethernet port. You don’t say whether or not you did that, so I can’t tell. Also, the IP address has to be located on the bridge itself, not the ethernet port, when the bridge is active. You also don’t say whether that’s the case.

It’s difficult to tell from the images, but it looks like when you activate the bridge you are still seeing all of your ethernet connected devices, just with the bridge name in the first column, which is as it should be.

If I’m missing something in your problem description, please ask again with more detail.


Sent from my iPhone using Tapatalk

Thank you for your interest.

A client device is running and suddenly the wireless data is not being transferred to the cable. without a certain period of time. I give the ip address to the correct ethernet but can not ping it. Sometimes when I restart it is the solution. sometimes I do not do what I do, and for a while I wait for the bridge to close and when I reopen it starts to work on its own. I do not change any settings.

All I know is that the information part in the neighbors is empty. it also looks in the pictures.

Thank you for everything.

I give the ip address to the correct ethernet but can not ping it.

When you make a statement such as this, it implies that you may not understand what I have already explained. If the ethernet is part of a bridge, directing your ping directly to the ethernet interface will never work because it has no address and the ping response will never be received. If the ethernet is part of a bridge, you must ping the bridge, not the hardware port.

I don’t understand your comment about “waiting for the bridge to close.” What does that mean, and why would it happen?

What I understand so far is that periodically you see traffic stop to or from a particular device on the bridge – not the entire hardware interface, just one device on it. If so, I believe you’re looking in the wrong place to analyze the problem.

explanation with example

also
Access Points Not Ac

I changed with ldf, sxt 5-hpnd r2 and there is no problem.

Sounds like you have determined that your “Client Netmetal 922” is faulty.

Without the ip address / routes / bridge-ports configs for the two netmetal devices, there’s little more I can do for you.

Hello

I changed the client 922. I tried Sxt 5 Ac. The result is the same. I tried QRT 5 Ac the same result. When I try QRT 5 h, there are three problems.

I have observed;

Mikrotik AC series products sometimes stop traffic between the interfaces when they are built.

First, I'm a Mac address poisoning. It was not a solution.
Then I did a loop search. It was not a solution.

When traffic is interrupted between the latest bridge port interfaces; incomplete information in the neighbors section.

Configuration;


Ap Netmetal

[admin@AP] > ip ad pr
Flags: X - disabled, I - invalid, D - dynamic

ADDRESS NETWORK INTERFACE

0 10.0.1.2/24 10.0.1.0 ether1
1 10.10.10.1/24 10.10.10.0 wlan1

[admin@AP] > in br pr
Flags: X - disabled, R - running
0 R name="bridge-local" mtu=auto actual-mtu=1500 l2mtu=1600 arp=enabled arp-timeout=auto mac-address=xxxx protocol-mode=rstp priority=0x8000 auto-mac=no admin-mac=xxxxxx max-message-age=20s forward-delay=15s transmit-hold-count=6 ageing-time=5m

[admin@AP] > in br po pr
Flags: X - disabled, I - inactive, D - dynamic

INTERFACE BRIDGE PRIORITY PATH-COST HORIZON

0 ether1 bridge-local 0x80 10 none
1 I sfp1 bridge-local 0x80 10 none
2 wlan1 bridge-local 0x80 10 none


Client Netmetal

[admin@Client > ip ad pr
Flags: X - disabled, I - invalid, D - dynamic

ADDRESS NETWORK INTERFACE

0 192.168.0.1/24 192.168.0.0 ether1
1 10.10.10.2/24 10.10.10.0 wlan1

[admin@Client] > in br pr
Flags: X - disabled, R - running
0 R name="bridge-local" mtu=auto actual-mtu=1500 l2mtu=1600 arp=enabled arp-timeout=auto mac-address=xxxx protocol-mode=rstp priority=0x8000 auto-mac=no admin-mac=xxxxxx max-message-age=20s forward-delay=15s transmit-hold-count=6 ageing-time=5m

[admin@Client] > in br po pr
Flags: X - disabled, I - inactive, D - dynamic

INTERFACE BRIDGE PRIORITY PATH-COST HORIZON

0 ether1 bridge-local 0x80 10 none
1 I sfp1 bridge-local 0x80 10 none
2 wlan1 bridge-local 0x80 10 none



No Routes rule.

Why do you have IP addresses on ether1 and wlan1 while those interfaces are part of a bridge? When interfaces are in a bridge you only add addresses to the bridge.

Yup, I’ve already explained this to him twice. I think we may have a language translation issue.