MikroTik

Posted: **Wed Mar 15, 2017 12:21 pm**

RB1100AHx2 ver 6.38.3(stable)
dhcp client Windows 7 (some Lenovo laptop) cant get dynamic IP from router.

log picture in attachment

if you need more info please let me know.

Posted: **Wed Mar 15, 2017 12:44 pm**

Have you tried 6.37.5?

Most useful info for these issues is a packet capture, see https://wiki.mikrotik.com/wiki/Manual:T ... et_Sniffer that way actual "conversation" between ROS and client can be followed.

You may also enable dhcp debugging: go to System > Logging then add a new rule with Topics=dhcp and action=disk so that you can easily filter other logging by setting disk dropdown on log view.

Posted: **Wed Mar 15, 2017 2:52 pm**

on version 6.37.5 i have problems with CAPSMAN and CAP devices (they can't connect), but this is another story.

dhcp debug response from logs

Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug: dhcp1 received discover with id 2626241787 from 0.0.0.0
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     ciaddr = 0.0.0.0
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     chaddr = 1C:39:47:EC:8B:F4
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Msg-Type = discover
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Client-Id = 01-1C-39-47-EC-8B-F4
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Host-Name = "DMIdea"
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Class-Id = "MSFT 5.0"
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Router-Discovery,Static-Route,Vendor-Specific,NETBIOS-Name-Server,NETBIOS-Node-Type,NETBIOS-Scope,Classless-Route,MS-Classless-Route,Auto-Proxy-Config
Mar/15/2017 14:52:40 dhcp,warning dhcpDebug: dhcp1 offering lease 10.10.10.81 for 1C:39:47:EC:8B:F4 without success
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug: dhcp1 sending offer with id 2626241787 to 10.10.10.81
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     ciaddr = 0.0.0.0
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     yiaddr = 10.10.10.81
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     siaddr = 10.10.10.1
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     chaddr = 1C:39:47:EC:8B:F4
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Msg-Type = offer
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Server-Id = 10.10.10.1
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Address-Time = 29400
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Subnet-Mask = 255.255.255.0
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Router = 10.10.10.1
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Domain-Server = 10.10.10.1
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug: dhcp1 received request with id 2626241787 from 0.0.0.0
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     ciaddr = 0.0.0.0
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     chaddr = 1C:39:47:EC:8B:F4
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Msg-Type = request
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Client-Id = 01-1C-39-47-EC-8B-F4
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Address-Request = 10.10.10.81
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Server-Id = 10.10.10.1
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Host-Name = "DMIdea"
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Client-FQDN = 00-00-00-44-4D-49-64-65-61
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Class-Id = "MSFT 5.0"
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Router-Discovery,Static-Route,Vendor-Specific,NETBIOS-Name-Server,NETBIOS-Node-Type,NETBIOS-Scope,Classless-Route,MS-Classless-Route,Auto-Proxy-Config
Mar/15/2017 14:52:40 dhcp,info dhcpDebug: dhcp1 assigned 10.10.10.81 to 1C:39:47:EC:8B:F4
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug: dhcp1 sending ack with id 2626241787 to 10.10.10.81
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     ciaddr = 0.0.0.0
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     yiaddr = 10.10.10.81
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     siaddr = 10.10.10.1
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     chaddr = 1C:39:47:EC:8B:F4
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Msg-Type = ack
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Server-Id = 10.10.10.1
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Address-Time = 29400
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Subnet-Mask = 255.255.255.0
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Router = 10.10.10.1
Mar/15/2017 14:52:40 dhcp,debug,packet dhcpDebug:     Domain-Server = 10.10.10.1
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug: dhcp1 received request with id 2626241787 from 0.0.0.0
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     ciaddr = 0.0.0.0
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     chaddr = 1C:39:47:EC:8B:F4
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Msg-Type = request
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Client-Id = 01-1C-39-47-EC-8B-F4
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Address-Request = 10.10.10.81
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Server-Id = 10.10.10.1
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Host-Name = "DMIdea"
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Client-FQDN = 00-00-00-44-4D-49-64-65-61
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Class-Id = "MSFT 5.0"
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Router-Discovery,Static-Route,Vendor-Specific,NETBIOS-Name-Server,NETBIOS-Node-Type,NETBIOS-Scope,Classless-Route,MS-Classless-Route,Auto-Proxy-Config
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug: dhcp1 sending ack with id 2626241787 to 10.10.10.81
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     ciaddr = 0.0.0.0
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     yiaddr = 10.10.10.81
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     siaddr = 10.10.10.1
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     chaddr = 1C:39:47:EC:8B:F4
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Msg-Type = ack
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Server-Id = 10.10.10.1
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Address-Time = 29397
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Subnet-Mask = 255.255.255.0
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Router = 10.10.10.1
Mar/15/2017 14:52:44 dhcp,debug,packet dhcpDebug:     Domain-Server = 10.10.10.1
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug: dhcp1 received request with id 2626241787 from 0.0.0.0
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     ciaddr = 0.0.0.0
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     chaddr = 1C:39:47:EC:8B:F4
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Msg-Type = request
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Client-Id = 01-1C-39-47-EC-8B-F4
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Address-Request = 10.10.10.81
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Server-Id = 10.10.10.1
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Host-Name = "DMIdea"
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Client-FQDN = 00-00-00-44-4D-49-64-65-61
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Class-Id = "MSFT 5.0"
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Router-Discovery,Static-Route,Vendor-Specific,NETBIOS-Name-Server,NETBIOS-Node-Type,NETBIOS-Scope,Classless-Route,MS-Classless-Route,Auto-Proxy-Config
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug: dhcp1 sending ack with id 2626241787 to 10.10.10.81
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     ciaddr = 0.0.0.0
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     yiaddr = 10.10.10.81
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     siaddr = 10.10.10.1
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     chaddr = 1C:39:47:EC:8B:F4
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Msg-Type = ack
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Server-Id = 10.10.10.1
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Address-Time = 29388
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Subnet-Mask = 255.255.255.0
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Router = 10.10.10.1
Mar/15/2017 14:52:53 dhcp,debug,packet dhcpDebug:     Domain-Server = 10.10.10.1

Posted: **Wed Mar 15, 2017 4:04 pm**

Maybe my topic is the same as General->"ROS 6.38 serious DHCP server problem".

Posted: **Wed Mar 15, 2017 7:21 pm**

Yes, could be related.

Try running wireshark on that windows machine, to see if the mikrotik offers are getting received on the windows interface.

You can run 6.37.5 on the CAPsMAN controller with 6.38.5 CAPs... verified.

Posted: **Thu Mar 16, 2017 11:22 am**

if that session is enough? (please see attachment).
as i can see Windows PC only sent discover.

dump file in gzip archive

Posted: **Thu Mar 16, 2017 11:34 am**

but from my PC with Ubuntu Linux in same subnet it looks normal.
picture in attachment. very strange for me

Posted: **Thu Mar 16, 2017 11:44 am**

As I suspected, the windows machine isn't receiving anything.

ROS -> Lenovo communication works, but Lenovo -> ROS doesn't.

Possible causes:

- problem with 6.38 L2; if DHCP server is run on a bridge, try disabling RSTP on it. Try (for a test) to set up a standalone DHCP server on a single ether and plug the lenovo there, does it make a difference?

- Try a different driver on Lenovo laptop. Make sure there's nothing unusual in its ethernet configuration.

- Try disabling the drop invalid firewall rule on input chain.

Posted: **Fri Mar 17, 2017 10:11 am**

tested with another device HAP ac(v6.38.3 and v6.38.5)
PC directly connected over LAN cable, routeros with default settings. same Windows PC only sent discovery packet and no answer from router.

maybe is is broken LAN card in PC.

Posted: **Fri Mar 17, 2017 12:37 pm**

I had similar issue with HP laptop. Mikrotik offered IP but laptop never get it.

Solution was to turn OFF bootp on DHCP server.

Posted: **Mon Mar 20, 2017 9:29 am**

i have changed MAC address in LAN card driver and now it worked ~ 5 min. after same result "dhcp1 offering lease XX:XX mac wihout success.". How i can find where this MAC address is blocked or something similar?

Thanks.

Posted: **Mon Mar 20, 2017 12:54 pm**

I'd say 6.38 related... generate a supout with a new mac address (working) and another while DHCP is not working and submit it to support.

Posted: **Tue Mar 21, 2017 8:17 am**

On a VLAN? Set the MTU to 1504.

Posted: **Tue Mar 21, 2017 8:58 am**

Last news.
Upgraded firmware to version 6.38.5, disabled rstp on brige interface. and problem still exist. will start meeting with support.

(but currently my CAPSMAN is working)

Posted: **Tue Mar 21, 2017 1:44 pm**

You can test 6.37.5 only on the CAPs manager...

Posted: **Wed Mar 22, 2017 9:40 am**

morning,
tested with version 6.37.5 on HAP ac with default config. same results "defconf offering lease without success"
please see big picture in attachment.

Posted: **Wed Jul 12, 2017 8:39 pm**

hi niemi, Did you manage to solve the problem of DHCP server offering lease without success?

regards

Posted: **Wed Jul 12, 2017 9:34 pm**

Try setting authoritative=yes on DHCP Server settings. Reboot advised.

Posted: **Wed Jul 12, 2017 10:05 pm**

A duplicate client MAC could cause this.
While it's failing, check the arp table on the Mikrotik. It's under Switch > Host, or Switch > FDB. It should show your PC's mac address as being down one of the interfaces.
Tools > Packet Sniffer on the Mikrotik will also show if the Mikrotik is in fact actually sending the offer. Check the dst-mac of the offer packet, it should be your PC.

Posted: **Wed May 08, 2019 12:53 pm**

Hi Guys,
I'm having this error, Has everyone fixed it yet? Router OS: 6.44.3
Thanks Guys!!

Posted: **Fri May 10, 2019 12:09 am**

For me solution was easy and I've made this complicate because I've followed all instructions in thread, reset RMPro remote control (now need to spend at least 2 hour to configure all devices again), changed all DHCP settings, etc etc etc ...

Well, final solution for me was :
get back from 6.44.3 to 6.42.6 and everything is working fine.

btw.
Spent additinal 30 minutes by trying to reset password on THIS site, I know old email but don't remember username :
- when I am trying to reset password this is asking for username which I don't remember
- when I am trying to register new account this say email is already used (yes, I know, but HOW to use this email ...)

and yeah, I am upset with my "let's upgrade this" right now

Posted: **Mon Jun 03, 2019 7:18 am**

For me solution was easy and I've made this complicate because I've followed all instructions in thread, reset RMPro remote control (now need to spend at least 2 hour to configure all devices again), changed all DHCP settings, etc etc etc ...

Well, final solution for me was :
get back from 6.44.3 to 6.42.6 and everything is working fine.

btw.
Spent additinal 30 minutes by trying to reset password on THIS site, I know old email but don't remember username :
- when I am trying to reset password this is asking for username which I don't remember
- when I am trying to register new account this say email is already used (yes, I know, but HOW to use this email ...)

and yeah, I am upset with my "let's upgrade this" right now

Look like I got the same problem with 6.44.3

Posted: **Tue Jun 04, 2019 5:19 am**

I found the issue that may be due to compatibility between the latest ROS DHCP driver and ethernet hardware/driver. In my setup of x86 hardware, I used to use routerOS KVM to create a virtural network interface for my linux client. The default network interface is based on redhat virtio.

Under the latest firmware, it can get network ip when boot up but somehow it loses its ip upon renewal. That means the client is not connecting to network or internet.

When I look back the KVM wiki, it found that the virtual network interface can be created to emulate e1000. When I re create a separate virtual network interface with hardware emulation to intel e1000, IP address renewed was successful. I did not make any setting changed under routeros DHCP server nor downgrade the firmware to a lower version as described above by other users.

But I have to monitor the situation for a longer period of time.

Posted: **Wed Jul 03, 2019 10:13 pm**

Any news?

Posted: **Thu Jun 18, 2020 6:32 am**

Same problem with Android TV and v 6.47, moreover, when TV is conneted, it jams other hosts somehow (no network access). "DHCP offered without success"
Nothing to to with bootp or authoritative options, that's a bs**t.

Posted: **Tue Aug 25, 2020 6:10 am**

Hello guys, after a lot of research on this problem that is taking the peace of thousands of people here on the forum regarding the DHCP Bug mikrotik (offering lease without success), I decided to speak up and carry out this outburst. From what I understand this bug affects all versions above 6.38.7 and it seems that there is nothing, nothing that can be done to solve this problem; with regard to the mikrotik people, it is absurd that no engineer or programmer is going to speak publicly about it.

Well, let's go to the resolution of the facts, let's go to the origin of this problem, which seems to be the masking of MAC ADDRESS.

Here I use a DD-WRT router in AP BRIDGE mode (ROUTED), in this mode this equipment is absolutely unable to pass the true mac address of the clients that are dependent on it, this generates a MAC duplication for the DHCP service to which it understands how to were it an attempt to duplicate or clone or attempt to breach because of this mikrotik displays the following error message:

defconf offering lease 192.168.10.xxx for 00: 30: 18: xx: xx: xx to 10: FE: ED: xx: xx: xx without success

So far so good, but this is a problem for those who use the MAC masking system, and in my view it seems that there is no minimum interest from mikrotik in solving this problem, or that at least it could create a LEGACY DHCP option that could handle MAC masking. I sincerely hope that mikrotik can help us, because as well as the other colleagues we are already discouraged from these bugs and these errors.

Posted: **Mon Sep 07, 2020 2:29 am**

Same issue as Rafaelholeva. I tried anothers routers and works without problems, I spent a lot of hours searching for a solution and nothing.

Posted: **Wed Oct 21, 2020 10:07 am**

Same here, many hours to finally find this out, this is nuts. I can see in logs the request. Is MikroTik at least looking at this?

What gets me is I have a wAP ac connected to a Cisco switch and a Hex router connected to same switch for internet. The wAP ac unit has the default vlan (1) and a second vlan (20). On my Cellphone via wi-fi I can get an IP address from dhcp server on Hex when I connect to ssid that is mapped to vlan1 but when I associate with other ssid mapped on vlan 20, I never get the address. All is configured correctly and I can see the request in the logs of the Hex.

Has anyone gotten a wAP ac to work with multiple ssid's mapped to multiple vlans?

TIA

Jerry

Posted: **Fri Oct 23, 2020 6:00 pm**

Hello,

Thank you for contacting MikroTik Support.

It looks like you have created a VLAN interface on the secondary (ether) interface rather than the primary (bridge) interface on the wAP ac.

If you are looking for VLAN filtering between bridge ports and tagged/untagged port configuration, perhaps take a look on the bridge vlan-filtering option:
https://wiki.mikrotik.com/wiki/Manual:I ... _Filtering
https://help.mikrotik.com/docs/display/ ... VLAN+Table

Best regards,
Edgars P.

Posted: **Fri Oct 23, 2020 6:28 pm**

No sympathy for anyone that uses vlan1 and further no sympathy for anyone using vlans and has the bridge providing DHCP services. Associate the DHCP services to the vlans and leave the poor bridge alone (so it can focus on bridge ports and bridge vlan filtering) ;-)

Yeah its that kind of hard ass Friday.
If you follow this guide and you still have issues then the firmware is really borked!!
viewtopic.php?t=143620
(yeah the wiki sucketh)

Posted: **Thu Oct 07, 2021 2:46 pm**

Recently encountered 2 cases of this problem in my network. Both of them were unrelated to RouterOS.
In one case, it was unconfigured tagged port for VLAN on an intermediate switch.
In another one it was broken LAN card driver on end PC due to damaged HDD.
Please check your end devices before suspecting bugs in RouterOS

MikroTik

DHCP server offering lease without success

DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success

Re: DHCP server offering lease without success