Post subject: ipw3945 cannot communicate.
PostPosted: Sun Nov 25, 2007 12:50 pm 
   
message unavailable


 
 Post subject: Re: ipw3945 cannot communicate.
PostPosted: Sun Nov 25, 2007 12:50 pm 
On Wed, 21 Nov 2007 22:50:50 -0500, Unruh wrote:

Quote:
As far as I know iptables is shut down ( no iptables running according to
ps) so it cannot(?) be the firewall. What in the world could it be? It is
hard to believe it is hardware since dns and dhcp work.
But I need suggestions as to what it could be.

iptables is a kernel module, not a separate process.

Either dig in "man iptables, or install shorewall, and then use
"shorewall clear" to allow all access. I suspect what you currently have,
is the equivalent of "shorewall stop", which blocks all traffic.

Note that shorewall, is just one front-end, for configuring iptables. There
are several available, like guarddog. They are just used for creating and
loading the iptables rules. They don't actually run a process, to act as
a firewall, like in windows.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)


 
 Post subject: Re: ipw3945 cannot communicate.
PostPosted: Tue Nov 27, 2007 3:54 pm 
"David W. Hodgins" writes:

Quote:
On Wed, 21 Nov 2007 22:50:50 -0500, Unruh wrote:

As far as I know iptables is shut down ( no iptables running according to
ps) so it cannot(?) be the firewall. What in the world could it be? It is
hard to believe it is hardware since dns and dhcp work.
But I need suggestions as to what it could be.

iptables is a kernel module, not a separate process.

Either dig in "man iptables, or install shorewall, and then use
"shorewall clear" to allow all access. I suspect what you currently have,
is the equivalent of "shorewall stop", which blocks all traffic.

Note that shorewall, is just one front-end, for configuring iptables. There
are several available, like guarddog. They are just used for creating and
loading the iptables rules. They don't actually run a process, to act as
a firewall, like in windows.

Thanks Will try. However, I ran
service iptables stop
and it stated that
"Resetting built-in chains to the default ACCEPT policy:"
Also, eth0, a wired connection, works fine, which sort of suggests it is
not iptables ( although it might still be)


 





SitemapIndex SitemapIndex RSS Feed RSS Feed Channel list Channel list
  0x61.com 2009-2010 - Internet Forums and much more!