AuthPuppy

No Internet Access and Invalid request path ' '

Asked by Asoh Frank Senior

Presently, i can see the network Login and Administrative Login page.

But when i click on any of them, i get a webpage cannot be found error.

.........................................................................................................................................
When i use this this link, http://authpuppy.localhost/frontend_dev.php/ping/?gw_id=000B6B020792&sys_uptime=2799&sys_memfree=138784&sys_load=0.13&wifidog_uptime=1

I can get access to the pages: along with these error below. It was the link that helped me go through the installation phase.

Warning: ob_start(): function "not found or invalid name in /var/www/authpuppy/vendor/symfony/lib/config/sfApplicationConfiguration.class.php on line 155

Notice: ob_start(): failed to create buffer in /var/www/authpuppy/lib/vendor/symfony/lib/config/sfApplicationConfiguration.class.php on line 155

________________________________________________________________________

If i use the normal link authpuppy.localhost which takes me to the main index page with admin and network access ; when i trigger any action link clicking on any button(admin,network ) it shoes a page cannot be displayed error.

Also i will like to ask, when adding a node, what is gw id ?

And I dont get a redirect to the login page when accessing e.g google.com i just get page not displayed error. Isnt there redirection ?

Additionally in my wifidog -d -f 7, i get Invalid request path ' '

Thank you.

Question information

Language:
English Edit question
Status:
Solved
For:
AuthPuppy Edit question
Assignee:
No assignee Edit question
Solved by:
Asoh Frank Senior
Solved:
Last query:
Last reply:
Revision history for this message
gbastien (gbastien02) said : 		#1

Can you provide screenshots, along with the exact and complete url of the requested pages when you get a page cannot be found error?

Also, you should make sure those warnings are not present because the gateway expects an exact answer, with no warning or anything else. Are you sure you have all the pre-requisites to run symfony framework? Check out http://symfony.com/legacy/doc/getting-started/1_4/en/02-prerequisites, there is a script to verify all pre-requisites.

The gw_id is the value you enter in the gateway's wifidog.conf file at gw id (near top of file). If it is commented out, the default value used is the interface's mac address. By installing the apNodeExtraPlugin, you'll get the functionnality to be able to automatically create a new node with the given gateway id when you first try to connect through a gateway if the node does not exist.

As for the invalid request path, if the problem is still there once you can access admin and login pages, please post the full debug output with the wifidog.conf file.

Revision history for this message
Asoh Frank Senior (asoh2004) said : 		#2

Dear gbastien,

Thanks for your efforts so far. How may i send you a print screen ? there are no attachment features here. Presently, i checked the symfony requirements and corrected 1 pre-requisite. Now, i can gladly access all the links without the need of
using the frontend_dev. But i still cannot have internet service after the splash network login and also no redirections on my web browser to authpuppy.localhost even though the terminal indicates that redirections are being done. Could this be a problem with the IPTABLES rules ? These are my outputs

 /usr/local/etc/wifidog-msg.html: No such file or directory
