Gargoyle Forum

Posted: **Sun Jan 04, 2015 4:28 am**

Hi

I seem to have some issue with DHCP config. I tried to search thru the forum but cannot find solution for my issue.

I have just installed Gargoyle 1.6.2 on my NetGear WNDR3800 device. It helped me to solve the long lasting issue of stock netgear firmware with dropping WLAN clients, thanks

However the problem that I have at the moment is related with DHCP configuration - I wan't DHCP to assign specific IPs to the specific devices by MAC. I have added few MACs to the Gargoyle setup like this (last digits of MAC are masked, just in case):

Code: Select all

[x] LAN DHCP Server Enabled
DHCP range:
	Start:	192.168.1.100
	End:	192.168.1.249
	Lease Time: 12 (hours)
			

Assigned Static IP Addresses:
Hostname	MAC	IP		
GEL-PC-WIFI  1C:4B:D6:55:12:34    192.168.1.54		
GEL-PC-WIRED 48:5B:39:29:12:34 	192.168.1.232		
BROTHER		00:80:92:C4:12:34 	192.168.1.161		
TP-LINK		00:23:CD:12:12:34 	192.168.1.60

However whenever I'm connecting from any WiFi device, DHCP seems to be assigning IP starting from 192.168.1.50, which is even outside the allowed DHCP range. Also the host names that I have assigned on DHCP setup page seem to be mixed up - see MAC 00:23xxx assigned to wrong IP and hostname below:

Code: Select all


Hostname	Host IP	Host MAC	Bitrate	Signal
(unknown)	192.168.1.50		1C:4B:D6:55:12:34	108.0 Mbit/s	-63 dBm
(unknown)	192.168.1.51		20:68:9D:EE:12:34	121.5 Mbit/s	-74 dBm
GEL-PC-WIFI 192.168.1.54		00:23:CD:12:12:34	1.0 Mbit/s	-69 dBm
(unknown)	192.168.1.56		00:E0:91:D0:12:34	54.0 Mbit/s	-79 dBm

I've checked twice that my devices are relying on DHCP to obtain the IP. What could be the problem? Thanks in advance!

P.S. HNY to all BTW

Posted: **Sun Jan 04, 2015 4:52 am**

can you show us screen shots of your related config pages

also sometimes a failsafe reset can fix many problems (depending....)

Posted: **Sun Jan 04, 2015 6:32 am**

Here are the screenshots. I can't reboot router right now as it's heavily used, but will try to do it later.

What looks very suspicious to me is that IP ...1.54 and hostname "GEL-PC-WIFI" that are assigned to the wrong MAC...

Posted: **Sun Jan 04, 2015 6:53 am**

Reboot didn't help. All the new clients are being assigned with IP in range 192.168.1.5x. Weird...

Posted: **Sun Jan 04, 2015 9:35 am**

Hi mate what is ment by firstboot is not a reboot it is a command what you type in over telnet. You can read more here:
http://wiki.openwrt.org/doc/howto/generic.failsafe
Thinking about it now i dont no if you have to be in Failsafe to run firstboot. It mite work from a standard command line. It's like doing a factory reset.

Posted: **Sun Jan 04, 2015 10:56 am**

Oh, good to know, thanks! I'm still new to Gargoyle and OpenWRT

I will try it later when not much traffic.

Posted: **Sun Jan 04, 2015 4:44 pm**

I had the same problem on 1.6.2 with a WDR3600, except it also happened even without using static IPs. Plus the clients that received a wrong IP address couldn't connect to the internet.

Can you let me know if a firstboot fixes it for you?

Posted: **Mon Jan 05, 2015 1:33 am**

from memory there was a bug that was patched after 1.6.2

try

http://www.gargoyle-router.com/phpbb/vi ... =14&t=6356

Posted: **Tue Jan 06, 2015 4:36 am**

Thanks to all for responses! Unfortunately can't run failsafe reboot due to heavy traffic, probably will delay it until weekend. Will update you then.

Posted: **Tue Jan 06, 2015 6:07 am**

I've had a closer look at your screen shots

I can't see a problem

it appears that you have manually assigned static IP address, which can be any address you like?

Gargoyle Forum

DHCP - locking IP to MAC doesn't seem to work

DHCP - locking IP to MAC doesn't seem to work

Re: DHCP - locking IP to MAC doesn't seem to work

Re: DHCP - locking IP to MAC doesn't seem to work

Re: DHCP - locking IP to MAC doesn't seem to work

Re: DHCP - locking IP to MAC doesn't seem to work

Re: DHCP - locking IP to MAC doesn't seem to work

Re: DHCP - locking IP to MAC doesn't seem to work

Re: DHCP - locking IP to MAC doesn't seem to work

Re: DHCP - locking IP to MAC doesn't seem to work

Re: DHCP - locking IP to MAC doesn't seem to work