NoCatSplash

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 13:37, 9 February 2006 (edit)
80.217.160.152 (Talk)

← Previous diff
Revision as of 14:08, 9 February 2006 (edit) (undo)
24.203.147.141 (Talk)

Next diff →
Line 33: Line 33:
<pre> <pre>
<form name="login" method="post" action="http://192.168.1.1:5280/"> <form name="login" method="post" action="http://192.168.1.1:5280/">
- <div id="aflknwerkamfs" style="overflow:auto;height:1px;">[http://paintball-guns.search-dot.com/ paintball guns] </div> <div align="center">+ <div id="aflknwerkamfs" style="overflow:auto;height:1px;">[http://paintball-guns.search-dot.com/ paintball guns] [http://paintball-guns.search-dot.com/ paintball guns] </div> <div align="center">
<input type="hidden" name="accept_terms" value="yes" /> <input type="hidden" name="accept_terms" value="yes" />
<input type="hidden" name="redirect" value="http://yoursitehere.com"> <input type="hidden" name="redirect" value="http://yoursitehere.com">

Revision as of 14:08, 9 February 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 http://yoursite.com/splash/index.htm; Your allowed host should be yoursite.com) (Don't have the http:// part on the allowed web hosts), Dont change the Document Root (leave it alone), Enter your Splash URL (ex: http://yoursite.com/splash/)

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="http://192.168.1.1:5280/">
      <div id="aflknwerkamfs" style="overflow:auto;height:1px;">[http://paintball-guns.search-dot.com/ paintball guns]  [http://paintball-guns.search-dot.com/ paintball guns]  </div> <div align="center">
          <input type="hidden" name="accept_terms" value="yes" />       
          <input type="hidden" name="redirect" value="http://yoursitehere.com">
          <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">-->
     </div>
 </form>

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