[isf-wifidog] Wifidog wrt54g install support questions
mina at naguib.ca
Sam 5 Nov 19:09:05 EST 2005
The WiFiDog has a built-in web server. By default, that web server
does not listen to the traditional port 80, but instead on port 2060
The error message below is wifidog complaining that while it was
setting up that web server, it failed to bind to that port. The most
common reason this could happen is if there's something else
listening on the same port.
Is wifidog already running ? If that's the case, that's where the
problem is. The already-running wifidog is already listening on the
If it's not, you need to find out what's listening on the port and
resolve that conflict.
If you modified the "GatewayPort" config directive in wifidog.conf to
something like "80", then "don't do that". Revert it back to the
default "2060". Unless you really know what you're doing you should
leave that setting untouched.
If it is the default, and you've made sure that no older copy of
wifidog is currently running, use this command to verify that the
port is indeed being bound by an application:
netstat -a | grep LISTEN | grep 2060
Then, and this is the hard part, use the process of illimination to
kill off processes one by one until you finger the one that was
listening to that port.
There are easier ways to do that last step, but none of the needed
features are included in the OpenWRT installations I've seen.
On 5-Nov-05, at 6:48 PM, Rein Petersen wrote:
> Hi All,
> Before I post my questions regarding installing wifidog on wrt54g
> here, I wanted to make certain there isn't a better place to pose
> those kinds of questions (please let me know). If this is the place to
> post such questions then please read on.
> I've been following the installation instructions prepared at:
> The node I'm preparing is intended for wirelesstoronto but I'm able to
> deduce the differences in /etc/wifidog.conf.
> My issue was running the command :
> wifidog –f –d -7
> which I later discovered was a typo fixed in the wiki in a later
> revision; it should have been:
> wifidog –f –d 7
> Anyway, rerunning the command emmited quite a bit of information but
> the last entry concerned me the most:
> (gateway.c:386) Could not create web server: Address already in
> Unable to really make sense of the issue I tried connecting to the
> router wirelessly to find that I can connect successfuly but it passes
> me directly to the internet without presenting the portal page.
> Any suggestions?
> Thanks in advance,
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
More information about the WiFiDog