RT-AC66U - 3.0.0.4.374.35_4, DHCP flood

[Lukapple]

Hi.
I’ve RT-AC66U with Merlin build 3.0.0.4.374.35_4 (main router) and another router (Linksys wrt-54gl, DD-WRT v24-sp1), that is running in “repeater bridge” mode. Routers are connected with wi-fi connection.

I’ve noticed strange things in 3.0.0.4.374.35_4. Linksys router started to flood my dhcp server and eat my IP addresses. There are 100+ clients with linksys’s mac address - see attached picture.

Could this be a bug in .35_4 ?

 

[krum]

If you have windows 7 machines
http://brielle.sosdg.org/archives/522-Windows-7-flooding-DHCP-server-with-DHCPINFORM-messages.html

aslo

http://forums.smallnetbuilder.com/showpost.php?p=74640&postcount=6

or the best solution

http://forums.smallnetbuilder.com/showpost.php?p=74642&postcount=8

 

[Lukapple]

Hi.
I'm not on windows machine.
Those IPs are all from one MAC address, which belongs to WiFi of the other router.
That other router has static IP and it's in bridge mode - wirelessly connected to main router.

Under "System log - DHCP leases" everything looks OK.

 

[krum]

Then do this one

http://forums.smallnetbuilder.com/sh...42&postcount=8

 

[Lukapple]

It didn't help.
I think that this is not same problem. In "General log" everything looks ok, there is no flooding "DHCP REQUEST, INFORM,..." messages.
Those IPs appears just on the first page (see screenshot at my first post).

 

[NeutralGold]

It didn't help.
I think that this is not same problem. In "General log" everything looks ok, there is no flooding "DHCP REQUEST, INFORM,..." messages.
Those IPs appears just on the first page (see screenshot at my first post).

Does the router that's in bridge mode have your main router set as the gateway and dns server? Sometimes if you leave those fields blank or default they can cause behavior like that when in bridge mode.

 

[Lukapple]

Can't find those settings in dd-wrt.
Here is my setup(see secondary site, primary is ASUS in my situation):

I've noticed that wifi signal between primary and secondary is weak, maybe that's the reason...

Here are screenshots from secondary router settings:

 

[Lukapple]