North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: Alternative to NetFlow for Measuring Traffic flows
- From: Joe Abley
- Date: Mon Dec 16 22:40:54 2002
On Monday, Dec 16, 2002, at 22:28 Canada/Eastern, Richard A Steenbergen
If you are interested in traffic *to* a particular destination, surely
you could just tweak localpref on routes based on an as-path filter?
On Mon, Dec 16, 2002 at 09:16:55PM -0500, K. Scott Bethke wrote:
Also, that method has the same "knowing the routes" problem as netflow.
based on ALL the ASN's of the people on the peering switch.. but in
cases anyone pushing any real traffic will probably not have fine
samples enough to determine a peering relationship based on a single
with this method. Maybe Im wrong but hey if you are taking 200megs
one ASN I would hope you knew about it.
Whereever you are getting your list of ASN's route ASN.*"'s routes,
is pretty much no way they are accurate (for an ASN of ANY size).
You would have to statically route (or otherwise inject routes with a
specific nexthop) a list of their customer prefixes that would have to
If you are interested in traffic *from* a particular destination (you
have a network full of eyes, not content) then this approach is not