Terrific. Thanks. I turned on the 1.2 captive portal yesterday at 5:30
am and it worked fine until about 3 pm but then stopped working (timed
out clients got error messages rather than being directed to the portal
page even after I rebooted), and I had to turn it off. I had retained
this line in the portal page: <input name="redirurl" type="hidden"
I'm hopeful that I can turn the captive portal back on after upgrading.
I see this in the changelog
"new feature: the number of connections per client IP address can now be
limited to prevent one misbehaved user from tying up the server. The
default limit for the captive portal is now 4 connections per client,
and 16 in total (can be adjusted on captive portal setup page)"
I'm afraid (as a relative newbie) I don't understand just what
constitutes a connection in this context and in particular under what
circumstances it may be advisable to adjust the total default number of
16 connections. When does a user's captive portal connection start and
end? Should the connection number be adjusted to be greater than the
total number of expected concurrently logged in users?
Manuel Kasper wrote:
>first things first - happy new year to you all! I hope that it has
>begun well for you.
>The year 2006 already brings us a new m0n0wall release: 1.21 is
>ready! It mostly consists of many captive portal improvements (thanks
>to Jonathan de Graeve) - more and better RADIUS options, a file
>manager, and better mini_httpd stability. There have also been a few
>bug fixes of course.
>Download it at:
>Captive portal users should make sure that they've got the "redirurl"
>hidden field in their login forms, even if they're only running it in
>HTTP mode. Those who have been using inofficial builds with the
>"element manager" need to delete the old elements from their
>config.xml before upgrading (see the changelog for details). Other
>than that, it should be a painless upgrade from 1.2.
>BTW, the m0n0wall logo stickers are scheduled to be delivered later
>this month - I'll let you know when they're ready (there'll be an
>order form on m0n0.ch).
>Also, I'm sorry about the m0n0.ch downtime earlier today (although I
>doubt that many of you have noticed ;) - the CPU fan decided that it
>didn't want to live for another year and died shortly after midnight.
>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch