Linux Netfilter discussions
 help / color / mirror / Atom feed
* sniffing the forwarded packets
@ 2003-03-10 21:05 Patrick Ahler
  2003-03-10 22:13 ` Aldo S. Lagana
  2003-03-10 22:49 ` Athan
  0 siblings, 2 replies; 3+ messages in thread
From: Patrick Ahler @ 2003-03-10 21:05 UTC (permalink / raw)
  To: netfilter EMAIL

What can I use to view the packets passing through my router/firewall? I've
tried tethereal but that only seems to be able to capture on the specific
devices (eth1 or eth2) not the packets being forwarded, can anyone help?



^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: sniffing the forwarded packets
  2003-03-10 21:05 sniffing the forwarded packets Patrick Ahler
@ 2003-03-10 22:13 ` Aldo S. Lagana
  2003-03-10 22:49 ` Athan
  1 sibling, 0 replies; 3+ messages in thread
From: Aldo S. Lagana @ 2003-03-10 22:13 UTC (permalink / raw)
  To: 'Patrick Ahler', 'netfilter EMAIL'

'sniffing' usually refers to listening on a specific interface - that's
why the tools you tried, do that.

I have found that by first declaring what I am looking for, I can
usually get a good idea of it by tcpdump, etc.  In other words - if I
want to know who from my LAN 192.168.0.* is going where, I look at the
internal interface and grep for port 80:
tcpdump -i eth0 port 80

If I need to know why an IPSec tunnel isn't coming up, I look at the
external interface and grep for those packets:
tcpdump -i eth2 port 500

I used to use ksnuffle to dump all the daily packets on the inside LAN
going to 80 to a file and then did some grepping through for a report of
internet usage; now I redirect port 80 to squid and use squid data files
for my reports

aldo

> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org 
> [mailto:netfilter-admin@lists.netfilter.org] On Behalf Of 
> Patrick Ahler
> Sent: Monday, March 10, 2003 4:05 PM
> To: netfilter EMAIL
> Subject: sniffing the forwarded packets
> 
> 
> What can I use to view the packets passing through my 
> router/firewall? I've tried tethereal but that only seems to 
> be able to capture on the specific devices (eth1 or eth2) not 
> the packets being forwarded, can anyone help?
> 
> 



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: sniffing the forwarded packets
  2003-03-10 21:05 sniffing the forwarded packets Patrick Ahler
  2003-03-10 22:13 ` Aldo S. Lagana
@ 2003-03-10 22:49 ` Athan
  1 sibling, 0 replies; 3+ messages in thread
From: Athan @ 2003-03-10 22:49 UTC (permalink / raw)
  To: Patrick Ahler; +Cc: netfilter EMAIL

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

On Mon, Mar 10, 2003 at 04:05:28PM -0500, Patrick Ahler wrote:
> What can I use to view the packets passing through my router/firewall? I've
> tried tethereal but that only seems to be able to capture on the specific
> devices (eth1 or eth2) not the packets being forwarded, can anyone help?

  Unfortunately that's just how it works.  Any packet sniffer attaches
to a device and only sees the packets that go through that specific
device.

  The best you can do is run multiple sniffers, one per interface.
*Possibly* you might be able to use tcpdump for this and then write
something to interleave the packets from the timestamps.

-Ath
-- 
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
                  Finger athan(at)fysh.org for PGP key
	   "And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-03-10 22:49 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-03-10 21:05 sniffing the forwarded packets Patrick Ahler
2003-03-10 22:13 ` Aldo S. Lagana
2003-03-10 22:49 ` Athan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox