[PDB Tech] PeeringDB API Discrepency

[Chris Caputo]

Slightly related: It would be nice if in addition to the Peer Name column, 
the IPv4/IPv6 column and the Speed column could have natural sorts 
available.  (Natural sort by IPv4 addr, rather than IPv6 addr, unless IPv6 
is put into a separate column.)

Chris

On Tue, 4 Oct 2016, Matt Griswold wrote:
> Agreed, not sure how that got in, made 
> https://github.com/peeringdb/peeringdb/issues/71 and will check it out / 
> add better tests.
> 
> 
> On Oct 4, 2016 3:46 PM, "Arnold Nipper" <arnold.nipper at de-cix.net> wrote:
>       On 04.10.2016 22:29, Chris Caputo wrote:
>       > On Tue, 4 Oct 2016, Arnold Nipper wrote:
>       >> On 04.10.2016 18:53, James Bensley wrote:
>       >>> On 13 September 2016 at 11:00, Stefan Pratter <stefan at 20c.com> wrote:
>       >>>> Hi,
>       >>>>
>       >>>> Thank you for bringing this to our attention, i have opened a github ticket
>       >>>> for it here:
>       >>>>
>       >>>> https://github.com/peeringdb/peeringdb/issues/68
>       >>>>
>       >>>> Stefan
>       >>>
>       >>>
>       >>> Whilst playing the the PDB API some more I have found another "issue".
>       >>> It's not an issue with the API as such but perhaps a feature request;
>       >>> there seems to be no duplication detection.
>       >>>
>       >>> I was trying to automate some stuff at this IX: https://www.peeringdb.com/ix/745
>       >>>
>       >>> If you look there are two peers listed at that exchange with the same
>       >>> IPv4 address (AS 8468 and AS 60688, both with IP 195.66.246.11). This
>       >>> kind of thing should be easily detectable. Any scope for this sort of
>       >>> function to be added, where the AS number and company are different
>       >>> there shouldn't be a matching IP, the IP can only be announced by one
>       >>> AS number at an exchange.
>       >>
>       >> Woow ... how could this happen? Afaik it is not possible to add an IP
>       >> twice or even more often.
>       >>
>       >> Thanks for spotting. We will follow up with LINX to sort out the issue.
>       >
>       > It is possible.  We just had someone do this at the SIX in the past week.
>       > They added our route server addresses, which were registered already in
>       > PeeringDB.
>       >
> 
>       Definitely a severe bug imho and should be fixed immediately. I'm really
>       astonished that this pops up only now.
> 
> 
>       Arnold
>       --
>       Arnold Nipper
>       Chief Technology Evangelist and Co-Founder
> 
>       DE-CIX Management GmbH | Lindleystrasse 12 | 60314 Frankfurt am Main |
>       Germany | www.de-cix.net | Phone +49 69 1730902 22 |
>       Mobile +49 172 2650958 | Fax +49 69 4056 2716 |
>       arnold.nipper at de-cix.net | Geschaeftsfuehrer Harald A. Summa |
>       Registergericht AG Koeln HRB 51135
> 
> 
>       _______________________________________________
>       Pdb-tech mailing list
>       Pdb-tech at lists.peeringdb.com
>       http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
> 
> 
>