Our AS is in a macro that we don't authorize.
Hi, we checked that our AS is present in the macro: AS24748:AS-THINX (they have thousands of AS in their macro) After contacting atman.pl who is responsible for this macro, they tell me:
It appears that AS59432 is contained in one of our customers AS-SETs and it is automatically added to our AS-SET AS24748:AS-THINX
As soon as they remove AS59432, it will disappear from AS24748:AS-THINX
We have asked him how we can find out who that customer is. But their answer doesn't give us any information.
Please be kindly informed that our macros are being built automatically according to our customers` macros. If your AS happens to be removed from whichever of our customer`s macros, ours is to be changed accordingly.
We are concerned about this situation and do not know how to proceed. Thank you for your help! -- José Manuel Giner http://ginernet.com
Why you want remove your AS from IX routing list? You want that your prefixes does not get routed to some part of internet? Correct if I am wrong but for me that looks more like that at least someone (atman) do filtering even for tier1 operators and at least in theory it should be good thing. On 30.10.2018 16:27, José Manuel Giner wrote:
Hi, we checked that our AS is present in the macro: AS24748:AS-THINX (they have thousands of AS in their macro)
After contacting atman.pl who is responsible for this macro, they tell me:
It appears that AS59432 is contained in one of our customers AS-SETs and it is automatically added to our AS-SET AS24748:AS-THINX
As soon as they remove AS59432, it will disappear from AS24748:AS-THINX
We have asked him how we can find out who that customer is. But their answer doesn't give us any information.
Please be kindly informed that our macros are being built automatically according to our customers` macros. If your AS happens to be removed from whichever of our customer`s macros, ours is to be changed accordingly.
We are concerned about this situation and do not know how to proceed.
Thank you for your help!
-- F-Solutions Oy Tapio Haapala PL7, 90571 Oulu GSM +358400998371 Skype burner- IRC Burner@ircnet
I want my traffic routed where I want it. I'm not a member of that IX and if you're routing traffic through this IX, it's being a latency problem (my servers are a far away from that IX, +60 ms) and possibly a hijaking security problem. On 01/11/2018 10:13, Tapio Haapala wrote:
Why you want remove your AS from IX routing list? You want that your prefixes does not get routed to some part of internet? Correct if I am wrong but for me that looks more like that at least someone (atman) do filtering even for tier1 operators and at least in theory it should be good thing.
On 30.10.2018 16:27, José Manuel Giner wrote:
Hi, we checked that our AS is present in the macro: AS24748:AS-THINX (they have thousands of AS in their macro)
After contacting atman.pl who is responsible for this macro, they tell me:
It appears that AS59432 is contained in one of our customers AS-SETs and it is automatically added to our AS-SET AS24748:AS-THINX
As soon as they remove AS59432, it will disappear from AS24748:AS-THINX
We have asked him how we can find out who that customer is. But their answer doesn't give us any information.
Please be kindly informed that our macros are being built automatically according to our customers` macros. If your AS happens to be removed from whichever of our customer`s macros, ours is to be changed accordingly.
We are concerned about this situation and do not know how to proceed.
Thank you for your help!
-- José Manuel Giner http://ginernet.com
Hi, I do understand your concerns, but: also your AS number shows up in someone elses AS-SET is does not mean any traffic being routed anywhere. This is mainly a documentational and a possible security issue (also no harm seems to be done by now). AS24748 seem to have 106 Peers - far away from the "thousands". The macro: AS24748:AS-THINX contains about every single active AS-Number i know of (at least the first 10 of 15 that came into my mind were in there). So there guy's built a fancy and completely useless macro - maybe they shouldn't consider their upstream to be their customers. Anyhow - forget about them or try to make them clean up their mess - but I don't think this mailinglist might be able to help you any further. Kind regards Karl ________________________________________ Von: members-discuss [members-discuss-bounces@ripe.net]" im Auftrag von "José Manuel Giner [jm@ginernet.com] Gesendet: Freitag, 02. November 2018 10:27 An: members-discuss@ripe.net Betreff: Re: [members-discuss] Our AS is in a macro that we don't authorize. I want my traffic routed where I want it. I'm not a member of that IX and if you're routing traffic through this IX, it's being a latency problem (my servers are a far away from that IX, +60 ms) and possibly a hijaking security problem. On 01/11/2018 10:13, Tapio Haapala wrote:
Why you want remove your AS from IX routing list? You want that your prefixes does not get routed to some part of internet? Correct if I am wrong but for me that looks more like that at least someone (atman) do filtering even for tier1 operators and at least in theory it should be good thing.
On 30.10.2018 16:27, José Manuel Giner wrote:
Hi, we checked that our AS is present in the macro: AS24748:AS-THINX (they have thousands of AS in their macro)
After contacting atman.pl who is responsible for this macro, they tell me:
It appears that AS59432 is contained in one of our customers AS-SETs and it is automatically added to our AS-SET AS24748:AS-THINX
As soon as they remove AS59432, it will disappear from AS24748:AS-THINX
We have asked him how we can find out who that customer is. But their answer doesn't give us any information.
Please be kindly informed that our macros are being built automatically according to our customers` macros. If your AS happens to be removed from whichever of our customer`s macros, ours is to be changed accordingly.
We are concerned about this situation and do not know how to proceed.
Thank you for your help!
-- José Manuel Giner http://ginernet.com _______________________________________________ members-discuss mailing list members-discuss@ripe.net https://lists.ripe.net/mailman/listinfo/members-discuss Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/karl.kaiser%40upc.at Information gemäß § 14 Unternehmensgesetzbuch: T-Mobile Austria GmbH, Firmensitz: Wien, Geschäftsanschrift Rennweg 97-99, 1030 Wien, Firmenbuchnummer: FN 171112 k, Handelsgericht Wien.
On 30.10.2018 15:27, José Manuel Giner wrote:
Hi, we checked that our AS is present in the macro: AS24748:AS-THINX (they have thousands of AS in their macro)
After contacting atman.pl who is responsible for this macro, they tell me:
It appears that AS59432 is contained in one of our customers AS-SETs and it is automatically added to our AS-SET AS24748:AS-THINX
As soon as they remove AS59432, it will disappear from AS24748:AS-THINX
We have asked him how we can find out who that customer is. But their answer doesn't give us any information.
Maybe http://irrexplorer.nlnog.net/search/59432 does help to find the AS-SET. Good luck 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@de-cix.net | Geschaeftsfuehrer Harald A. Summa | Registergericht AG Koeln HRB 51135
Le 30-10-18 à 15:27, José Manuel Giner a écrit :
Hi, we checked that our AS is present in the macro: AS24748:AS-THINX (they have thousands of AS in their macro)
After contacting atman.pl who is responsible for this macro, they tell me:
It appears that AS59432 is contained in one of our customers AS-SETs and it is automatically added to our AS-SET AS24748:AS-THINX
As soon as they remove AS59432, it will disappear from AS24748:AS-THINX
We have asked him how we can find out who that customer is. But their answer doesn't give us any information.
Please be kindly informed that our macros are being built automatically according to our customers` macros. If your AS happens to be removed from whichever of our customer`s macros, ours is to be changed accordingly.
We are concerned about this situation and do not know how to proceed.
Thank you for your help!
Hello, If someone put you in theyr as-macro, it's maybe because they give you transit. Maybe the first search step is search all your transit as who are in this list and check theyr as-macro (get them over peering-db) Just an idea, but maybe it can help Cedric Rossius
* José Manuel Giner
Hi, we checked that our AS is present in the macro: AS24748:AS-THINX (they have thousands of AS in their macro)
We are concerned about this situation and do not know how to proceed.
To the best of my knowledge, there exists no mechanism in the database that lets ASN holders to authorise or deny the inclusion of their ASN in someone else's AS-set. For example, nobody can stop me from creating AS-set «AS-ALL-ODD-ASNS» containing AS1,AS3,AS5, et cetera. And nobody can stop me from instructing my peers and upstreams to use that AS-set to build their route filters facing my AS. This facilitates hijacks by malicious actors, of course. RPKI won't help as the origin AS is easily spoofed. You are of course free to attempt to chase down the maintainers of the offending AS-sets and convince them to remove your ASN, but over time it likely becomes an exercise in futility. C'est la vie... Tore
My vote for this option. On 01/11/2018 18:28, Dominic Schallert wrote:
3) Authorization for referencing ASN’s/AS-SET's in macros (probably not a good idea)
-- José Manuel Giner http://ginernet.com
participants (6)
-
Arnold Nipper -
Cedric R -
José Manuel Giner -
Kaiser, Karl -
Tapio Haapala -
Tore Anderson