From DD-WRT Wiki

Revision as of 19:27, 16 May 2008 by S2s2 (Talk | contribs)
Jump to: navigation, search

Comments brought from Wiki article:

For instance, I found some of these comments from the article to be completely erroneous. Comment: Since this is a web portal capture only, no other traffic is blocked.

Answer: I don't know what drugs you are smoking dude, but if you actually used NoCat, one notices it runs a firewall script using IPTABLES. It blocks all traffic, honey, unless the user clicks on I Agree. After 24 hours, or whatever the timeout is set to (in seconds), the user is BLOCKED again, and must log in. At forced LogOut time, if the client is -not- using an HTTP client (Like a web browser), it just simply fails to connect (if it's using TCP or UDP protocols). The client must then open a Web Browser, like Opera or Firefox or ewwww, Internet Exploder, without setting it for any remote proxies, just a direct internet connection. Whatever their default http:// homepage is, the client user is redirected to http://routerLANIP:5280/ (and shown the beautifus splash page).

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

-Yes, this is true. It can be modified in the nocat.conf

Just a couple things to keep in mind when using/testing this:

1. Since this is a web portal capture only, no other traffic is blocked.
-wrong, see above.

2. DNS must happen in order for the redirection to occur - so if you are testing on a machine that is not connected up you will not see the capture page.
-yes. The DD-WRT box must have a valid upstream (WAN) connection which is working. If the DSL line goes down, nocat ceases to function also. Upstream DNS MUST work.

3. If you attempt to access the "status" page, then you must have a status.html page there. Variables available are $GatewayName, $LocalTime, $GatewayStartTime, $TotalConnections, $Version, $GatewayMode, $LoginTimeout, $IdleTimeout, $HomePage, $AllowedWebHosts, $LastConnectionTime, $ConnectionCount, $UserTable

- This is all total nonsense. Why make this a point?!? There is already a great default status page. If the owner of the DD-WRT box simply uses the built-in pages to begin with, status.html already exists (and is quite a bit better than the default splash.html).