Hi.
I am using a Mikrotik modem/router combo (RBD53G-5HacD2HnD-TC&EG12-EA). I want to extend the wireless signal by another router.
So, on the new router I switch to Wireless AP and connect to Mikrotik successfully. It gets an IP from Mikrotik.
But every device connected to the new router does not get an IP address. If I set an IP manually, the the internet works.
What do I need to change in Mikrotik so it assigns the IP to other devices?
Without seeing your config and having an idea about the network the device is placed in, difficult to say.
Could it be there is no DHCP server defined for that subnet ?
Export config
Terminal: /export file=anynameyouwish
Move file to your computer
Edit and remove serial number, possible public WANIP, any passwds visible (Wifi security).
Then drop contents in between code quotes.
Most likely yes but that will be a consequence of the config you applied (or did not apply) for the setting you placed that device in.
And without seeing that config … we can all guess.
I switch to Wireless AP and connect to Mikrotik successfully. It gets an IP from Mikrotik.
Guesing guessing , I assume you connected the Wireless AP with it’s WAN port (having a DHCP client on that interface) so that this Wireless AP gets an IP address from the router/modem (as an ethernet client of the router/modem combo).
To have the wireless clients of the Wireless AP to also be part of the router/modem combo network , the connection has to be LAN-LAN, and LAN interfaces should be bridged. Then you have one L2 network, with the modem/router combo assigning IP addresses and functioning as gateway for the whole LAN.
I am connected to Mikrotik wirelessly, and Mikrotik should handle DHCP.
For example, the Wireless AP has IP x.x.x.10
In Mikrotik control panel I can see it connected, it has MAC address 11:11:11:11:11:11 and assiged IP x.x.x.10.
When I connect with my phone to Wireless AP and manually assign IP to x.x.x.20, in Mikrotik control panel there is still only one device connected with Wireless APs MAC address 11:11:11:11:11:11 but the IP is alternating between x.x.x.10 and x.x.x.20.
So, it seems like Mikrotik assigns the IP to Wireless AP, but it does not detect any other device connected to it.
To rule out the Wireless AP router, I connected it to a TP-Link router, and it assigned IP to every device connected to Wireless AP.
Confusing all the time. You have a Mikrotik Chateau (RBD53G-5HacD2HnD-TC&EG12-EA), which by the way is a Mikrotik and a Wireless AP (with also LTE connection)
Then you speak about a Wireless AP (another? name it or number it), and about a Mikrotik (which one, the Chateau is a Mikrotik, the Wireless AP is one as well? Yet another Mikrotik?)
.
Hi.
I am using a Mikrotik modem/router combo (RBD53G-5HacD2HnD-TC&EG12-EA) [DEVICE 1] . I want to extend the wireless signal by another router. [DEVICE 2]
So, on the new router [DEVICE 2 ?] I switch [DEVICE 3?] [ switch the setting or connect to?] to Wireless AP [Which one, 1 or 2] and connect to Mikrotik [ which one 1 or 2?] successfully. It gets an IP from Mikrotik [aaargh which one ? ].
But every device connected to the new router [ DEVICE 2] does not get an IP address. If I set an IP manually, the the internet works.
Sorry too confusing to understand what the connections and setup are.
router [DEVICE 1] connected by ethernet or wireless to the new Wireless AP [DEVICE 2] This second Wireless AP is a Mikrotik or not? Is set in Repeater mode or what setup? Connected to WAN port of [DEVICE 2] Wireless AP , or LAN port, or wifi (AP bridge-station bridge wifi connection or other?)
Not getting a DHCP lease for an IP address is very common in a wifi repeater setup, with the primary AP set as mode “AP” (not mode “AP bridge”) , and the second AP (functioning as repeater) connected with mode “station pseudobridge”. Standard wifi does not forward the destination MAC address in a wifi extension setup.
And “station pseudobridge” is known to fail in some cases, as the DHCP offer for the hidden MAC address is not sent over wifi. The known workaround is to use a static IP address.
The combination of wifi modes “AP bridge” and “station bridge” can make a good bridged wifi network with Mikrotik devices only. This is as good L2 as an ethernet bridged LAN-LAN connected setup.
The other solution is to have a routed connection with NAT. The second Wireless AP [DEVICE 2] (Mikrotik or TP-Link) then has a WAN connection to the first AP [DEVICE1] . [DEVICE 2 has its own DCHP server and hands out IP addresses to its client devices. The connection to Internet for client devices is towards the [DEVICE 1] link, and on that link IP connection requests carry the same IP and MAC address of [DEVICE 2] for all its client devices.
And to confuse everyone here … in the case of a wifi link with modes “AP” and “station pseudobridge” the IP connections over the wifi link between [DEVICE 1] and [DEVICE 2] are all with the same MAC address but different IP addresses.
I was struggling with it for the first time a week ago (but “bridge” - “station bridge” configuration in my case). Maybe not struggling with wireless bridge itself, but doing a “wireless trunk” on it, damn, it was frustrating - but satisfying after all
A small offtop, I know, but I guess bad AP - Client operation mode could be the main issue here.
The word Bridge is used so often in RouterOS, it is very confusing.
In the router acting as AP the wifi should be in mode “AP bridge”. If wifi is set in mode “Bridge”, it will only accept 1 (one) client device. This is used in RouterOS devices with a low license level (level=3), to keep them cheaper.
Having VLAN trunk over a “AP bridge - bridge” wifi connection is no problem. Don’t set VLAN on Bridge (yes that other bridge word) or on the WLAN interface (as use VLAN tag)
It’s exactly what I wanted to do - wireless communication between two points (it’s not possible to use cable), it’s not an AP for other devices like laptops, phones or other MT clients.
Having VLAN trunk over a “AP bridge - bridge” wifi connection is no problem. Don’t set VLAN on Bridge (yes that other bridge word) or on the WLAN interface (as use VLAN tag)
I achieved it by:
combining wlan1 and ether1 in one bridge,
adding VLAN interfaces under the bridge (with VLANs tags specified in their configuration),
setting Bridge / VLANs tab as follows (for example for VLAN 100):
tagged on ether1 and wlan1
untagged on vlan100
(management VLAN is tagged also on bridge itself so I can access the devices),
enabling VLAN filtering on that bridge.
It is working perfectly, I tested in on my desk, but I’m open for suggestions or better solutions. Remember that it’s just point to point wireless communication:
Switch trunk port → MT wireless point 1 → MT wireless point 2 → switch trunk port.
Nothing more or less between them.
That was just my simple start case … work as a “dump switch”. A “dump switch” is unaware of VLAN, and just passes them along.
Of course once you master the VLAN settings as a VLAN aware bridge, it is very good to use it. You can better control the flow, and do tag/untag in the bridges.
Understood, thank you
And once again sorry for the author that I’ve done some “research” in your topic, you never know when you have an opportunity to learn something, I just took my chance