kernel 2.2.16 - firewall information needed...

On Thu, 07 Aug 2003 23:45:57 -0700, Sampa Laiunen wrote:

> i would like to know from you how i can access the portmapping
> information and as a whole the port-information of the firewall.. i
> want to check on which port the firewall is attended and on which
> ports it sends.... i am totally new to this subject and i just want to
> know how i can access the information about the firewall...
> the firewall is allready running and it works but i need to
> reconfigure some details and it was not me who set it up... so if you
> could help me i would be very pleased.
>
> thanks in advance
> sampa
tried "iptables -L" lately?

i would like to know from you how i can access the portmapping
information and as a whole the port-information of the firewall.. i
want to check on which port the firewall is attended and on which
ports it sends.... i am totally new to this subject and i just want to
know how i can access the information about the firewall...
the firewall is allready running and it works but i need to
reconfigure some details and it was not me who set it up... so if you
could help me i would be very pleased.

thanks in advance
sampa

Or

iptables-save

Since iptables -L doesn't include interface info

--

"nunya" <business@127.0.0.1> wrote in message
newsan.2003.08.07.23.57.42.584573@127.0.0.1...
> On Thu, 07 Aug 2003 23:45:57 -0700, Sampa Laiunen wrote:
>
> > i would like to know from you how i can access the portmapping
> > information and as a whole the port-information of the firewall.. i
> > want to check on which port the firewall is attended and on which
> > ports it sends.... i am totally new to this subject and i just want to
> > know how i can access the information about the firewall...
> > the firewall is allready running and it works but i need to
> > reconfigure some details and it was not me who set it up... so if you
> > could help me i would be very pleased.
> >
> > thanks in advance
> > sampa
> tried "iptables -L" lately?

George Hewitt wrote:
> Or
>
> iptables-save
>
> Since iptables -L doesn't include interface info
>

I have no experience with 2.2 kernels, but I thought they had ipchains
instead of iptables.

Mark Atherton

Mark Atherton <(E-Mail Removed)> wrote in message news:<ctbd01-(E-Mail Removed)>...
> George Hewitt wrote:
> > Or
> >
> > iptables-save
> >
> > Since iptables -L doesn't include interface info
> >
>
> I have no experience with 2.2 kernels, but I thought they had ipchains
> instead of iptables.
>
> Mark Atherton


thats exactly the point... so i do not have iptables... but i think
with the help of the masquerading howto guide i found a good source to
look for solutions.
sampa

"Sampa Laiunen" <(E-Mail Removed)> wrote in message
news:<(E-Mail Removed) om>...
>
> thats exactly the point... so i do not have iptables... but i think
> with the help of the masquerading howto guide i found a good source to
> look for solutions.
> sampa

Sticking with the 2.2.* kernel is not really a good idea since the new
netfilter code present in the 2.4.* kernel is far superior to anything that
came before it, including ipchains. Netfilter uses stateful packet
filtering, otherwise known as connection tracking, which means the behaviour
of the firewall will change based on the information in the packet.

Essentially if you're at all interested/worried about security, then upgrade
to 2.4.* and netfilter.

If you want more info on netfilter see the official home of netfilter:
http://www.netfilter.org and Rusty's excellent HOWTO's at
http://www.netfilter.org/documentation/HOWTO/
The latest stable and development kernel can be obtained from
http://www.kernel.org/

-jps

---
-jamie <jps at silverdream dot org>
w: www.silverdream.org
* support free-speech: www.eff.org/br
Remove -NOSPAM from address before replying