http://wiki.dd-wrt.com/wiki/index.php?title=Talk:NoCatSplash&action=history&feed=atom Talk:NoCatSplash - Revision history 2024-03-28T14:52:35Z Revision history for this page on the wiki MediaWiki 1.10.1 http://wiki.dd-wrt.com/wiki/index.php?title=Talk:NoCatSplash&diff=25880&oldid=prev ScreamingAnger: /* Fix the article */ 2009-06-18T07:39:44Z <p><span class="autocomment">Fix the article</span></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 07:39, 18 June 2009</td> </tr> <tr><td colspan="2" align="left"><strong>Line 30:</strong></td> <td colspan="2" align="left"><strong>Line 30:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Then, the stupid article needs to better explain how to use the workaround section. I had no idea how the hell to &quot;create&quot; 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 &quot;less&quot; command is supposed to do. That needs to be explained.</td><td> </td><td style="background: #eee; font-size: smaller;">Then, the stupid article needs to better explain how to use the workaround section. I had no idea how the hell to &quot;create&quot; 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 &quot;less&quot; command is supposed to do. That needs to be explained.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">I've found out that nocat will refuse to work if my router is set to the &quot;wireless access point&quot; type configurations. <del style="color: red; font-weight: bold; text-decoration: none;">Specifically, if i set up my router to </del>the <del style="color: red; font-weight: bold; text-decoration: none;">point where </del>nocat <del style="color: red; font-weight: bold; text-decoration: none;">works</del>, and <del style="color: red; font-weight: bold; text-decoration: none;">then i disable it from getting a </del>DHCP <del style="color: red; font-weight: bold; text-decoration: none;">ip address (or set it </del>to <del style="color: red; font-weight: bold; text-decoration: none;">ANYTHING besides DHCP)</del>, <del style="color: red; font-weight: bold; text-decoration: none;">nocat </del>stops working. This is asinine, and it should be clearly explained to nocat users to set <del style="color: red; font-weight: bold; text-decoration: none;">this </del>up first, and then figure out what extra options will make nocat fail.</td><td>+</td><td style="background: #cfc; font-size: smaller;">I've found out that nocat will refuse to work if my router is set to the &quot;wireless access point&quot; type configurations. <ins style="color: red; font-weight: bold; text-decoration: none;">These configurations obviously apply when </ins>the <ins style="color: red; font-weight: bold; text-decoration: none;">device running </ins>nocat <ins style="color: red; font-weight: bold; text-decoration: none;">is NOT the &quot;internet router&quot;</ins>, and <ins style="color: red; font-weight: bold; text-decoration: none;">thus the name &quot;wireless access point&quot;. The wiki on these configs explain disabling the WAN </ins>DHCP <ins style="color: red; font-weight: bold; text-decoration: none;">option. This allows the router </ins>to <ins style="color: red; font-weight: bold; text-decoration: none;">simply act as a client on a lan. But when you do this</ins>, <ins style="color: red; font-weight: bold; text-decoration: none;">nocast </ins>stops working. This is asinine, and it should be clearly explained to nocat users to set <ins style="color: red; font-weight: bold; text-decoration: none;">nocat </ins>up first<ins style="color: red; font-weight: bold; text-decoration: none;">, get it working</ins>, and then figure out what extra options will make nocat fail<ins style="color: red; font-weight: bold; text-decoration: none;">. This is one of those options</ins>.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">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.</td><td> </td><td style="background: #eee; font-size: smaller;">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.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">[[User:ScreamingAnger|ScreamingAnger]] 09:35, 18 June 2009 (CEST)</td><td> </td><td style="background: #eee; font-size: smaller;">[[User:ScreamingAnger|ScreamingAnger]] 09:35, 18 June 2009 (CEST)</td></tr> </table> ScreamingAnger http://wiki.dd-wrt.com/wiki/index.php?title=Talk:NoCatSplash&diff=25879&oldid=prev ScreamingAnger: /* Fix the article */ 2009-06-18T07:35:11Z <p><span class="autocomment">Fix the article</span></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 07:35, 18 June 2009</td> </tr> <tr><td colspan="2" align="left"><strong>Line 33:</strong></td> <td colspan="2" align="left"><strong>Line 33:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">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.</td><td> </td><td style="background: #eee; font-size: smaller;">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.</td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;"></td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;">[[User:ScreamingAnger|ScreamingAnger]] 09:35, 18 June 2009 (CEST)</td></tr> </table> ScreamingAnger http://wiki.dd-wrt.com/wiki/index.php?title=Talk:NoCatSplash&diff=25878&oldid=prev ScreamingAnger: Fix the article 2009-06-18T07:31:05Z <p>Fix the article</p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 07:31, 18 June 2009</td> </tr> <tr><td colspan="2" align="left"><strong>Line 23:</strong></td> <td colspan="2" align="left"><strong>Line 23:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">- 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.</td><td> </td><td style="background: #eee; font-size: smaller;">- 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.</td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;"></td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;">== Fix the article ==</td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;"></td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;">First, the article needs to explain that a bunch of the &quot;variables&quot; don't work. For instance, last conection time and the number of connected users.</td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;"></td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;">Then, the stupid article needs to better explain how to use the workaround section. I had no idea how the hell to &quot;create&quot; 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 &quot;less&quot; command is supposed to do. That needs to be explained.</td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;"></td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;">I've found out that nocat will refuse to work if my router is set to the &quot;wireless access point&quot; type configurations. Specifically, if i set up my router to the point where nocat works, and then i disable it from getting a DHCP ip address (or set it to ANYTHING besides DHCP), nocat stops working. This is asinine, and it should be clearly explained to nocat users to set this up first, and then figure out what extra options will make nocat fail.</td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;"></td></tr> <tr><td colspan="2">&nbsp;</td><td>+</td><td style="background: #cfc; font-size: smaller;">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.</td></tr> </table> ScreamingAnger http://wiki.dd-wrt.com/wiki/index.php?title=Talk:NoCatSplash&diff=21151&oldid=prev S2s2: minor changes. 2008-07-04T07:28:54Z <p>minor changes.</p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 07:28, 4 July 2008</td> </tr> <tr><td colspan="2" align="left"><strong>Line 4:</strong></td> <td colspan="2" align="left"><strong>Line 4:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Comment: ''Since this is a web portal capture only, no other traffic is blocked.''</td><td> </td><td style="background: #eee; font-size: smaller;">Comment: ''Since this is a web portal capture only, no other traffic is blocked.''</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">Answer: I don't know what drugs you are smoking dude, but if you actually used NoCat, one <del style="color: red; font-weight: bold; text-decoration: none;">notices it </del>runs a firewall script using IPTABLES. It blocks '''all''' traffic<del style="color: red; font-weight: bold; text-decoration: none;">, honey</del>, 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 <del style="color: red; font-weight: bold; text-decoration: none;">LogOut </del>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 <del style="color: red; font-weight: bold; text-decoration: none;">ewwww, </del>Internet Exploder<del style="color: red; font-weight: bold; text-decoration: none;">, </del>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).</td><td>+</td><td style="background: #cfc; font-size: smaller;">Answer: I don't know what drugs you are smoking dude<ins style="color: red; font-weight: bold; text-decoration: none;">, '''pass them around''</ins>, but if you actually used NoCat, one <ins style="color: red; font-weight: bold; text-decoration: none;">might notice NoCat </ins>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 <ins style="color: red; font-weight: bold; text-decoration: none;">Log Out </ins>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).</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">The TCP port to bind the gateway service to. 5280 is de-facto standard for</td><td> </td><td style="background: #eee; font-size: smaller;">The TCP port to bind the gateway service to. 5280 is de-facto standard for</td></tr> <tr><td colspan="2" align="left"><strong>Line 14:</strong></td> <td colspan="2" align="left"><strong>Line 14:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">1. Since this is a web portal capture only, no other traffic is blocked.&lt;br&gt;</td><td> </td><td style="background: #eee; font-size: smaller;">1. Since this is a web portal capture only, no other traffic is blocked.&lt;br&gt;</td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">-<del style="color: red; font-weight: bold; text-decoration: none;">wrong</del>, see above.</td><td>+</td><td style="background: #cfc; font-size: smaller;">-<ins style="color: red; font-weight: bold; text-decoration: none;">incorrect</ins>, see above.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">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.&lt;br&gt;</td><td> </td><td style="background: #eee; font-size: smaller;">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.&lt;br&gt;</td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">-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.</td><td>+</td><td style="background: #cfc; font-size: smaller;">-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 <ins style="color: red; font-weight: bold; text-decoration: none;">(I.e. The Internet Connection) </ins>MUST work.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">3. If you attempt to access the &quot;status&quot; page, then you must have a status.html page there. Variables available are $GatewayName, $LocalTime, $GatewayStartTime, $TotalConnections, $Version, $GatewayMode, $LoginTimeout, $IdleTimeout, $HomePage,</td><td> </td><td style="background: #eee; font-size: smaller;">3. If you attempt to access the &quot;status&quot; page, then you must have a status.html page there. Variables available are $GatewayName, $LocalTime, $GatewayStartTime, $TotalConnections, $Version, $GatewayMode, $LoginTimeout, $IdleTimeout, $HomePage,</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">$AllowedWebHosts, $LastConnectionTime, $ConnectionCount, $UserTable&lt;br&gt;</td><td> </td><td style="background: #eee; font-size: smaller;">$AllowedWebHosts, $LastConnectionTime, $ConnectionCount, $UserTable&lt;br&gt;</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">- 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 <del style="color: red; font-weight: bold; text-decoration: none;">(</del>and is <del style="color: red; font-weight: bold; text-decoration: none;">quite a bit </del>better than the default splash.html<del style="color: red; font-weight: bold; text-decoration: none;">)</del>.</td><td>+</td><td style="background: #cfc; font-size: smaller;">- 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<ins style="color: red; font-weight: bold; text-decoration: none;">, </ins>and <ins style="color: red; font-weight: bold; text-decoration: none;">the status page </ins>is <ins style="color: red; font-weight: bold; text-decoration: none;">written much </ins>better than the <ins style="color: red; font-weight: bold; text-decoration: none;">crappy </ins>default splash.html.</td></tr> </table> S2s2 http://wiki.dd-wrt.com/wiki/index.php?title=Talk:NoCatSplash&diff=20510&oldid=prev S2s2 at 19:27, 16 May 2008 2008-05-16T19:27:04Z <p></p> <table border='0' width='98%' cellpadding='0' cellspacing='4' style="background-color: white;"> <tr> <td colspan='2' width='50%' align='center' style="background-color: white;">←Older revision</td> <td colspan='2' width='50%' align='center' style="background-color: white;">Revision as of 19:27, 16 May 2008</td> </tr> <tr><td colspan="2" align="left"><strong>Line 7:</strong></td> <td colspan="2" align="left"><strong>Line 7:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">The TCP port to bind the gateway service to. 5280 is de-facto standard for</td><td> </td><td style="background: #eee; font-size: smaller;">The TCP port to bind the gateway service to. 5280 is de-facto standard for</td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">NoCatSplash.</td><td>+</td><td style="background: #cfc; font-size: smaller;">NoCatSplash.<ins style="color: red; font-weight: bold; text-decoration: none;">&lt;br&gt;</ins></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">-Yes, this is true. It can be modified in the nocat.conf</td><td> </td><td style="background: #eee; font-size: smaller;">-Yes, this is true. It can be modified in the nocat.conf</td></tr> <tr><td colspan="2" align="left"><strong>Line 13:</strong></td> <td colspan="2" align="left"><strong>Line 13:</strong></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">Just a couple things to keep in mind when using/testing this:</td><td> </td><td style="background: #eee; font-size: smaller;">Just a couple things to keep in mind when using/testing this:</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">1. Since this is a web portal capture only, no other traffic is blocked.</td><td>+</td><td style="background: #cfc; font-size: smaller;">1. Since this is a web portal capture only, no other traffic is blocked.<ins style="color: red; font-weight: bold; text-decoration: none;">&lt;br&gt;</ins></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">-wrong, see above.</td><td> </td><td style="background: #eee; font-size: smaller;">-wrong, see above.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">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.</td><td>+</td><td style="background: #cfc; font-size: smaller;">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.<ins style="color: red; font-weight: bold; text-decoration: none;">&lt;br&gt;</ins></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">-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.</td><td> </td><td style="background: #eee; font-size: smaller;">-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.</td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">3. If you attempt to access the &quot;status&quot; page, then you must have a status.html page there. Variables available are $GatewayName, $LocalTime, $GatewayStartTime, $TotalConnections, $Version, $GatewayMode, $LoginTimeout, $IdleTimeout, $HomePage,</td><td> </td><td style="background: #eee; font-size: smaller;">3. If you attempt to access the &quot;status&quot; page, then you must have a status.html page there. Variables available are $GatewayName, $LocalTime, $GatewayStartTime, $TotalConnections, $Version, $GatewayMode, $LoginTimeout, $IdleTimeout, $HomePage,</td></tr> <tr><td>-</td><td style="background: #ffa; font-size: smaller;">$AllowedWebHosts, $LastConnectionTime, $ConnectionCount, $UserTable</td><td>+</td><td style="background: #cfc; font-size: smaller;">$AllowedWebHosts, $LastConnectionTime, $ConnectionCount, $UserTable<ins style="color: red; font-weight: bold; text-decoration: none;">&lt;br&gt;</ins></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;"></td><td> </td><td style="background: #eee; font-size: smaller;"></td></tr> <tr><td> </td><td style="background: #eee; font-size: smaller;">- 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).</td><td> </td><td style="background: #eee; font-size: smaller;">- 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).</td></tr> </table> S2s2 http://wiki.dd-wrt.com/wiki/index.php?title=Talk:NoCatSplash&diff=20509&oldid=prev S2s2: Moved comments from Wiki article here. Place for discussions. 2008-05-16T19:24:50Z <p>Moved comments from Wiki article here. Place for discussions.</p> <p><b>New page</b></p><div>Comments brought from Wiki article:<br /> <br /> For instance, I found some of these comments from the article to be completely erroneous.<br /> Comment: ''Since this is a web portal capture only, no other traffic is blocked.''<br /> <br /> 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).<br /> <br /> The TCP port to bind the gateway service to. 5280 is de-facto standard for<br /> NoCatSplash.<br /> <br /> -Yes, this is true. It can be modified in the nocat.conf<br /> <br /> Just a couple things to keep in mind when using/testing this:<br /> <br /> 1. Since this is a web portal capture only, no other traffic is blocked.<br /> -wrong, see above.<br /> <br /> 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.<br /> -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.<br /> <br /> 3. If you attempt to access the &quot;status&quot; page, then you must have a status.html page there. Variables available are $GatewayName, $LocalTime, $GatewayStartTime, $TotalConnections, $Version, $GatewayMode, $LoginTimeout, $IdleTimeout, $HomePage,<br /> $AllowedWebHosts, $LastConnectionTime, $ConnectionCount, $UserTable<br /> <br /> - 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).</div> S2s2