This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[connect-wg] Programmatic way to answer, "Who is sending me this stuff?"
- Previous message (by thread): [connect-wg] Programmatic way to answer, "Who is sending me this stuff?"
- Next message (by thread): [connect-wg] Programmatic way to answer, "Who is sending me this stuff?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
snash
snash at arbor.net
Wed Sep 9 12:19:44 CEST 2015
If I receive some traffic at an IXpeering router interface, I might want to know how I got it. If it is a stream of bad traffic I might want to ask my upstream peer to help turn it off. How do I find out who did send it to me? If I capture a sample packet I could see the source MAC address. Now I have to identify who owns the device with that MAC. Is there any guidance from the IX operators on how to do this? I'm sure phone calls to Ops teams are not cost effective or time efficient for anyone. A common programmatic method across IXes would suit my use-case admirably. I'd like to hear from anybody who either has a method in an IX, or who would like a method to exist. Regards Steve Steve Nash CEng MIET | Consultant Engineer EMEA Arbor Networks +44 7720 291359 (m) www.arbornetworks.com -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/connect-wg/attachments/20150909/3e233830/attachment.html>
- Previous message (by thread): [connect-wg] Programmatic way to answer, "Who is sending me this stuff?"
- Next message (by thread): [connect-wg] Programmatic way to answer, "Who is sending me this stuff?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]