Write code or pay somebody else to do it...

ntop is basically a TCP/IP analyzer, with limited understanding of the
Ethernet frames and of other Ethernet protocols (e.g. ICMP).  Also some
limited understanding of other transport protocols like Token Ring, FDDI,
etc.  (yes, I know there are differences between wireline level and
transport, but - like practical implementations of the OSI model - ntop
crosses some lines in the interest of sanity.

See ntop.h around 2270ff for some of the stuff we have (minimal)
understanding of.

Basically, if libpcap can grab it from an interface, ntop can see it.  The
function we use is

pcap_open_live() is used to obtain a packet capture descriptor to look at
packets on the network. device is a string that specifies the network device
to open. snaplen specifies the maximum number of bytes to capture. promisc
specifies if the interface is to be put into promiscuous mode. (Note that
even if this parameter is false, the interface could well be in promiscuous
mode for some other reason.) to_ms specifies the read timeout in
milliseconds. ebuf is used to return error text and is only set when
pcap_open_live() fails and returns NULL.

So, if tcpdump et al can see it, we probably can.

Off the cuff...

You would need access to the stream of ATM cells. (that's the issue of
whether the Fore unit can give you access to them, even if they're not
addressed to you - i.e. can atm act like a hub vs. a switch)?

You would need to write code in ntop to handle the lower level (ATM) frames.

You would need to maintain some sort of table mapping the ATM addresses to
the pvcs.

etc.

-----Burton


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Rippe, Mark (CCI-Warwick)
Sent: Thursday, August 01, 2002 11:56 AM
To: [EMAIL PROTECTED]
Subject: [Ntop-dev] monitoring pvc's on a fore tnx-1100


i am trying to monitor pvc's traffic on a fore tnx-11 atm device.
help?

[EMAIL PROTECTED]

"Don't pay no attention to 'im.
He's dumber 'n a bag full 'o hammers"

Everett McGill


_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://lists.ntop.org/mailman/listinfo/ntop-dev

_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://lists.ntop.org/mailman/listinfo/ntop-dev

Reply via email to