Trouble Starting NoCat(2)

"Dave Kanter" <[email protected]>
Newsgroups gmane.network.nocat
Message-ID <[email protected]>
Ok, while waiting for a group response, I looked up my error and realized 
that NoCat actually was running and everything is AOK.  Nothing connecting 
via wireless is being blocked, though.  It must be a hardware problem.  Is 
it...what, something misconfigured on my router?  A communications problem 
between my router and the computer on which NoCat is running?

Here's the dump of  iptables -L:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  anywhere             anywhere
NoCat      all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain NoCat (1 references)
target     prot opt source               destination
NoCat_Ports  all  --  anywhere             anywhere
NoCat_Inbound  all  --  anywhere             anywhere
DROP       tcp  -- !nocat.net            anywhere            tcp dpt:5280
DROP       all  --  anywhere             anywhere

Chain NoCat_Inbound (1 references)
target     prot opt source               destination

Chain NoCat_Ports (1 references)
target     prot opt source               destination

Chain RH-Firewall-1-INPUT (2 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     icmp --  anywhere             anywhere            icmp any
ACCEPT     ipv6-crypt--  anywhere             anywhere
ACCEPT     ipv6-auth--  anywhere             anywhere
ACCEPT     udp  --  anywhere             224.0.0.251         udp dpt:5353
ACCEPT     udp  --  anywhere             anywhere            udp dpt:ipp
ACCEPT     all  --  anywhere             anywhere            state 
RELATED,ESTABLISHED
ACCEPT     tcp  --  anywhere             anywhere            state NEW tcp 
dpt:ssh
REJECT     all  --  anywhere             anywhere            reject-with 
icmp-host-prohibited

And here's the last few entries in nocat.log:
[2005-04-20 18:51:11] Peer  127.0.0.1  requests localhost:5280
[2005-04-20 18:51:11] Attempting to serve 
/usr/local/nocat/htdocs//favicon.ico
[2005-04-20 18:51:11] Unable to satisfy GET 
http://localhost:5280/favicon.ico
[2005-04-20 18:51:12] Spawning child process 9302.
[2005-04-20 18:51:12] Connection to 127.0.0.1 from 127.0.0.1
[2005-04-20 18:51:12] Peer  127.0.0.1  requests localhost:5280
[2005-04-20 18:51:12] Serving status page  127.0.0.1
[2005-04-20 18:51:12] Spawning child process 9303.
[2005-04-20 18:51:12] Connection to 127.0.0.1 from 127.0.0.1
[2005-04-20 18:51:12] Peer  127.0.0.1  requests localhost:5280
[2005-04-20 18:51:12] Attempting to serve 
/usr/local/nocat/htdocs//favicon.ico
[2005-04-20 18:51:12] Unable to satisfy GET 
http://localhost:5280/favicon.ico
[2005-04-20 18:51:13] Spawning child process 9304.
[2005-04-20 18:51:13] Connection to 127.0.0.1 from 127.0.0.1
[2005-04-20 18:51:13] Peer  127.0.0.1  requests localhost:5280
[2005-04-20 18:51:13] Serving status page  127.0.0.1
[2005-04-20 18:51:13] Spawning child process 9305.
[2005-04-20 18:51:14] Connection to 127.0.0.1 from 127.0.0.1
[2005-04-20 18:51:14] Peer  127.0.0.1  requests localhost:5280
[2005-04-20 18:51:14] Attempting to serve 
/usr/local/nocat/htdocs//favicon.ico
[2005-04-20 18:51:14] Unable to satisfy GET 
http://localhost:5280/favicon.ico

Thanks!

Dave.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.