firewall + tcpdump
Hi,
Does tcpdump dumps traffic on a network in front or behind a firewall? If it dumps traffic in front of a firewall, would anyone kindly suggest a way to test the firewall?
Thanks in advance,
Peggy
Quoted 3 lines · Peggy Kam
Hi,
Does tcpdump dumps traffic on a network in front or behind a firewall?
Not sure quite what you by "in front or behind", however I can tell you that tcpdump works "closer to the wire" than netfilter, so it will see all traffic hitting the interface, whether netfilter allows it or not.
Quoted 2 lines
If it dumps traffic in front of a firewall, would anyone kindly suggest a way to test the firewall?
Um, test it by sending packets which should be allowed, and making sure they are, then sending ones which should be blocked, and making sure they are?
Or have I misunderstood the question? How would you propose to use tcpdump
to test the firewall anyway?
Regards,
Antony.
Signature · 8 lines
You can spend the whole of your life trying to be popular,
but at the end of the day the size of the crowd at your funeral
will be largely dictated by the weather.
- Frank Skinner
Please reply to the list;
please don't CC me.As you have said that all traffic hitting the interface is seen whether netfilter allows it or not, my question was how do I know whether the packets being sent get blocked?
Quoted 20 lines
Not sure quite what you by "in front or behind", however I can tell you that tcpdump works "closer to the wire" than netfilter, so it will see all traffic hitting the interface, whether netfilter allows it or not.
Quoted 4 lines
If it dumps traffic in front of a firewall, would anyone kindly suggest a way to test the firewall?
Um, test it by sending packets which should be allowed, and making sure they are, then sending ones which should be blocked, and making sure they are?
Or have I misunderstood the question? How would you propose to use tcpdump to test the firewall anyway?
Regards,
Antony.
Peggy,
Enable logging within your rules , and then check the log files.
David
Peggy Kam
<[email protected]>
Sent by: To
netfilter-admin@l [email protected]
ists.netfilter.or cc
g
Subject
Re: firewall + tcpdump
03/30/04 10:16 AM
As you have said that all traffic hitting the interface is seen whether netfilter allows it or not, my question was how do I know whether the packets being sent get blocked?
Quoted 1 line
Not sure quite what you by "in front or behind", however I can tell you
that
Quoted 1 line
tcpdump works "closer to the wire" than netfilter, so it will see all
traffic
Quoted 10 lines
hitting the interface, whether netfilter allows it or not.
Quoted 4 lines
If it dumps traffic in front of a firewall, would anyone kindly suggest a way to test the firewall?
Um, test it by sending packets which should be allowed, and making sure
they
Quoted 3 lines
are, then sending ones which should be blocked, and making sure they are?
Or have I misunderstood the question? How would you propose to use
tcpdump
Quoted 9 lines
to test the firewall anyway?
Regards,
Antony.
Quoted 7 lines · Peggy Kam
Quoted 3 lines
Not sure quite what you by "in front or behind", however I can tell you that tcpdump works "closer to the wire" than netfilter, so it will see all traffic hitting the interface, whether netfilter allows it or not.
As you have said that all traffic hitting the interface is seen whether netfilter allows it or not, my question was how do I know whether the packets being sent get blocked?
1. If it's a routing firewall, see if the packets come out the other side (tcpdump on both interfaces).
2. If it's not a routing firewall, see if any response packets come back again (for TCP).
3. Put a LOG rule in your ruleset just before DROPping the packets, so you know what got DROPped.
4. If you're really interested in this sort of thing, you might want to investigate http://www.snort.org
Regards,
Antony.
Signature · 5 lines
Abandon hope, all ye who enter here.
You'll feel much better about things once you do.
Please reply to the list;
please don't CC me.