[7][Fri Apr 10 17:59:50 2020][4144](httpd_thread.c:68) Returned from httpdProcessRequest() for 192.168.1.2
[7][Fri Apr 10 17:59:50 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[6][Fri Apr 10 17:59:50 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[7][Fri Apr 10 17:59:50 2020][4144](ping_thread.c:72) Running ping()
[7][Fri Apr 10 17:59:50 2020][4144](ping_thread.c:109) Entering ping()
[7][Fri Apr 10 17:59:50 2020][4144](centralserver.c:188) Locking config
[7][Fri Apr 10 17:59:50 2020][4144](centralserver.c:188) Config locked
[7][Fri Apr 10 17:59:50 2020][4144](centralserver.c:232) Level 1: Calculated 1 auth servers in list
[7][Fri Apr 10 17:59:50 2020][4144](centralserver.c:248) Level 1: Resolving auth server [authpuppy.localhost]
[7][Fri Apr 10 17:59:50 2020][4144](util.c:139) Locking wd_gethostbyname()
[7][Fri Apr 10 17:59:50 2020][4144](util.c:139) wd_gethostbyname() locked
[7][Fri Apr 10 17:59:50 2020][4144](util.c:154) Unlocking wd_gethostbyname()
[7][Fri Apr 10 17:59:50 2020][4144](util.c:154) wd_gethostbyname() unlocked
[7][Fri Apr 10 17:59:50 2020][4144](centralserver.c:308) Level 1: Resolving auth server [authpuppy.localhost] succeeded = [192.168.1.1]
[7][Fri Apr 10 17:59:50 2020][4144](centralserver.c:333) Level 1: Connecting to auth server authpuppy.localhost:80
[7][Fri Apr 10 17:59:50 2020][4144](auth.c:83) Running fw_counter()
[7][Fri Apr 10 17:59:51 2020][4144](centralserver.c:359) Level 1: Successfully connected to auth server authpuppy.localhost:80
[7][Fri Apr 10 17:59:51 2020][4144](centralserver.c:190) Unlocking config
[7][Fri Apr 10 17:59:51 2020][4144](centralserver.c:190) Config unlocked
[7][Fri Apr 10 17:59:51 2020][4144](centralserver.c:197) Connected to auth server
[7][Fri Apr 10 17:59:51 2020][4144](ping_thread.c:167) HTTP Request to Server: [GET /ping/?gw_id=000B6B020792&sys_uptime=1023&sys_memfree=51680&sys_load=0.22&wifidog_uptime=481 HTTP/1.0
User-Agent: WiFiDog 20090925
Host: authpuppy.localhost

]
[7][Fri Apr 10 17:59:51 2020][4144](ping_thread.c:171) Reading response
[7][Fri Apr 10 17:59:51 2020][4144](gateway.c:259) Handler for SIGCHLD called. Trying to reap a child
[7][Fri Apr 10 17:59:51 2020][4144](gateway.c:263) Handler for SIGCHLD reaped child PID 4661
[7][Fri Apr 10 17:59:51 2020][4144](gateway.c:259) Handler for SIGCHLD called. Trying to reap a child
[7][Fri Apr 10 17:59:51 2020][4144](gateway.c:263) Handler for SIGCHLD reaped child PID 4663
[7][Fri Apr 10 17:59:51 2020][4144](firewall.c:237) Locking client list
[7][Fri Apr 10 17:59:51 2020][4144](firewall.c:237) Client list locked
[7][Fri Apr 10 17:59:51 2020][4144](firewall.c:348) Unlocking client list
[7][Fri Apr 10 17:59:51 2020][4144](firewall.c:348) Client list unlocked
[7][Fri Apr 10 17:59:51 2020][4144](ping_thread.c:199) Read 280 bytes, total now 280
[7][Fri Apr 10 17:59:51 2020][4144](ping_thread.c:217) Done reading reply, total 280 bytes
[7][Fri Apr 10 17:59:51 2020][4144](ping_thread.c:221) HTTP Response from Server: [HTTP/1.0 200 OK
Date: Fri, 10 Apr 2020 17:59:51 GMT
Server: Apache/2.2.22 (Debian)
X-Powered-By: PHP/5.4.4-12
Set-Cookie: authpuppy=4v2pv6akreg248nlb37qbmrhn5; path=/
Vary: Accept-Encoding
Content-Length: 5
Connection: close
Content-Type: text/html; charset=utf-8

Pong
]
[7][Fri Apr 10 17:59:51 2020][4144](ping_thread.c:228) Auth Server Says: Pong
[7][Fri Apr 10 17:59:51 2020][4144](httpd_thread.c:65) Processing request from 192.168.1.2
[7][Fri Apr 10 17:59:51 2020][4144](httpd_thread.c:66) Calling httpdProcessRequest() for 192.168.1.2
[6][Fri Apr 10 17:59:51 2020][4144](http.c:118) Captured 192.168.1.2 requesting [http%3A//www.authpuppy.org/] and re-directing them to login page
[7][Fri Apr 10 17:59:51 2020][4144](http.c:198) Redirecting client browser to http://authpuppy.localhost:80/login/?gw_address=192.168.1.1&gw_port=2060&gw_id=000B6B020792&url=http%3A//www.authpuppy.org/
[2][Fri Apr 10 17:59:51 2020][4144](http.c:299) Failed to open HTML message file /usr/local/etc/wifidog-msg.html: No such file or directory
[7][Fri Apr 10 17:59:51 2020][4144](httpd_thread.c:68) Returned from httpdProcessRequest() for 192.168.1.2
[7][Fri Apr 10 17:59:51 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[6][Fri Apr 10 17:59:51 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[6][Fri Apr 10 17:59:53 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[7][Fri Apr 10 17:59:53 2020][4144](httpd_thread.c:65) Processing request from 192.168.1.2
[7][Fri Apr 10 17:59:53 2020][4144](httpd_thread.c:66) Calling httpdProcessRequest() for 192.168.1.2
[6][Fri Apr 10 17:59:53 2020][4144](http.c:118) Captured 192.168.1.2 requesting [http%3A//5-pct.channel.facebook.com/ping%3Fpartition%3D19%26cb%3D509s] and re-directing them to login page
[7][Fri Apr 10 17:59:53 2020][4144](http.c:198) Redirecting client browser to http://authpuppy.localhost:80/login/?gw_address=192.168.1.1&gw_port=2060&gw_id=000B6B020792&url=http%3A//5-pct.channel.facebook.com/ping%3Fpartition%3D19%26cb%3D509s
[2][Fri Apr 10 17:59:53 2020][4144](http.c:299) Failed to open HTML message file /usr/local/etc/wifidog-msg.html: No such file or directory
[7][Fri Apr 10 17:59:53 2020][4144](httpd_thread.c:68) Returned from httpdProcessRequest() for 192.168.1.2
[7][Fri Apr 10 17:59:53 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[6][Fri Apr 10 17:59:53 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[7][Fri Apr 10 17:59:53 2020][4144](httpd_thread.c:65) Processing request from 192.168.1.2
[7][Fri Apr 10 17:59:53 2020][4144](httpd_thread.c:66) Calling httpdProcessRequest() for 192.168.1.2
[6][Fri Apr 10 17:59:53 2020][4144](http.c:118) Captured 192.168.1.2 requesting [http%3A//5-pct.channel.facebook.com/p%3Fpartition%3D19%26cb%3Dhf49] and re-directing them to login page
[7][Fri Apr 10 17:59:53 2020][4144](http.c:198) Redirecting client browser to http://authpuppy.localhost:80/login/?gw_address=192.168.1.1&gw_port=2060&gw_id=000B6B020792&url=http%3A//5-pct.channel.facebook.com/p%3Fpartition%3D19%26cb%3Dhf49
[2][Fri Apr 10 17:59:53 2020][4144](http.c:299) Failed to open HTML message file /usr/local/etc/wifidog-msg.html: No such file or directory
[7][Fri Apr 10 17:59:53 2020][4144](httpd_thread.c:68) Returned from httpdProcessRequest() for 192.168.1.2
[7][Fri Apr 10 17:59:53 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[6][Fri Apr 10 17:59:55 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[7][Fri Apr 10 17:59:55 2020][4144](httpd_thread.c:71) No valid request received from 192.168.1.2
[7][Fri Apr 10 17:59:55 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[6][Fri Apr 10 18:00:00 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[6][Fri Apr 10 18:00:00 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[6][Fri Apr 10 18:00:00 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[7][Fri Apr 10 18:00:00 2020][4144](httpd_thread.c:71) No valid request received from 192.168.1.2
[7][Fri Apr 10 18:00:00 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[7][Fri Apr 10 18:00:00 2020][4144](httpd_thread.c:71) No valid request received from 192.168.1.2
[7][Fri Apr 10 18:00:00 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[7][Fri Apr 10 18:00:00 2020][4144](httpd_thread.c:71) No valid request received from 192.168.1.2
[7][Fri Apr 10 18:00:00 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[7][Fri Apr 10 18:00:01 2020][4144](httpd_thread.c:65) Processing request from 192.168.1.2
[7][Fri Apr 10 18:00:01 2020][4144](httpd_thread.c:66) Calling httpdProcessRequest() for 192.168.1.2
Invalid request path ''
[7][Fri Apr 10 18:00:01 2020][4144](httpd_thread.c:68) Returned from httpdProcessRequest() for 192.168.1.2
[7][Fri Apr 10 18:00:01 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[6][Fri Apr 10 18:00:02 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[6][Fri Apr 10 18:00:02 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[7][Fri Apr 10 18:00:02 2020][4144](httpd_thread.c:65) Processing request from 192.168.1.2
[7][Fri Apr 10 18:00:02 2020][4144](httpd_thread.c:66) Calling httpdProcessRequest() for 192.168.1.2
[6][Fri Apr 10 18:00:02 2020][4144](http.c:118) Captured 192.168.1.2 requesting [http%3A//creativecommons.org/images/public/cc-GPL-a.png] and re-directing them to login page
[7][Fri Apr 10 18:00:02 2020][4144](http.c:198) Redirecting client browser to http://authpuppy.localhost:80/login/?gw_address=192.168.1.1&gw_port=2060&gw_id=000B6B020792&url=http%3A//creativecommons.org/images/public/cc-GPL-a.png
[2][Fri Apr 10 18:00:02 2020][4144](http.c:299) Failed to open HTML message file /usr/local/etc/wifidog-msg.html: No such file or directory
[7][Fri Apr 10 18:00:02 2020][4144](httpd_thread.c:68) Returned from httpdProcessRequest() for 192.168.1.2
[7][Fri Apr 10 18:00:02 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[7][Fri Apr 10 18:00:05 2020][4144](httpd_thread.c:65) Processing request from 192.168.1.2
[7][Fri Apr 10 18:00:05 2020][4144](httpd_thread.c:66) Calling httpdProcessRequest() for 192.168.1.2
[6][Fri Apr 10 18:00:05 2020][4144](http.c:118) Captured 192.168.1.2 requesting [http%3A//creativecommons.org/images/public/cc-GPL-a.png] and re-directing them to login page
[7][Fri Apr 10 18:00:05 2020][4144](http.c:198) Redirecting client browser to http://authpuppy.localhost:80/login/?gw_address=192.168.1.1&gw_port=2060&gw_id=000B6B020792&url=http%3A//creativecommons.org/images/public/cc-GPL-a.png
[2][Fri Apr 10 18:00:05 2020][4144](http.c:299) Failed to open HTML message file /usr/local/etc/wifidog-msg.html: No such file or directory
[7][Fri Apr 10 18:00:05 2020][4144](httpd_thread.c:68) Returned from httpdProcessRequest() for 192.168.1.2
[7][Fri Apr 10 18:00:05 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[6][Fri Apr 10 18:00:05 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[7][Fri Apr 10 18:00:05 2020][4144](httpd_thread.c:71) No valid request received from 192.168.1.2
[7][Fri Apr 10 18:00:05 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[6][Fri Apr 10 18:00:12 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[6][Fri Apr 10 18:00:12 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[7][Fri Apr 10 18:00:12 2020][4144](httpd_thread.c:65) Processing request from 192.168.1.2
[7][Fri Apr 10 18:00:12 2020][4144](httpd_thread.c:66) Calling httpdProcessRequest() for 192.168.1.2
[6][Fri Apr 10 18:00:12 2020][4144](http.c:118) Captured 192.168.1.2 requesting [http%3A//creativecommons.org/images/public/cc-GPL-a.png] and re-directing them to login page
[7][Fri Apr 10 18:00:12 2020][4144](http.c:198) Redirecting client browser to http://authpuppy.localhost:80/login/?gw_address=192.168.1.1&gw_port=2060&gw_id=000B6B020792&url=http%3A//creativecommons.org/images/public/cc-GPL-a.png
[2][Fri Apr 10 18:00:12 2020][4144](http.c:299) Failed to open HTML message file /usr/local/etc/wifidog-msg.html: No such file or directory
[7][Fri Apr 10 18:00:12 2020][4144](httpd_thread.c:68) Returned from httpdProcessRequest() for 192.168.1.2
[7][Fri Apr 10 18:00:12 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2
[6][Fri Apr 10 18:00:18 2020][4144](gateway.c:474) Received connection from 192.168.1.2, spawning worker thread
[7][Fri Apr 10 18:00:18 2020][4144](httpd_thread.c:71) No valid request received from 192.168.1.2
[7][Fri Apr 10 18:00:18 2020][4144](httpd_thread.c:73) Closing connection with 192.168.1.2

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This is my wifidog.conf output

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

# $Id: wifidog.conf 1422 2009-09-25 22:38:13Z gbastien $
# WiFiDog Configuration file

# Parameter: GatewayID
# Default: default
# Optional
#
# Set this to the node ID on the auth server
# This is used to give a customized login page to the clients and for
# monitoring/statistics purpose. If you run multiple gateways on the same
# machine each gateway needs to have a different gateway id.
# If none is supplied, the mac address of the GatewayInterface interface will b$
# without the : separators

# GatewayID default

# Parameter: ExternalInterface
# Default: NONE
# Optional
#
# Set this to the external interface (the one going out to the Inernet or your $
# Typically vlan1 for OpenWrt, and eth0 or ppp0 otherwise,
# Normally autodetected

ExternalInterface eth0

# Parameter: GatewayInterface
# Default: NONE
# Mandatory
#
# Set this to the internal interface (typically your wifi interface).
# Typically br0 for whiterussian, br-lan for kamikaze (by default the wifi inte$
# and eth1, wlan0, ath0, etc. otherwise
# You can get this interface with the ifconfig command and finding your wifi in$

GatewayInterface wlan0

# Parameter: GatewayAddress
# Default: Find it from GatewayInterface
# Optional
#
# Set this to the internal IP address of the gateway. Not normally required.

GatewayAddress 192.168.1.1

# Parameter: HtmlMessageFile
# Default: wifidog-msg.html
# Optional
#
# This allows you to specify a custome HTML file which will be used for
# system errors by the gateway. Any $title, $message and $node variables
# used inside the file will be replaced.
#
# HtmlMessageFile /opt/wifidog/etc/wifidog-.html

# Parameter: AuthServer
# Default: NONE
# Mandatory, repeatable
#
# This allows you to configure your auth server(s). Each one will be tried in order, untill one responds.
# Set this to the hostname or IP of your auth server(s), the path where
# WiFiDog-auth resides in and the port it listens on.
#AuthServer {
# Hostname (Mandatory; Default: NONE)
# SSLAvailable (Optional; Default: no; Possible values: yes, no)
# SSLPort (Optional; Default: 443)
# HTTPPort (Optional; Default: 80)
# Path (Optional; Default: /wifidog/ Note: The path must be both prefixed and suffixed by /. Use a single / for server root.)
# LoginScriptPathFragment (Optional; Default: login/? Note: This is the script the user will be sent to for login.)
# PortalScriptPathFragment (Optional; Default: portal/? Note: This is the script the user will be sent to after a successfull login.)
# MsgScriptPathFragment (Optional; Default: gw_message.php? Note: This is the script the user will be sent to upon error to read a readable message.)
# PingScriptPathFragment (Optional; Default: ping/? Note: This is the script the user will be sent to upon error to read a readable message.)
# AuthScriptPathFragment (Optional; Default: auth/? Note: This is the script the user will be sent to upon error to read a readable message.)
#}

AuthServer {
    Hostname authpuppy.localhost
    SSLAvailable no
    Path /
}

#AuthServer {
# Hostname auth2.ilesansfil.org
# SSLAvailable yes
# Path /
#}

# Parameter: Daemon
# Default: 1
# Optional
#
# Set this to true if you want to run as a daemon
# Daemon 1

# Parameter: GatewayPort
# Default: 2060
# Optional
#
# Listen on this port
# GatewayPort 2060

# Parameter: HTTPDName
# Default: WiFiDog
# Optional
#
# Define what name the HTTPD server will respond
# HTTPDName WiFiDog

# Parameter: HTTPDMaxConn
# Default: 10
# Optional
#
# How many sockets to listen to
# HTTPDMaxConn 10

# Parameter: HTTPDRealm
# Default: WiFiDog
# Optional
#
# The name of the HTTP authentication realm. This only used when a user
# tries to access a protected WiFiDog internal page. See HTTPUserName.
# HTTPDRealm WiFiDog
# Parameter: HTTPDUserName / HTTPDPassword
# Default: unset
# Optional
#
# The gateway exposes some information such as the status page through its web
# interface. This information can be protected with a username and password,
# which can be set through the HTTPDUserName and HTTPDPassword parameters.
# HTTPDUserName admin
# HTTPDPassword secret

# Parameter: CheckInterval
# Default: 60
# Optional
#
# How many seconds should we wait between timeout checks. This is also
# how often the gateway will ping the auth server and how often it will
# update the traffic counters on the auth server. Setting this too low
# wastes bandwidth, setting this too high will cause the gateway to take
# a long time to switch to it's backup auth server(s).
# CheckInterval 60

# Parameter: ClientTimeout
# Default: 5
# Optional
#
# Set this to the desired of number of CheckInterval of inactivity before a client is logged out
# The timeout will be INTERVAL * TIMEOUT
ClientTimeout 5

# Parameter: TrustedMACList
# Default: none
# Optional
#
# Comma separated list of MAC addresses who are allowed to pass
# through without authentication
#TrustedMACList 00:00:DE:AD:BE:AF,00:00:C0:1D:F0:0D

# Parameter: FirewallRuleSet
# Default: none
# Mandatory
#
# Groups a number of FirewallRule statements together.

# Parameter: FirewallRule
# Default: none
#
# Define one firewall rule in a rule set.

# Rule Set: global
#
# Used for rules to be applied to all other rulesets except locked.
FirewallRuleSet global {
    ## To block SMTP out, as it's a tech support nightmare, and a legal liability
    #FirewallRule block tcp port 25

    ## Use the following if you don't want clients to be able to access machines on

 ## the private LAN that gives internet access to wifidog. Note that this is not
    ## client isolation; The laptops will still be able to talk to one another, as
    ## well as to any machine bridged to the wifi of the router.
    # FirewallRule block to 192.168.0.0/16
    # FirewallRule block to 172.16.0.0/12
    # FirewallRule block to 10.0.0.0/8

    ## This is an example ruleset for the Teliphone service.
    #FirewallRule allow udp to 69.90.89.192/27
    #FirewallRule allow udp to 69.90.85.0/27
    #FirewallRule allow tcp port 80 to 69.90.89.205
}

# Rule Set: validating-users
#
# Used for new users validating their account
FirewallRuleSet validating-users {
    FirewallRule allow to 0.0.0.0/0

# Rule Set: known-users
#
# Used for normal validated users.
FirewallRuleSet known-users {
    FirewallRule allow to 0.0.0.0/0
}

# Rule Set: unknown-users
#
# Used for unvalidated users, this is the ruleset that gets redirected.
#
# XXX The redirect code adds the Default DROP clause.
FirewallRuleSet unknown-users {
    FirewallRule allow udp port 53
    FirewallRule allow tcp port 53
    FirewallRule allow udp port 67
    FirewallRule allow tcp port 67
}

# Rule Set: locked-users
#
# Not currently used
FirewallRuleSet locked-users {
    FirewallRule block to 0.0.0.0/0
}

Revision history for this message
Asoh Frank Senior (asoh2004) said : 		#3

At the moment, i fixed the redirection by manually adding the file (wifidog-msg.html) into the path (/usr/local/etc/wifidog-msg.html ) I wonder why it didnt go there during installation. Presently i am faced now with only the problem of no internet.

Revision history for this message
Asoh Frank Senior (asoh2004) said : 		#4

And now i finally have internet !!!!!!!!! Wow !! !!!!!!! relieved ! I disabled all the plugins and allowed just splashonly and it worked.

Please 1 last question. Can Wifidog/authpuppy work in Layer3 topologies ?

Revision history for this message
Asoh Frank Senior (asoh2004) said : 		#5

.