You may also try daloRADIUS for the management of your RADIUS deployment.

Regards,
Liran Tal.

27

(5 replies, posted in Special Configurations)

You're ADSL router is your WAN link to the world, it doesn't require any configuration.
This is what your configuration should look like:

[Internet Cloud] <-> [ADSL Router] <-> [Ubuntu Server] <-> [Wireless AP]

On the Ubuntu server you need to setup one ethernet card to connect to the ADSL router for an Internet link
and the second ethernet card goes into the Edimax AP for the wireless interface.

Then it's just all about setting up chillispot for the captive portal.

Goodluck.


Regards,
Liran Tal.

Thanks for the positive feedback Andrew,
daloRADIUS is all about community and users needs, we develop it so that everyone can customize
it and deploy it fast and easy on any server.

I'd love to hear if there are any feature requests to improve daloRADIUS.

Regards,
Liran Tal.

29

(11 replies, posted in Documentation)

Hey Toto,

Will you please try to explain again what is your need, it's a bit vague and I'd like to help.


Regards,
Liran Tal.

30

(0 replies, posted in Documentation)

Hey guys,

i'm not sure how many of you are aware of daloRADIUS, the management platform for RADIUS deployments.
daloRADIUS is an advanced RADIUS web management application aimed at managing hotspots and general-purpose
ISP deployments. It features user management, graphical reporting, accounting, a billing engine and integrates with
GoogleMaps for geo-locating


Homepage:   http://sourceforge.net/projects/daloradius/
Wiki page:     http://daloradius.wiki.sourceforge.net/
Screenshots: http://sourceforge.net/project/screenshots.php?group_id=193562





    * Changelog for Release 0.9.5
          - added improved support for sql db queries
          - added new contact info for hotspot owners
          - added more attributes and ordered existing
          - added support to relate users to groups on new user, batch add user and new quick-add users pages
            as well as editing these groups entries in edit user page
          - added suport for database debugging and error handling
          - added custom accounting query page
          - added disconnect user on maintenance sub-category
          - added partial tabindexs support to forms (Antonis Faragitakis)
          - added description dialogs for pages upon clicking on page titles
          - added and improved new blue css layout
          - added icons and support for deleting single attributes for users
            in the Edit User management page
          - improved interface with addition of checkboxs for multi-action tasks
          - improved online help support for each page
          - improved support on Test User Connectivity to use radclient with more features
          - improved support on all sidebar input values so that variables are saved when
            the pages are reloaded/submitted to a new page
          - fixed double-insert records of userinfo data if user exists
          - fixed deleting of userinfo data for a record that is being deleted
          - fixed drawing the options selectbox in the radreply tab in User Edit page
          - fixed saving an existing nas entry in different name (not having to delete it)
          - fixed several typos and variable declerations through-out the pages
          - fixed duplicate groups entries in usergroup table (paparent)
          - language file and variables are better sorted out (finally)
          - alot of php/html code clean up and code indentation



Plans for the upcoming 0.9-6 release:

    * A whole re-work of the attributes management is coming in - I've already started coding it, based on ajax, the new attributes management is going to be a life saver easy, include tooltips, recommended OP and target table (radcheck/radreply),
      as well as a helper routine. Definitely something worth waiting for...
    * More Ajax and more improvements to the GUI layout, more icons




I'd love to get some feedback.

Merry Christmas,
Liran.

Sorry for the long time.

It didn't require any changes to the firewall rule, just add to /etc/firewall.user:
iptables -A forwarding_rule -i tun0 -j ACCEPT

To break the bridge bonding between vlan0 and eth1 simply do:
brctl delif br0 eth1
This will separate the eth1 (WLAN) interface from the br0 bridge.

Then just start chilli on eth1 and everything should work fine.


Let me know if you have any problems.

Regards,
Liran Tal.

Yeah I'm gonna set this up pretty soon and will keep you updated.
Since you mentioned nvram it's necessary to ask which version of openwrt
are you working with :-)
WR or Kamikaze?

About the setup - in terms of interfaces, its not a must to use the brctl utility
indeed and nvram settings are probably easier to manage although a reboot
is required to apply them while brctl commands work on-the-fly.

So basically the configuration should be simple, if currently (default) I have
the nvram setting: lan_ifnames=vlan0 eth1 eth2 eth3
I should simply take eth1 out of it, and manually with brctl also break the
bridge between vlan0 and eth1 just to check for these settings without
rebooting.

About the firewall I am still unsure how to set up the rules so that I keep
the original openwrt's firewall script while adding support for chillispot.


What do you say about the firewall?
I believe chillispot is to be set so that it drops all packets going outside
but I can't remember

Hey ajauberg,

I was wondering how would you approach a setup where the interfaces are configured
in such way that vlan0 (LAN) is separated from eth1 (WLAN) interface?
Would you simply delete the br0 bridge between in them, such as "brctl delbr br0 eth1" and
thats it.

To continue with that, would the firewall rules actually have to be changed? it doesn't
seem as if they pose a problem. It would be enough to simply add to /etc/firewall.user
"iptables -A forwarding_rule -i tun0 -j ACCEPT"
(and possibly a rule to drop everything coming from the eth1 interface as chillispot
manually assigns new iptable rules for clients when they authenticate).



What do you think?