Main Router RB2011UiAS-2HnD manage DHCP and Primary for ethernet and WAN, secondary one wifi for two clients which ar not in range from AP
cAP ax connected via eth to Router, there are 3 wifi configured 1x 5ghz own SSID and 2x 2ghz with sameme SSID first for wpa2 second for wpa3 because when set wpa 2 and 3 at same security clients have problems to connect
mAP used as client bridge, connected to the 2ghz wifi from cAP and one client at eth1.
Now my problem the client on mAP didn't get an IP from the main router
Hello and thank you for the quick reply! Yes, I did that if I remember correctly. Otherwise, the MAP was not accessible via the normal network. Only here, as I took the interface out of the bridge and set Manuel to LAN, was I able to establish a connection here, but I will test it again.
Yep, but there are other things that seem to me "off" in your configuration.
The DHCP client (where needed[1]) should be running on the bridge1, not on the wlan1.
Since wlan1 is (correctly) part of the bridge, it doesn't really exist anymore externally.
And the DHCP relay should not be needed at all, your setup corresponds - in theory - to a "dumb" switch of which one of the ports happens top be a wireless link, since the pseudo-bridge being not a "proper bridge", it may actually need it, but I wouldn't be so sure.
As well proxy-arp - if actually needed - should be only on the outside of the box (the bridge) contining the various interfaces and not on the single interfaces that are part of the bridge.
A common recommendation is also to assign manually a MAC to the bridge interface.
Since they are not used anywhere, the categorization of interfaces is also redundant/unneeded, i.e. you can remove:
/interface list
add name=WAN
add name=LAN
/interface list member
add interface=wlan1 list=LAN
add interface=ether1 list=LAN
add interface=ether2 list=LAN
add interface=bridge1 list=LAN
(but this is only cosmetic)
[1] if you use (as you should) Winbox 3 to access that mAP, you don't even need to have an IP assigned, and connect via MAC instead:
BTW there are several reports of issues with Webfig with 7.20.4, yet another reason to use Winbox.
This newish 7.20.x releases are being reported as being flaky in several functions, but it would be strange that a basic thing like DHCP server/client is not working.
How are you connecting to the mAP (via ether port), with winbox via MAC, right?
So the mAP doesn't get an IP address but the cAP does get one?
Anything in log of the mAP (possibly after a reboot), related to dhcp?
Can you try (only as an experiment) to connect the mAP to the cAP via ethernet cable, let's say on ether1 of the mAP, and connect the PC to port ether2 of the mAP?
Most probably unrelated, but this (on the main router) is not advised:
/interface detect-internet
set detect-interface-list=all
should be disabled:
/interface detect-internet
set detect-interface-list=none
today i have do some tests
reset mAP –> delet configuration
when connect to eth2 from cAP evrey thing fine mAP get IP adress with client on bridge
next step
eth1,eth2, wlan1 –> parts of bridge –> ip client get no IP
eth1, eth2, –> part of bridge –> ip client listen on wlan1 and get IP –> Bridge and wlan interface list set to LAN
Client on eth1 with fix ip for test can be reached with ping from mAP
Can’t be pinged from my PC connected on eth2 from mAP
If you reset the mAP, and do NOT make ANY change EXCEPT the wifi (station-pseudobridge) and SSID credentials settings, what is the config?
Should have wlan1 and ether2 assembled into a bridge (LAN) and ether1 set as WAN (and firewall rules and NAT) but if we ignore this latter part, disable the dhcp server and simply add a dhcp client on the bridge, the bridge should get an IP both when the mAP is connected to the cAP via ether2 and when it is instead connected to it via wlan1.
If this doesn't happen, comparing logs when the connection is through ether2 and when it is via wlan1 should show some differences.
At this point, if I were you I would downgrade the software to an earlier surely working release, up to you if going for 7.19.6 or an earlier one, I am starting to suspect that it is actually a release-dpendent bug.
So, I tried connecting a second mAP since downgrading the first one wasn't possible.
Unfortunately, the second mAP is exhibiting the same behavior with the old firmware.
As soon as all ports are part of the bridge, the bridge doesn't receive an IP address. However, if the WLAN port isn't part of the bridge, it does receive an IP address.
I think the problem occurs on the cAP or the main router. Perhaps something is blocking the connection, preventing only individual clients from connecting to the WLAN and not the bridge?
I don't really understand your configuration for those, it seems to me like you have them half configured for capsman/cap but with capsman not enabled (capsman address set to 127.0.0.1 on the cAP?).
The datapath settings you have are not common in a non-capsman setup, but I am not familiar enough with them to suggest whether these could cause issues or not.
But it is strange that the standalone wlan1 gets the IP and the bridge does not.
Yep, no station-bridge, but station-pseudobridge should work, this latter has limitations, but you have only one client attached to the mAP, and it should support IP based protocols, so ...
You could try assigning manually to the bridge on the mAP the same MAC as the wlan1 interface, but no idea if it would help, maybe your current "auto" setting detects multiple MACs in the bridge and freaks out.
And I would remove the arp=proxy-arp setting, too.
