Ok I figured it out myself, the <a href="http://www.linuxelectrons.com/News/Mobile/20040623115842787">http://www.linuxelectrons.com/News/Mobile/20040623115842787</a> is a cool VOIP service and wifidog AP by default offers people option to use this VOIP service if firewall configuration has those IP address
<br>FirewallRule allow udp to <a href="http://69.90.89.192/27" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">69.90.89.192/27</a><br> FirewallRule allow udp to <a href="http://69.90.85.0/27" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
69.90.85.0/27</a><br> FirewallRule allow tcp port 80 to <a href="http://69.90.89.205/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
69.90.89.205</a><br>Gateway ID = MAC address of Wifidog AP or a template ID needs to be created on Authenication server.<br><br>ExternalInterface is the WAN Port of the wifidog Access Point Port confgured as static or DHCP eth0.. Or if Configured for PPOE it is ppoe.
<br><br>I did figure that out correct.. right >?<br><br>Raj<br><br><br><br><div><span class="gmail_quote">On 8/31/06, <b class="gmail_sendername">Rajendra Jagad</b> <<a href="mailto:rjagad@gmail.com">rjagad@gmail.com
</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;"><div><div>Hi Benoit Thank you for the response, I try to experiment and run wifidog -f -d 7 after running
</div>
<div>configure, make and then make install It runs and does lot of stuff. </div>
<div>But wifidog expect the wifidog.conf to be inside /etc/ directory the install scripts puts it</div>
<div>in /usr/loca/openwrt/wifidog.conf I think that is because I had created a wifidog.conf file manully before running</div>
<div>the script.. So it is smart to put where the old files are. But then the wifidog -f -d 7 still looks inside /etc/</div>
<div>Should I report this as a bug and open a ticket ??</div>
<div> </div>
<div>I have other issues I am running authentication server on Fedora core 5, very window friendly environment.</div>
<div>One has to manully configure the wifidog.conf file and I am having problem understanding some of the terminalogies mention there in.</div>
<div> </div>
<div><a href="http://dev.wireless-fr.org/trac.cgi/file/ipk-ffw/trunk/data/etc/wifidog.conf?rev=16" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://dev.wireless-fr.org/trac.cgi/file/ipk-ffw/trunk/data/etc/wifidog.conf?rev=16
</a> is the link to one of the supposedly working wifidog.conf file.</div>
<div> </div>
<div>GatewayID is missing. I think to me it is unclear the terminology GatewayID. Comming from Networking world it has alway been an IP address or Hostname. Here the comments says one has to set it to template ID on the Authentication
server.I did a find . -exec grep -in command to find the template ID and found one in wifidog-1-1.3beta2/wifidog.conf </div>
<div>If somebody can tell me where to find this template that would be greate. Then it says It would be MAC address of Gateway Does mean MAC address if Auth- Server or Router, Most firewalls and Authecation proxy the MAC address of the router located on its WAN Port. That knowledge confuses me a little.
</div>
<div> </div>
<div>ExternalInterface vlan1 -- Is this the external interface on multihome Authen server Or Multihomed wiidog AP/ Router</div>
<div> </div>
<div>Why are this specific IP listed under generic configuration and not even commented out ? I do not understand.</div>
<div>FirewallRule allow udp to <a href="http://69.90.89.192/27" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">69.90.89.192/27</a><br> FirewallRule allow udp to <a href="http://69.90.85.0/27" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
69.90.85.0/27</a><br> FirewallRule allow tcp port 80 to <a href="http://69.90.89.205" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
69.90.89.205</a><br> </div>
<div><br> Thanks for the help</div>
<div> </div>
<div>Raj</div></div><div><span class="e" id="q_10d64f0ca12345cb_1">
<div><br><br> </div>
<div><span class="gmail_quote">On 8/31/06, <b class="gmail_sendername">Benoit Gregoire</b> <<a href="mailto:bock@step.polymtl.ca" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">bock@step.polymtl.ca
</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">> I do not have fully compatible openwrt APs, so thatīs why I asked if I can<br>> setup the client daemon of wifidog at the same server that will run the
<br>> wifidog auth server.<br><br>You can.<br>_______________________________________________<br>WiFiDog mailing list<br><a href="mailto:WiFiDog@listes.ilesansfil.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
WiFiDog@listes.ilesansfil.org</a><br><a href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
</a><br></blockquote></div><br>
</span></div></blockquote></div><br>