From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 02:21, 15 January 2006 (edit) (Talk)
(What is it)
← Previous diff
Revision as of 02:24, 15 January 2006 (edit) (undo) (Talk)
(What is it)
Next diff →
Line 21: Line 21:
-'''Troubleshooting:'''+'''Splash Page Code'''
-'''Problem 1:'''+'''Typical Oversight'''
-I've setup an internal webserver on our network, and gotten so far as to get nocatsplash to redirect web requests, for example, requests for etc., to the internal webserver instead.<BR/>+A typical problem with most installations is the administrator (you) forgetting that the splash page must contain a form with a button that submits certain data to the router, allowing it to "know" which clients have or have not visited the splash page.
-On my test client machine, I couldn't go any further than the redirect page. I was always redirected to the splash page. It seemed the router had no way of 'knowing' I had already seen the splash.html screen. And I have no idea, from the existing information, what to code onto the splash.html for an 'I Accept' or 'Continue' button.+
'''Solution:''' '''Solution:'''
-The Form code for your "I Accept" button is as follows. This was taken from the original nocat splash page.+The Form code for your "I Accept" button is similar to the following. This was taken from the original nocat splash page:
<pre> <pre>

Revision as of 02:24, 15 January 2006


What is it

Enabling the use of NoCatSplash allows you to redirect a client to a specific web page when connecting via wireless or wired. It can redirect the client to a Splash URL hosted online (not on the router's filsystem). It can use the JFFS2 filesystem services on the router, so hosting the splash page can be done directly on the router. After being redirected to the splash page, the client can click on an 'I Agree', 'Continue' or similar button of your choosing on the splash page, and it brings the user to the page they were originally loading (or sends the client to the site of your choosing).

This could be use to advertise your neighbourhood wLAN, or display a splash screen in a cafe. While Authentication was originally envisioned for NoCat (NoCatAuth), support has been removed to make this as streamlined as possible. The DD-WRT version just displays a splash screen and nothing else. It will intercept the client's browser when the timeout period expires. So, once a day, or whatever interval you choose, the client will pull up the splash screen.

For me, NoCatSplash has been an easy point and click affair, using a Splash URL (not hosted locally on the router).

Simply enable NoCatSplash, enter your Homepage (this is the page people will be redirected to, after seeing the splash page), then add your Allowed Web Hosts (This should be/include the domain of the Splash URL. ex: if your Splash url is on; Your allowed host should be (Don't have the http:// part on the allowed web hosts), Dont change the Document Root (leave it alone), Enter your Splash URL (ex:

I left all of the other settings alone, and mine works fine!

A Noteable Quirk: Your Splash page won't show anything linked outside of the html file if the Splash URL isn't hosted on the router or through a Samba mount. For example .css and images won't load, but style tags in the HEAD of your html page will.

Splash Page Code

Typical Oversight A typical problem with most installations is the administrator (you) forgetting that the splash page must contain a form with a button that submits certain data to the router, allowing it to "know" which clients have or have not visited the splash page.

Solution: The Form code for your "I Accept" button is similar to the following. This was taken from the original nocat splash page:

 <form name="login" method="post" action="">
     <div align="center">
          <input type="hidden" name="accept_terms" value="yes" />       
          <input type="hidden" name="redirect" value="">
          <input type="hidden"    name="mode_login">
          <!--<input type="image"    name="mode_login"   src="images/login.gif" border="0">-->
          <input type="submit" value="enter">
          <!--<input type="submit" value="submit">-->

Alternatively in the above example you can use "$redirect" for the redirect location (instead of to allow the client to browse to their originally intended site vs. always being redirected to the site of your choosing.




To make the configuration options appear, you have to enable NoCatSplash then Save the configuration. Now you can configure the options.
When finished configuring, use "Reboot Router".

Gateway Name
The name of the gateway. Whatever you want to call it. "Joe's Pizza Shop and free DSL Cafe" for example. Use the variable $GatewayName in your splash.html page to display this.

Space separated list of hostnames.
List any hosts (for example, the webserver with the splash page, or other websites) that you would like to allow clients to have web access to (TCP port 80 (HTTP) and 443 (HTTPS?)) before they "log in" (before they click on "I Accept" in your splash page), however actual authentication is not supported.
List any webservers, that you would like connecting clients to be able to access, before clicking on I Agree on the initial nocatsplash screen. Such as the webserver hosting your EULA or Welcome Page, if it isn't the router itself.

Document Root
Where all of the application templates (including SplashForm) are hiding. Can be different from Apache's DocumentRoot.
splash.html is the form displayed to users on capture.

Splash URL
Optional URL to fetch dynamic remote splash page from.
Leave empty if using a page stored on the router.

Space separated list of ports.
Specify TCP ports to denied access to when public class users login. All others will be allowed. If nothing is specified, access is granted to all ports to public class users.

You should *always* exclude port 25 (SMTP), unless you want to run a portal for wanton spam sending. Users should have their own way of sending mail. It sucks, but that's the way it is.

Login Timeout
How much time, in seconds, elapses before the client has to see the splash screen again, and click on 'I Agree'. How often a client is shown the EULA or other designated splash page.

For Open Mode portals, you probably want to set LoginTimeout to something large (like 86400, for one notification per day). Open Mode, is the only mode supported at this time.

Log verbosity (to syslogd)

  • 0 is (almost) no logging.
  • 10 is log everything.
  • 5 is probably a safe middle road.

Route only
Required only if you DO NOT want your gateway to act as a NAT.
Enable this only if you're running a strictly routed network, and don't need the gateway to enable NAT for you. You would not normally use this option. So if you don't understand it, leave it to No/Off.

A few things I found while looking for documentation on the net: In the nocat.conf file (you'll have to telnet or ssh into the router to set these)
comment: The only supported option at this time. I don't think it has to be set. GatewayMode Open
comment: The IP Range which will see the splash page.
comment: The LAN/wLAN IP of the router. I don't think it needs to be set
comment: The DNS server. Again, I don't think this needs to be set here.

Advanced configuration


Configuration file:
/etc # cat nocat.conf

nvram entries:

NC_ExcludePorts=25 21 23


The TCP port to bind the gateway service to. 5280 is de-facto standard for NoCatSplash.

Documentation source
NoCatSplash is copyright (c) 2004 - 2005 Schuyler Erle <> and Rob Flickenger <>, and is distributed under the GNU Public License v2 or better.
The original manual page is copyright 2005 Keegan Quinn.