[107771] in North American Network Operators' Group
RE: community real-time BGP hijack notification service
daemon@ATHENA.MIT.EDU (Skywing)
Fri Sep 12 20:41:36 2008
From: Skywing <Skywing@valhallalegends.com>
To: Gadi Evron <ge@linuxbox.org>, Andrew Fried <andrew.fried@gmail.com>
Date: Fri, 12 Sep 2008 19:41:14 -0500
In-Reply-To: <Pine.LNX.4.62.0809121449280.13078@linuxbox.org>
Cc: "nanog@merit.edu" <nanog@merit.edu>
Errors-To: nanog-bounces@nanog.org
Ah, both reasons really; setup mail flow rules, verify mail delivery, and c=
reate appropriate whitelist entries if need be to make sure that notificati=
ons tend not to mysteriously vanish. All general things that I like to do =
for any new mail-based monitoring system.
- S
-----Original Message-----
From: Gadi Evron [mailto:ge@linuxbox.org]
Sent: Friday, September 12, 2008 3:50 PM
To: Andrew Fried
Cc: Skywing; Kevin Oberman; nanog@merit.edu
Subject: Re: community real-time BGP hijack notification service
On Fri, 12 Sep 2008, Andrew Fried wrote:
> Mail being what it is today, testing message delivery is an excellent
> idea. I'll implement that feature this weekend.
I think he meant he wants to be able to get an example alert to his inbox
on registration/on request so he can special filters which can wake him
up.
Gadi.
> Andy
>
> Skywing wrote:
>> It might be useful to have an option to generate an example alert mail f=
or purposes of setting up necessary mail processing rules and that sort. J=
ust a thought.
>>
>> - S
>>
>> -----Original Message-----
>> From: Gadi Evron [mailto:ge@linuxbox.org]
>> Sent: Friday, September 12, 2008 3:13 PM
>> To: Kevin Oberman
>> Cc: nanog@merit.edu
>> Subject: Re: community real-time BGP hijack notification service
>>
>> On Fri, 12 Sep 2008, Kevin Oberman wrote:
>>
>>> Looks interesting, but it only takes a fairly short list of ASNs for a
>>> prefix. For our big CIDR blocks, we have WAY too many ASNs to enter the=
m
>>> all, so it's pretty useless for me. I need to be able to enter at very
>>> least a dozen ASes and I suspect may folks have a LOT more then that.
>>>
>>
>> I am sure we can fix that, Thanks for the comment!
>>
>>
>>> For now, I'll enter some shorter pieces from the block, but I'm most
>>> concerned with the pieces that are not currently assigned, so are
>>> available for hijack. I have added the larger, unassigned blocks. I'll
>>> start adding assigned bits and pieces as well as unassigned pieces, but
>>> being able to put all valid origin ASes in the list for the full blocks
>>> would be a lot nicer.
>>>
>>
>> Please let us know if you encounter any issues.
>>
>>
>>
>>> --
>>> R. Kevin Oberman, Network Engineer
>>> Energy Sciences Network (ESnet)
>>> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
>>> E-mail: oberman@es.net Phone: +1 510 486-8634
>>> Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
>>>
>>>
>>
>>
>>
>
