[144375] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Saudi Telecom sending route with invalid attributes

daemon@ATHENA.MIT.EDU (Kyle Duren)
Fri Sep 9 21:26:41 2011

In-Reply-To: <CAGWn6LTZa5Z3siNnWj3L4jP-SExwBP_Y+sK2fWvkL_Gvy6zAvQ@mail.gmail.com>
Date: Fri, 9 Sep 2011 18:26:03 -0700
From: Kyle Duren <pixitha.kyle@gmail.com>
To: Clay Haynes <chaynes@centracomm.net>
Cc: "Jonas Frey \(Probe Networks\)" <jf@probe-networks.de>, nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Is this announcement still showing up this way (no easy way to check
myself).

-Kyle

On Thu, Sep 8, 2011 at 4:20 PM, Clay Haynes <chaynes@centracomm.net> wrote:

> On Thu, Sep 8, 2011 at 7:11 PM, Jonas Frey (Probe Networks) <
> jf@probe-networks.de> wrote:
>
> > Hello,
> >
> > anyone else getting a route for 212.118.142.0/24 with invalid
> > attributes? Seems this is (again) causing problems with some (older)
> > routers/software.
> >
> >               Announcement bits (4): 0-KRT 3-KRT 5-Resolve tree 1
> > 6-Resolve tree 2
> >                AS path: 6453 39386 25019 I Unrecognized Attributes: 39
> > bytes
> >                AS path:  Attr flags e0 code 80: 00 00 fd 88 40 01 01 02
> > 40 02 04 02 01 5b a0 c0 11 04 02 01 fc da 80 04 04 00 00 00 01 40 05 04
> > 00 00 00 64
> >                Accepted Multipath
> >
> >
> > -Jonas
> >
> >
> Yup! We're seeing the same thing too, and we're filtering it out.
> Originating AS is 25019
>
> -Clay
>

home help back first fref pref prev next nref lref last post