Salut André,

je ne sais pas comment intégrer le client wifidog à une image open wrt ou
dd wrt.

par contre, je sais comment l'intégrer à AirOs
http://dev.wifidog.org/wiki/doc/install/airos


Il y a quelques inexactitudes dans la doc (du moins si tu utilises un ordi
sur ubuntu) :

- ne pas utiliser /dev : l éspace sera insufisant pour faire la
compilation. Il vaut mieux se créer un répertoire dans /home et partir de
là (exemple : /home/ISF)

- pour créer les liens symboliques, ne pas mettre de tilde ~
ex : remplacer ln -s ~/home/ISF/wifidog/airos/wifidog/
par ln -s /home/ISF/wifidog/airos/wifidog/

- Si jamais tu le fais sur une machine virtuelle ubuntu, il y a des
dépendances à installer :
apt-get install libncurses5-dev
apt-get install ncurses-term
apt-get install zlib1g-dev
apt-get install gawk
apt-get install bison
apt-get install flex
apt-get install autoconf
apt-get install subversion
apt-get install patch


- avant de faire cette commande
make world V=99
il faut se trouver dans le repertoire /openwrt

Aussi, la doc parle de faire des wget pour récupérer des archives, mais
avec moi ça ne marchait jamais, fichier corrumpu etc. le mieux c'est de le
télécharger et le mettre à la main dans le répertoire pour le "dézipper"


La semaine prochaine, je devrais avoir du temps à consacrer à vérifier ton
serveur et te faire une image si tu n'a pas réussi


C'est un peu compliqué à faire avec AirOS, car on ne peut pas modifier le
fichier wifidog.conf après coup, il faut recompiler... C'est pour cela que
faire ses premiers tests avec un wrt54g/L est intéressant.
Mais tu sembles être *extrêmement* motivé alors amuses toi :)


Cordialement
Jackson JOSEPH-EUGENE
Coordinateur technique et des bénévoles Ile Sans Fil


2012/7/25 Andrei <email address hidden>

> Sometimes, there is so few activities here that it seem that authpuppy's
> dead. His father wifidog is almost dead but not totally.
>
> I installed Openwrt on one of my router. It worked fine and i really
> don't know what distro i took, this time it was just for a test with a
> cheap router a TP-Link 741ND ver. 2.5 with this firmware : openwrt-
> ar71xx-generic-tl-wr741nd-v2-squashfs-factory.bin and i do not know wich
> "backfire" (an openwrt serious expression) it is related to, but it seem
> to be the last one 10.03.1 created at the end of December 2011.
>
> Now i have my router running. But as it is for DD-WRT there is no
> official documents about installing a router based on OpenWRT with a
> specific tool related to wifidog and there's nothing about authpuppy. In
> my point of view, it is good to have an authentication server but if
> there no "gas" to run it (even if there is router's image made for it)
> it remain a server who does nothing.  Anyway.
>
> I found some links about wifidog one where a geek make it complicated
> for nothing creating a dual boot router with dual wifidog daemons. I
> think that the guy lost itself in his own explanation that we can see
> here :
>
> https://forum.openwrt.org/viewtopic.php?id=24926 (Just reading it and it
> is like  )
>
> I found this url :
>
> http://wiki.openwrt.org/doc/howto/wireless.hotspot.wifidog
>
> Having ??? signs in the wifidog configuration of the router :
>
> opkg install wifidog
> vi /etc/???
> . /etc/init.d/??? enable
> . /etc/init.d/??? start
> netstat -a
>
> and i can see if this package can be run in my backfire 10.0.03.1
> firmware.
>
> Is there's some other ways to installed a running and working router
> with authpuppy without having to take an image of an existing running
> router ? (So many thanks to those who helped about that image by the way
> and i don't want to tell name here).
>
> Why there is no real documentation about the half side of authpuppy :
> The communication side ?
>
> --
> You received this bug notification because you are subscribed to
> AuthPuppy.
> https://bugs.launchpad.net/bugs/1028578
>
> Title:
>   Connection management problem
>
> Status in AuthPuppy authentication server for Wifidog networks:
>   New
>
> Bug description:
>   Some ways to configure wifidog in DD-WRT make it works although
>   there's others ways were it lead to problems.
>
>   On first instance, since i made classful connections meaning that having
> a network topology having one of the address's type between  192.168.1.0 to
> 192.168.254.0 (class C) respecting mask related to class C connection which
> are 255.255.255.0
>    (otherwise /24) help a lot and solve many problems.
>
>   I discovered it cause my airport extreme router (made by Apple) is a
>   class A router. This mean that adressing the mask must respect
>   255.0.0.0 network topology (in other word /8) and a 10.0.0.0 network
>   type adressing topology.
>
>   This may be obsolete for certain peoples, but that's not the case on
>   some iptables (firewall) entries. I discover that a class C address
>   with a 255.255.0.0 mask may be refused by some linux ip tables rules
>   of linux based server.
>
>   It may be possible to change iptables having classless adressing
>   instead classful adressing.
>
>   GOD ! why it is so hard to explain !!! Anyway ... in english.
>
>   Now, that this problem lead me to have better results in my
>   connection's problems, if in the wifidog dd-wrt configuration of my
>   router i simply disable HTTP Server Authentication Support, i have
>   this kind of url :
>
>
> https://www.nexeras.com/login/?gw_address=192.168.10.1&gw_port=2060&gw_id=2&url=http%3A//www.grc.com/
>   (grc.com contains a lot of useful things by the way) .
>
>   But if i enabled it everything's fine, and i have access to internet.
>   But i do not have any splash page, and my server is configured to have
>   splash page only connection.
>
>   If i disabled AuthServer SSL Available it may lead to the same problem
>   explain before. The only way to have a connection is to enable HTTP
>   Server Authentification Support all the subsequent textboxes are
>   blank, and having AuthServer SSL Available enabled.
>
>   So if it make a difference in configuration it may be also be a bug
>   ...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/authpuppy/+bug/1028578/+subscriptions
>