Here is some screenshot of the auth-server on multiple step of the
administration process. The screenshot aren't currently hosted on the
wifidog dev-wiki but i'd be pleased to put them somewhere if asked. <br clear="all"><br><a href="http://step.polymtl.ca/%7Epraetori/wifidog/auth_beforelogin.jpg" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Authentification Server: Before Login </a><br>
<div style="margin-left: 40px;">First page from the portal: the login page.<br>
</div>
<br><a href="http://step.polymtl.ca/%7Epraetori/wifidog/auth_afterlogin.jpg" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Authentification Server: After Login </a><br>
<div style="margin-left: 40px;">When logged. If you are using the
system "normaly" you should have a customized portal page. Since i've
connected directly to the auth-server, i'm having general options<br>
</div>
<br><a href="http://step.polymtl.ca/%7Epraetori/wifidog/auth_administration.jpg" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Authentification Server: Administration</a><br>
<div style="margin-left: 40px;">If you click on "administration", from the previous screen shot. Administration options are on the left.<br>
</div>
<br><a href="http://step.polymtl.ca/%7Epraetori/wifidog/auth_nodemgt_list.jpg" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Authentification Server: Node list</a><br>
<div style="margin-left: 40px;">First item from the node management
administration option. You get a list off all the node in your network,
you can edit/create new one from here.<br>
</div>
<br><a href="http://step.polymtl.ca/%7Epraetori/wifidog/auth_nodemgt.jpg" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Authentification Server: Node management</a><a href="http://step.polymtl.ca/%7Epraetori/wifidog/auth_nodemgt.jpg" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
</a><br>
<div style="margin-left: 40px;">An "edit" command from the node list
will bring you to that screen [careful, big image] - you write down
node-specific informations here. The geo data is used to place the dot
on the google map.<br>
</div>
<br><a href="http://step.polymtl.ca/%7Epraetori/wifidog/auth_networkmgt.jpg" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Authentification Server: Network management </a><br>
<div style="margin-left: 40px;">This is the network management screen... everything is pretty clear. <br>
<br>
</div>
For "true" definition of each screen/menu you should check in the documentation. I'm only writing doc for my own install.<br>
<br>
Pascal Ch.<br>
<br>-- <br>Pascal Charest, OpenSource Consultant.<br><a href="http://blog.pacharest.com/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://blog.pacharest.com</a>
<br><br><div><span class="gmail_quote">On 12/11/06, <b class="gmail_sendername">Benoit Grégoire</b> <<a href="mailto:bock@step.polymtl.ca">bock@step.polymtl.ca</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Monday 11 December 2006 10:31, <a href="mailto:chip@innovates.com">chip@innovates.com</a> wrote:<br>> You make too many assumptions about what I will do if I start using<br>> WifiDog. As part of the contract I'm working on I will have to make at
<br>> minimum the following additions to WifiDog:<br>><br>> 1. An operating schedule for each node, to close access and display a<br>> closed access point message for those that attempt to connect.<br>><br>
> 2. Per user and per node bandwidth control.<br>><br>> All of which work I would definitely resubmit to the project. It<br>> appears both of these features are on other people's radar also, but<br>> haven't made it to existing developer's priority yet. But maybe they
<br>> have and the documentation and ticket system hasn't been updated yet<br>> either.<br><br>While obvoiusly not everything anyone is planning to work on is in the ticket<br>system, it is generally up to date, accurate and well maintained.
<br><br>> Letting the feature lists and documentation fall behind, doesn't do<br>> anyone any good. It only makes potential new comers either look else<br>> where, because the project looks less mature than it really is, or
<br>> generates questions on mailing list like this message that everyone gets<br>> tired of answering.<br><br>Oh, you'll get no arguments from me there, I've been the one pushing the<br>hardest for better docs, and writing a lot of it. But I've been focussing on
<br>docs that I'm currently the only one capable of writing. I've been hoping<br>other people will sink their teeths in the feature list, which is easier and<br>simple for multiple people to work on, but so far this hasn't happened yet.
<br><br>> I am a potential new user and contributor of the project, but don't see<br>> much value in setting up every hotspot project I can find just evaluate<br>> which one I really want to sink my teeth into.<br>
<br>I think that's a mistake, before spending weeks/month of full time work<br>modifying one, you should spend at least a day on each one. There's only a<br>handfull of captive portal projects.<br><br>> If you haven't noticed
<br>> from this posting, I'm a real believer in updating documentation when<br>> code gets updated especially when I contribute to a project.<br><br>Well, we'll be very happy to have you should you chose wifidog.<br>
<br>--<br>Benoit Grégoire<br>Technologies Coeus inc.<br><br><br>_______________________________________________<br>WiFiDog mailing list<br><a href="mailto:WiFiDog@listes.ilesansfil.org">WiFiDog@listes.ilesansfil.org</a><br>
<a href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog">http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog</a><br><br><br></blockquote></div><br><br clear="all"><br>-- <br>Pascal Charest, OpenSource Consultant.
<br><a href="http://blog.pacharest.com">http://blog.pacharest.com</a>