ip range redirecting to login page

[lockpicker]

I'm running v1.2.0 on WRT54GL with Download Limits set based on ip ranges(roughly 2.5GB per IP range) and an all other individuals combined daily quota of 50MB. The clients have been given static DHCP's from the router with individual people having ip's for all their devices in one range. I''ve faced two issues so far:

1. When I move a device from an all other individuals category to one of the ip ranges with a quota and the daily limit for all others category was exhausted, the device was still being redirected to the login page(with other devices in the range behaving normally) with a quota exhausted message. This went away when I deleted the quota for the other category and re-created it.

2. After issue 1 being resolved, all devices on one of my ip ranges are being redirected to the router login page even though the quota used is only 2.5%. I haven't tried deleting and recreating the quota for this range as I'm wary of loosing the usage data for the range.

And rebooting does not help in either case.

Any suggestions?

[Eric]

You refer to "an all other individuals combined daily quota of 50MB." Do you mean "all others indivdual", or "all others combined"? They are two different things.

[lockpicker]

Hi Eric,
I'm referring to the "All others combined" category.

[Eric]

Ok, I'm looking into this now. However, I should warn you that unless/until I can replicate the error I'm probably not going to be able to solve it.

The more details you can provide about the configuration that resulted in the problem, the better. Ideally, you would show me a screenshot of the quota section with the label "first I configured it this way", and then another with "and then I adjusted it to this" which is when I started having the problem with the IP A.B.C.D.

[lockpicker]

Thanks Eric,

More than happy to help make this stable. I'll post more detail later today once I get back home.

[lockpicker]

First, This is the problem

Redirected screen

redirected_screen.jpg (42.42 KiB) Viewed 6089 times

Looking at the url, I can tell that all the requests are being redirected to the router.

Here's how I met with the problem.

1. After installing v1.2.0 on my WRT54GL, I set up the following static DHCP assignments

Initial Client Config

client_config_1.jpg (22.5 KiB) Viewed 6088 times

Having done this, I set up the following quotas

Quota Setup

Quotas_1.jpg (30.5 KiB) Viewed 6088 times

At this stage, everything was working as expected. After this, I connected two more devices to the network which were then assigned a DHCP address by the router which did not fall under any of the quota limited ip ranges hence belonging to the others(combined) category.

edit: some text moved to next post

[Will continue in the next post as there is a 3 attachment limit on posts]

[lockpicker]

Now, I moved the two devices under question into two different ip ranges respectively and arrived at the following static dhcp assignments

Client config 2

client_config_2.jpg (44.29 KiB) Viewed 6073 times

At this stage, the device with ip 192.168.1.22 continued to use the quota from the others(combined) category and hence exhaused the quota limit for that category(which is 50MB)

Once the quota limit for the others(combined) category was reached, The two devices (192.168.1.22 and 192.168.1.13) were blocked from accessing the internet with a quota used message in red.

After a few reboot attempts when the problem persisted, I deleted and recreated the quota for the others(combined) category which seemingly fixed the problem at hand.

At this stage all devices were able to use the internet from there respective quotas and all was well.

Since the next morning however, all the devices from the ip ranges
192.168.1.11-192.168.1.20 and 192.168.1.31-192.168.1.40 are facing the problem of being redirected to the router config page even the quota's are far from exhausted and the problem persists.

I hope I have been able to articulate the problem in a manner which can be understood. Please let me know if any more detail is required.

edit: After a power cycle on the router, the same behavior started occurring on all the ip ranges and I had no choice but to delete and re-create all the ranges
(As unfortunately I'm not the only one using the router and the others are not as patient in the name of discovery)
The problem seems to be not occurring after doing this but I will watch and report any further instances. I hope the description helps recreate the scenario.

[Eric]

I'm pretty sure I know what was causing your first problem. The router can't force a renewal of a DHCP lease, so when you asigned a static IP it didn't take effect right away. You have to wait for either the existing dhcp lease to expire or reboot the host system (not the router), or tell the dhcp client running on the host to renew it's lease.

The second issue sounds more serious. First, are you sure that all the host systems were actually being assigned the appropriate assigned static IPs, and appropriate quotas were being incremented? It's possible that this is a repeat of problem #1. If that's not it then it definitely sounds like there is a bug somewhere. I will continue to try to replicate the problem, and if I can replicate it, fix it.

By the way -- your screenshots are exactly what I needed. Thanks!

[Eric]

This should be fixed now -- I just released version 1.2.1 with the fix.

Thanks for bringing this issue to my attention!

[lockpicker]

Thanks Eric,
Appreciate the turnaround.

Keep up the good work.