News: This forum is now permanently frozen.
Pages: [1]
Topic: DHCP Fails v1.3.3 (actually any version)  (Read 2652 times)
« on: January 06, 2012, 17:33:11 »
dbogdan@lumc.edu *
Posts: 14

I have m0n0wall set up to hand out IP addresses on a private  with a /21 address range (255.255.248.0).  About every three or four days, the system just stops handing out addresses.  I attempt to look at the DHCP lease info, but it is apparently too large to crunch back to the browser.  My only resolve is to reboot.

Does anyone have any ideas?  I'm now kicking around a dhcp relay for this instead.

Thanks in advance,

Dave
« Last Edit: January 06, 2012, 21:07:14 by dbogdan@lumc.edu »
« Reply #1 on: January 06, 2012, 17:51:04 »
Fred Grayson *****
Posts: 994

Maybe that's a typo but 255.255.248.0 is not a /29, it's a /21.

--
Google is your friend and Bob's your uncle.
« Reply #2 on: January 06, 2012, 21:05:48 »
dbogdan@lumc.edu *
Posts: 14

I don't see how this helped the cause, but thanks.  I think this may something to do with the file size of the dhcp table.  If the table ends up on the floppy, that may be the reason, but not sure it does or doesn't.  I'm going to install the hard disk version and see if this clears it up.  I'll post my results for folks that are interested in the result, not the syntax of my message.
« Last Edit: January 06, 2012, 22:27:32 by dbogdan@lumc.edu »
« Reply #3 on: January 17, 2012, 19:10:59 »
dbogdan@lumc.edu *
Posts: 14

I just installed the system to a Hard drive.  Hopefully this will resolve it.   Will get back to all in a day or two as it seems it take this long for us to encounter issues.
« Reply #4 on: January 19, 2012, 18:40:39 »
dbogdan@lumc.edu *
Posts: 14

Status:

Still having an issue after installing to the hard drive.  I reduced the number of leases to 750.  Still using a using 255.255.248.0 mask. Originally x.x.96.1 - x.x.103.239.  Now down to x.x.96.1 - x.x.98.255.  Hopefully this will reduce the dhcp dataset size if that's what the issue is.  I also reduced the lease to 1 hour, from 3.

Looking at the Beta version next.
« Reply #5 on: February 27, 2012, 18:41:06 »
PlasmaFlow *
Posts: 6

Status:

Still having an issue after installing to the hard drive.  I reduced the number of leases to 750.  Still using a using 255.255.248.0 mask. Originally x.x.96.1 - x.x.103.239.  Now down to x.x.96.1 - x.x.98.255.  Hopefully this will reduce the dhcp dataset size if that's what the issue is.  I also reduced the lease to 1 hour, from 3.

Looking at the Beta version next.

Do you really need such a large supernet?

also, what is your lease time and what is the typical device on your network?
I/E Laptops, Computers, IPPhones? PPTP VPN?

You may try to check if all the leases show active or expired also, its why i asked for the minimum and maximum lease times.
 
« Reply #6 on: March 03, 2012, 04:49:31 »
cmb *****
Posts: 851

Generally when that happens it's because the lease database is too big for the RAM disk where m0n0wall keeps it. Installing to a hard drive is functionally no different, it still runs from RAM and keeps the leases in RAM. Not sure there's an easy way around that, hacking the source to make that a bigger RAM disk is the only option as far as I'm aware.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines