First of all, I just want to say that the bug about blocking people from using a different IP had disappeared. I don't remember what version made the problem go away. Now If i want to use the wrong IP, I have to disable that setting first.
Secondly, could we please have a way to delete information from the quotas screen? The recent version solved the problem with assigning group quotas over old one. That was a start. I still have quotas in there for IPs that are no longer in use. They will stay 0. I would like to delete them from the chart.
Thirdly, I would like to report an actual bug. It was been a problem for awhile now, so I thought I would report it.
We have the router set up to assign by DHCP address in the range from 10-12. !0,11,12 share a quota and are open in the firewall. Because we use the all others individual quota, IP address 13,14, etc would get a full blown quota if someone used them. To prevent this, we have all IPs blocked in the firewall, except those that are currently authorized for use.
The bug is if all those IP addresses are leased out, it instead gives people the IP address of 13, and then 14. If 13 and 14 are both given out, I think it refuses to give out an address at all. In that case, they get a private address from the switch we have connected to the router, not from the router. I don't know what happens if 10-14 are taken and someone tries to connect to wireless.
I had the lease time set to 740 hours, so it was rather easy to lease out 10,11, and 12 simultaneously. This seemed kinda pointless with the staic IPs working properly, so I set the lease time back to 24h. I don't know if I will run out of DHCP leases again now, but the bug should still be fixed. It shouldn't be giving out 13 and 14 anyways. If it doesn't give out IPs it isn't suppossed to, and no one can steal an IP they don't belong having (which is currently the case), then we wouldn't need to use the firewall to block address to all unknown IPs.
DHCP bug
Moderator: Moderators
Re: DHCP bug
The issue you describe sounds like it might be a bug in dnsmasq, the dhcp server OpenWrt (and therefore Gargoyle) uses. I'll see if I can replicate this, and if so figure out exactly what's causing it. Thanks for reporting the issue.
A couple people have requested the ability to edit a quota's ip without resetting it, so I may implement this soon. Actually, the way a quota resets when you modify the ip list was a deliberate feature originally, since the quota id was tied to the ip, but now it may be time to rethink that.
A couple people have requested the ability to edit a quota's ip without resetting it, so I may implement this soon. Actually, the way a quota resets when you modify the ip list was a deliberate feature originally, since the quota id was tied to the ip, but now it may be time to rethink that.
Re: DHCP bug
ok thank you for checking into it. The first few times I noticed it I thought it was a virus or something, but with it happening so many times, including with brand new computers, I knew it was a bug in the software.