From DD-WRT Wiki
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, pass them around, but if you actually used NoCat, one might notice NoCat runs a firewall script using IPTABLES. It blocks all' traffic, 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 Log Out 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 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
-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.
-incorrect, 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 (I.e. The Internet Connection) 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 the status page is written much better than the crappy default splash.html.
 Fix the article
First, the article needs to explain that a bunch of the "variables" don't work. For instance, last conection time and the number of connected users.
Then, the stupid article needs to better explain how to use the workaround section. I had no idea how the hell to "create" the .sh files. I eventually found out through other sources that you can do it with the VI editor. And i STILL dont know what the hell the "less" command is supposed to do. That needs to be explained.
I've found out that nocat will refuse to work if my router is set to the "wireless access point" type configurations. These configurations obviously apply when the device running nocat is NOT the "internet router", and thus the name "wireless access point". The wiki on these configs explain disabling the WAN DHCP option. This allows the router to simply act as a client on a lan. But when you do this, nocast stops working. This is asinine, and it should be clearly explained to nocat users to set nocat up first, get it working, and then figure out what extra options will make nocat fail. This is one of those options.
Also, why doesn't the article explain how to troubleshoot nocat? Which logs to look at if there's problems? I still don't know, and it needs to be in this article.
ScreamingAnger 09:35, 18 June 2009 (CEST)