![]() ![]() OFF meant something different than expected. The Linksys was sending a DHCP NAK for every DHCP request that was sent out. Once had a Linksys Home gateway WRT54G used as switch only, with DHCP server OFF, connected to the office network The whole department lost connection. Have to check RE450 again! DHCP server is OFF, not auto ?. Can login via 元 web to the MQS.ĭifference is the MQS DHCP server is OFF. There I see the IP address leased to the MQS. (Hope mAP was faster than MQS, and MQS has taken IP address). With the default configuration (DHCP client with fallback, no DHCP server), connected to a mAP Lite with default settings for the DHCP server (except IP address range). UPDATE: the RBMQS seems all to be a matter of sequence and timing. If that one works, then there is a simple all-Mikrotik case May do some test later with a different DHCP server. Very similar to the 2.5bridge (universal repeater, pseudostation bridge. #TP LINK REPEATER SOFTWARE#Software is not very clear, but that device does not allow for a Mikrotik DHCP lease between wifi and ethernet. A Mikrotik device to make the wifi-ethernet transition. My newest experience is with the Mikrotic MQS. #TP LINK REPEATER MAC#The broadcast is using IP 255.255.255.255 OK, but the MAC address is not FF:FF:FF:FF:FF:FF, so it does not pass the repeater. The idea of Mikrotik DHCP to broadcast the last step if it fails, is not good enough. DHCP address leases over halfbridges (2.5, changing the source MAC address in the in some packets, but sometimes not relaying broadcast packets) seems a delicate procedure. And therefore claim there is probably no problem but only wrong configuration by the customer. and there are many discussions with Mikrotik, who seems not to be able to reproduce the problem. ![]() Other DHCP servers do work with some of these other repeaters (like Edimax) where Mikrotik fails. However there are cases where only the DHCP server from Mikrotik fails to lease an ip address. The TP-link repeater is the device showing the problem in a consistent way, it fails also for some other DHCP servers. Other repeaters like Engenius ENS202EXT and Draytek AP810 do this without any problem. It looks like the RE450 is not handling DHCP requests as it should. other than 1/6/11 ) this strongly reduces the usefullness of the RE450. Together with the lack of control of the used wifi channel in the RE450 (it's always auto and it assigns overlapping channels, eg. It also needs some reverse engineering of the IP plan of the original AP in all other cases. The wokaround with the DHCP served from the RE450 is not usable in a multi-user environment where IP address control is part of the LOGIN/passthrough authorisation. The client never gets a proper IP address. There is never an answer on the ARP request and the DHCP IP address is dropped by the DHCP server, it does not come to the "bounded" status, as it does if the client is connected directly to the hAP wifi. And the RE450 should answer that request (as a 2.5 half-bridge) with it's own MAC address (proxy ARP) or at least pass it on to the DHCP client. #TP LINK REPEATER VERIFICATION#But then the router does a verification with a broadcasted ARP request for that IP address. Handing out and receiving the DHCP IP address goes well. It lasts 30 seconds (status offered) and then disappears.īy using the Sniffer tool in the hAP the handshake can be followed. I can see the DHCP offering from the Mikrotik hAP in the DHCP server leases list. (This same problem also applies with the RE450 and a Draytek Vigor 2132 router). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |