Somewhere in the path should be standard 802.2 or what's the vlan encap, 802.1q? Or maybe try netflow or sflow?
To your original question I don't think ntop supports native MPLS labels/tagging/encap/ whatever. ________________________________ From: [email protected] To: [email protected] Sent: Wed May 06 06:11:40 2009 Subject: Re: [Ntop] MPLS Thanks for the reply. This is Ethernet. This is our most convenient choke point to run ntop but it's an MPLS link between our data center and our ISP. ------------------------------ Message: 2 Date: Tue, 5 May 2009 13:35:12 -0500 From: "Gary Gatten" <[email protected]> Subject: Re: [Ntop] MPLS To: <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Can't you capture on the Ethernet side? ______________________________ __ From: [email protected] [mailto:[email protected]] On Behalf Of inetjunkmail Sent: Tuesday, May 05, 2009 1:15 PM To: [email protected] Subject: [Ntop] MPLS We're running ntop on an MPLS link. It doesn't seem to work. Are there plans for MPLS support? Any ideas on how we could pop the MPLS headers before sending to ntop for processing? We do not have overlapping IPv4 addresses within the MPLS traffic so everything should be good if we can just get the MPLS header off. <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font>
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
