We have a WLAN bridge with Mikritik devices. Netbox5. So far everything is working except for the errors in connection with radar detection…
However, every day I now see in our two VMWare servers that the slave device is trying to occupy the IP addresses.
A duplicate IP address was detected for 192.168.100.xxx on interface vmk0. The current owner is 48:…
I already had a ticket with a Miktrotik technician but he also did not find the reason for this.
Does anyone have an idea?
What is the wireless interface mode on the Mikrotik device that is not an AP?
Station pseudobridge ? Do you mean that point ?
DHCP Server and Client are disabled.
Station pseudobridge carries a maximum of 3 Mac addresses, so you will have a ma address masking if you have multiple devices
Does that mean for me or the problem?
Since both devices are Mikrotik ones, change the mode from station-pseudobridge to station-bridge and do the other required settings and the issue will be gone. The 802.11 standard did not anticipate there could be multiple devices behind a wireless station so the “sender MAC address” and “source MAC address” are not separate fields in the radio header. By switching to station-bridge, the station will use a proprietary radio frame format that has dedicated fields for both MAC addresses in both directions.
Super thanks ! What do you mean with the other settings ?
I mean https://help.mikrotik.com/docs/spaces/ROS/pages/122388518/Wireless+Station+Modes#WirelessStationModes-Modestation-bridge - on the AP side, you have to double-check that bridge-mode is set to yes. You can also switch the mode on the AP side from ap-bridge to just bridge as you only have a single station-bridge connected to it.
OK thanks! Both setting are now changed. I will let you know if the ip war is over 
Unfortunately, the problem has not been solved. The device still tries to reserve almost all IP addresses… This morning the logs of the devices and switches are full of them. I have now switched it off, only that helps at the moment
Maybe I’ve misunderstood the original issue? From what I got you were seeing DHCP requests to come from the MAC address of the remote Mikrotik, with different Client-ID values to they were server with different IP addresses. Is that the case or something else was actually happening?
After switching the remote Mikrotik to station-bridge mode, does it look the same? If yes, can you run /tool sniffer quick port=68 interface=wlan1 on the AP, start the remote device, let it run that way for 5 minutes, then /tool sniffer save file=dhcp.pcap and use Wireshark to see in the file what is going on?
In addition: does any of LAN infratructure devices have proxy-ARP enabled? I see many people enable it without understanding what it does and then run into problems caused by it.
I have two VMware servers which are constantly unreachable and the log shows that a device with the MAC address of the Mikrotik Slave WLAN Adapter with the same IP address as the servers has been detected. The same happens with other servers and devices. These are all fixed IP addresses and are outside the DHCP range. When I switch off the slave device, this interference stops immediately.
on the Slave Log ether1: bridge port received packet with own address as source address (48:a9:…), probably loop
under Interface - Ethernet - is ARP Enabled but i cant find proxy arp ?
arp is the parameter, proxy-arp is the value. The wireless interface of the remote Mikrotik is probably a member port of a bridge, and the arp setting on that bridge is important.
So what should i do now ?
It is a bridge yes. But with this error i cant use this devices.
Otherwise i have to sold it and try other manufacturer.
So i have now activated the loop protection:wlan1: bridge port received packet with own address as source address (48:a9:8a:e4:e6:9d), probably loop
I dont know whats happend in the devices ! there is no physicaly loop
And i think the configuration is one of the smallest see picture
Post the export of the configuration of both Mikrotik devices, after removing serial numbers, public addresses and eventual usernames to external services. And describe what is the overall network topology (at both ends of of the wireless link), as that determines what are tne requirements on the wireless equipment.
The command is /export hide-sensitive file=siteA. In RouterOS 7, hide-sensitive only exists for backward compatibility as it is the default behavior, so if it is not accepted, you are running an old version of ROS 7 - just omit the parameter.