selective connection tracking?
Hi,
I am from the FreeBSD/ipfilter world. I recently switched to Linux and netfilter. One question I have with netfilter connection tracking is whether there I can instruct the connection tracking to selectively tracking connections.
Looks to me once I loaded the conn_track modules, everything was tracked. Is there a way I can specify, for example, that I only want http to be tracked? All other traffic will be dropped anyway, tracked or not.
Regards,
Ming
i think , thereis a raw target on POM and something as NOTRACK in order to ignore conntracking for those connections...
Try it
Quoted 13 lines · El Miércoles, 12 de Mayo de 2004 19:42, [email protected] escribió:
Hi,
I am from the FreeBSD/ipfilter world. I recently switched to Linux and netfilter. One question I have with netfilter connection tracking is whether there I can instruct the connection tracking to selectively tracking connections.
Looks to me once I loaded the
conn_trackmodules, everything was tracked. Is there a way I can specify, for example, that I only want http to be tracked? All other traffic will be dropped anyway, tracked or not.Regards,
Ming
Quoted 2 lines · clister
i think , thereis a raw target on POM and something as NOTRACK in order to ignore conntracking for those connections...
Oh dear :( Maybe I am getting out of date :)
Regards,
Antony.
Signature · 4 lines
This email was created using 100% recycled electrons.
Please reply to the list;
please don't CC me.Quoted 4 lines · On Wednesday 12 May 2004 6:42 pm, [email protected] wrote:
Hi,
I am from the FreeBSD/ipfilter world. I recently switched to Linux and
netfilter.
Welcome to our world :)
Quoted 2 lines
One question I have with netfilter connection tracking is whether there I can instruct the connection tracking to selectively tracking connections.
No.
Quoted 1 line
Looks to me once I loaded the
conn_trackmodules, everything was tracked.
Correct.
Quoted 2 lines
Is there a way I can specify, for example, that I only want http to be tracked? All other traffic will be dropped anyway, tracked or not.
If it's going to be dropped, there won't be a connection, therefore the other traffic won't consume any connection tracking resources.
Regards,
Antony.
Signature · 7 lines
How I want a drink, alcoholic of course, after the heavy chapters involving
quantum mechanics.
- 3.14159265358979
Please reply to the list;
please don't CC me.Quoting Antony Stone <[email protected]>:
Quoted 7 lines
Quoted 3 lines
Looks to me once I loaded the
conn_trackmodules, everything wastracked.
Correct.
Quoted 7 lines
Quoted 1 line
Is there a way I can specify, for example, that I only want http to
be
Quoted 1 line
tracked? All other traffic will be dropped anyway, tracked or not.
If it's going to be dropped, there won't be a connection, therefore the other
traffic won't consume any connection tracking resources.
I believe the connection tracking is useful for the FORWARD filter, however, for the INPUT filter, its the job of Linux TCP/UDP to take care of those things. Keep another set of stat below the IP layer does not make sense to me. The upper layer protocol has a better knowledge of the connection state than the conn_track anyway.
Quoted 18 lines
Regards,
Antony.
Signature · 10 lines
How I want a drink, alcoholic of course, after the heavy chapters involving quantum mechanics. - 3.14159265358979 Please reply to the list; please don't CC me.
Hello Ming,
I thought you could do connection tracking per port for example if you where
forwarding / allowing out http and ssh but then wanted to block SSH.
At first you would have:
iptables -A forward -i eth1 -o eth0 -s internalnetwork -p tcp --dport 80 -match state --state ESTABLISHED,NEW -j ACCEPT
iptables -A forward -i eth1 -o eth0 -s internalnetwork -p tcp --dport 22 -match state --state ESTABLISHED,NEW -j ACCEPT
Would allow port 80 and port 22 new or established connections, then if you removed the rule for port 22 and had a default policy of deny then SSH connections should be dropped.
Michael.
Quoted 18 lines · On Wed, 12 May 2004 13:42:03 -0400 (EDT) [email protected] wrote:
Hi,
I am from the FreeBSD/ipfilter world. I recently switched to Linux and netfilter. One question I have with netfilter connection tracking is whether there I can instruct the connection tracking to selectively tracking connections.
Looks to me once I loaded the
conn_trackmodules, everything was tracked. Is there a way I can specify, for example, that I only want http to be tracked? All other traffic will be dropped anyway, tracked or not.Regards,
Ming
Signature · 3 lines
Michael Gale Network Administrator Utilitran Corporation
Sorry I misunderstood the question.
Michael.
Quoted 54 lines · On Thu, 13 May 2004 10:28:29 -0600 Michael Gale <[email protected]>…
Hello Ming,
I thought you could do connection tracking per port for example if you where
forwarding / allowing out http and ssh but then wanted to block SSH.At first you would have:
iptables -A forward -i eth1 -o eth0 -s internalnetwork -p tcp --dport 80 -match state --state ESTABLISHED,NEW -j ACCEPT
iptables -A forward -i eth1 -o eth0 -s internalnetwork -p tcp --dport 22 -match state --state ESTABLISHED,NEW -j ACCEPT
Would allow port 80 and port 22 new or established connections, then if you removed the rule for port 22 and had a default policy of deny then SSH connections should be dropped.
Michael.
Quoted 18 lines · On Wed, 12 May 2004 13:42:03 -0400 (EDT) [email protected] wrote:
Hi,
I am from the FreeBSD/ipfilter world. I recently switched to Linux and netfilter. One question I have with netfilter connection tracking is whether there I can instruct the connection tracking to selectively tracking connections.
Looks to me once I loaded the
conn_trackmodules, everything was tracked. Is there a way I can specify, for example, that I only want http to be tracked? All other traffic will be dropped anyway, tracked or not.Regards,
MingSignature · 3 lines
Michael Gale Network Administrator Utilitran Corporation
Signature · 3 lines
Michael Gale Network Administrator Utilitran Corporation