Which is better for your embedded captive portal, ChilliSpot or WiFiDog?

Which is smaller?
ChilliSpot + kmod-tun packages: 59k
WiFiDog + libpthread packages:  50k or 85k (depending on libpthread package used)

Which is easier to install?

Which is easiest to administer and update?

Which is easiest for the end-user?

Which has the better feature set?

Which auth-server is better - radius or wifidog-auth?

From a cursory glace at the features listed here:
http://www.chillispot.org/features.html
http://www.ilesansfil.org/wiki/WiFiDog/FeatureList
It seems that WiFiDog is more fully-featured, with better options for local content.  I've not used either yet, so I'm interested in hearing from people who have used one or the other, or - even better - both.  Are they both intended for exactly the same application - hotspot portalling and authentication - or do they specialise differently in different aspects?

Hello,
this is a bit old topic but still interesting. I would also like to know the pro/cons of both solutions.

Regards,
Tex

WifiDog doesn't require a RADIUS server.

Yes, there are differences between the two. For one thing,Wifidog is more than just an access controller the open-source project also includes a captive portal application. Wifidog works with iptables, which is already in the firmware.Chillispot, however, offers features like MAC authentication and has radius internally.You are able to do more with Chillispot,but requires you do invest more time in developing your own version of the "hotspotlogin.cgi" sample script given with Chillispot.Yet, you are able to do more with Wifidog in terms of captive portal and standard access controller features.