<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Our server is down, so I decided to spend a little time on my Captive
Auth-Server. I have managed to get it running with routers using ver
1.1.3Beta. When I try to replavce the router with a new one running
1.1.4, I continue to have problems accessing the auth server. I took
a few clips from the screens that I think may be helpful. Any help,
ideas, direction appreciated.<br>
<br>
Here are my clips- hope they are of some use or provide at least a clue.<br>
<br>
login as: root<br>
<a class="moz-txt-link-abbreviated" href="mailto:root@192.168.5.1">root@192.168.5.1</a>'s password:<br>
<br>
<br>
BusyBox v1.00 (2007.01.30-11:42+0000) Built-in shell (ash)<br>
Enter 'help' for a list of built-in commands.<br>
<br>
_______ ________ __<br>
| |.-----.-----.-----.| | | |.----.| |_<br>
| - || _ | -__| || | | || _|| _|<br>
|_______|| __|_____|__|__||________||__| |____|<br>
|__| W I R E L E S S F R E E D O M<br>
WHITE RUSSIAN (0.9) -------------------------------<br>
* 2 oz Vodka Mix the Vodka and Kahlua together<br>
* 1 oz Kahlua over ice, then float the cream or<br>
* 1/2oz cream milk on the top.<br>
---------------------------------------------------<br>
root@msf-012-DD:~# wifidog-init status<br>
WiFiDog status<br>
<br>
Version: 1.1.4<br>
Uptime: 0d 0h 4m 19s<br>
Has been restarted: no<br>
Internet Connectivity: yes<br>
<font color="#cc0000"><big><b>Auth server reachable: no</b></big></font><br>
Clients served this session: 0<br>
<br>
0 clients connected.<br>
<br>
Authentication servers:<br>
Host: 192.168.2.200 (192.168.2.200)<br>
<br>
<br>
<br>
Extract from wifidog -f -d 7<br>
<br>
[7][Sat Jan 1 00:06:24 2000][1295](util.c:111) Process PID 1300 exited<br>
[7][Sat Jan 1 00:06:24 2000][1295](fw_iptables.c:80) Executing
command: iptables -t nat -A WiFiDog_AuthServers -d 192.168.2.200 -j
ACCEPT<br>
[7][Sat Jan 1 00:06:24 2000][1295](util.c:109) Waiting for PID 1302 to
exit<br>
[7][Sat Jan 1 00:06:24 2000][1295](gateway.c:259) Handler for SIGCHLD
called. Trying to reap a child<br>
<br>
<br>
<br>
[7][Sat Jan 1 00:08:43 2000][1568](centralserver.c:325) Level 1:
Connecting to auth server 192.168.2.200:80<br>
[7][Sat Jan 1 00:08:46 2000][1568](centralserver.c:342) Level 1: <font
color="#cc0000"><b>Failed to connect to auth server 192.168.2.200:80 <big><big>(No
route to host)</big>.</big> Marking it as bad and trying next if
possible</b></font><br>
[7][Sat Jan 1 00:08:46 2000][1568](centralserver.c:224) Level 2:
Calculated 1 auth servers in list<br>
[7][Sat Jan 1 00:08:46 2000][1568](centralserver.c:182) Unlocking
config<br>
[7][Sat Jan 1 00:08:46 2000][1568](centralserver.c:182) Config unlocked<br>
<b>[3][Sat Jan 1 00:08:46 2000][1568](centralserver.c:185) Failed to
connect to any of the auth servers</b><br>
<br>
<br>
[7][Sat Jan 1 00:07:03 2000][1295](fw_iptables.c:80) Executing
command: iptables -t filter -X WiFiDog_Unknown<br>
[7][Sat Jan 1 00:07:03 2000][1295](util.c:109) Waiting for PID 1396 to
exit<br>
[7][Sat Jan 1 00:07:03 2000][1295](gateway.c:259) Handler for SIGCHLD
called. Trying to reap a child<br>
[7][Sat Jan 1 00:07:03 2000][1295](gateway.c:263) Handler for SIGCHLD
reaped child PID -1<br>
[7][Sat Jan 1 00:07:03 2000][1295](util.c:111) Process PID 1396 exited<br>
[6][Sat Jan 1 00:07:03 2000][1295](gateway.c:294) Explicitly killing
the fw_counter thread<br>
[6][Sat Jan 1 00:07:03 2000][1295](gateway.c:298) Explicitly killing
the ping thread<br>
Killed<br>
root@msf-012-DD:~#<br>
<br>
</body>
</html>