sch-einesystem | Blog
| ||
|
|
|
|
|
|
 | |
| [0] |
20241209-0715-0-1.jpg |
 | |
| [1] |
20241209-0715-0-2.jpg |
 | |
| [2] |
20241209-0715-0-3.jpg |
 | |
| [3] |
20241209-0715-0-4.jpg |
 | |
| [4] |
20241209-0715-0-5.jpg |
 | |
| [5] |
20241209-0715-0-6.jpg |
 | |
| [6] |
20241209-0715-0-7.jpg |
 | |
| [7] |
20241209-0715-0-8.jpg |
 | |
| [8] |
20241209-0715-0-9.jpg |
| -------- Nachricht --------
Betreff: Re: [PEERINGDB-202412TQALS1] RE: Re: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS21158 and one or more IXPs Datum: Mon, 9 Dec 2024 07:12:20 +0100 Von: Maximilian Baehring <maximilian@baehring.at> An: chriztoffer <support@peeringdb.com> Kopie (CC): noc@moedove.com, ruben@ifog.ch, LOCIX NOC <noc@locix.online>, maximilian.baehring@zentral-bank.eu, maximilian.baehring@googlemail.com LocIX is a semiuprofessional IX at Frankfurt a.M. operated by formerclassmates of me, the only thing of interest they have there is graitous IPv6 traffic at AS6939, that was marketing- gag when the partly in germany serbian/ex-red-army-soldiers AS6939 tried to sell huge companies like Metllgetsallsf AG an hewlett packard theyr peering. i am one of the ibnvetors of IPv6 that orginally whas an april-fool an dindictes that german police/labour unions who tried to spy IPsec Tunnels did not knew the difference between IPSec and IPv6, the proof ist that there is no IPv5 but IPNG. Metallegesellscaft AG, a huge mining company with thosunds of elpyes and mer than 250 meinesaround the word more thena was coerced by okeo terois gangs to buy back hijackes routes for sreveral milliosn of dollars, now locix tries to do the same thing with my network. my mother was working at the "bundesvrand der Wachn und Schliessgesellchaften", like therer are labour unions of workrs thre need to be the opposite, the organisation of employers, and this is the union of the topmost big bank bosses. therfore the same car onteh same route that i was using to be driven to shcool was bomb balsted. https://www.bpb.de/kurz-knapp/hintergrund-aktuell/196955/vor-30-jahren-ermordung-von-alfred-herrhausen/ i was woking besides my work in the it indutry for a parliament as well as in theprsse, togehteh wich cistian metz of grmren zdf/3sat television. i was found out that RAF communist terroist had corrupt guay in the greman police her in frankfurta.M., the k15 in frankfurt adickesalle, the 1./5. the disctrct police satstion and the police in bad homburg where thebob balst tookplace. besides that pepole wher former classmates of my school. the baonm blast terrorist are inatrnationally organized left wing paramilitarys that also work together with labur-unionsiet and commusts in coutry like china. some of the communsit the spys were arested https://www.tagesschau.de/inland/festnahmen-spionage-china-100.html also some of the terroist https://www.tagesschau.de/inland/innenpolitik/anklage-klette-terror-raf-100.html . and all of this becouse of evidenece material taht i collectd (as i sais i wolred for r the press) and published in my blog whrefore they sevaraltimes trid to kill me. my child was kidnappend and laboru union and corrupt policmene try to get my ntwork offline. Thefore they made a new peering with AS44324 at locix whcihs trasited my traffic without any permission. lik theis ther gad also been spy acivity in the year 2003 by AS15844, a company that makes WLN/WIKI Liks to 38GHZ backbone in bad homburg whis is parr of the "edward snowden" hacks, snowden is a "lier" who tried to save his job by woking fopr the "russian red army" spying german companies. tey made massive ddos/virus/spam attacks by geratoing traffic and spopofing ips in mainzer landstraße infrankfirt a.M. her tey do not have to pay for itand mades us tarffic invices of thenthousands of dollars onthe lines taht connected bad homburg und frankfurt a.M.. the red army guys organize themselves togethr with the labour uiost of teh DATA CNERTE SECURTY,and teh data cneter securyt ist the Union woh is the psioe of the abritgebervabnd "undbsnvand der shc und schliessgesllschaften", the "employers' association" who dies wo much money hay gat if hey ar inthe lef winglabour unions. as you may know you have to be netral insuch thigs if yu ant to work inthe telco industyr but they aren't. they severaltimes tried to kill me and even poisonde me withmedicine after is was injuredby occuurpt policmen that i inavstgated aganst inhopsital with so i hav problems with thyping . like this they ried to coierce my compayn to hier ciorrut peronllem form them orgnsized in the ommusitc labour nion to infilatrate tha bak job eployers union. but what has all of this to do with LocIX?Welleher are also some of teh corrut guy wokimng inthe datanceter Ceriuyt at the Kleyerstraße/Rebsöckerstraße Data-Center who work for teh communitsts. They tried to hijack my outbound traffic and to be a illegal upstream. please sse the screenhot attached. it shows that "bgp.he.net" lists AS44324 as trasit for my network wat it is not accoding to ripe aut-num: https://apps.db.ripe.net/db-web-ui/lookup?source=ripe&key=AS21158&type=aut-num i kbow this guy called moedove he blengs to tthe peoples that kidnapped my child trying to tkae ove rmy copyn and then tottack the banks. i deteted this error in his route filters, he forwarded my traffic to AS6939 that i peer at another IXP (kleyrex) with. Therofre routes to AS6939 get AS two AS path prepends set at locIX by lrge BGP Community. if the route comes from me or from my uspetra AS34927 tahn this is always as path prependend toensure keyrex and not locix gets the AS6939 traffic. i had several inidents with the guys at "he.net" where we foud out that IPv6 peerings sohwer at locix/kylrex forwarded rotes that wer even blockedby deCIX route filters visible at theyr looking glass. the guys overthere are not very proffessional, kleyrex partly not even answers emails it is operted by Ghostnet, a Intrenet provider for BAd Homburg v.d.Höhe wherethe Hrrehausne Bob Blast Took Place by gystaht i Know very well, Lars Weber(?) for example. This guys treid to press me with my kindpped chidlto hand the over customers/ routes. the belog to the commust labour unionist gangs. wo hat i found in bgein of demceber taht as44324 moedove lls waslited as an upstram for me but i do not wtant to have them for polictal reasons, the belong to the cmmust labour union group polictally. i opened an ticket and told locix and as34829 that they are illagylly doing a trasit between my network and as6939, i was able to see that theyr and my ipv6 interface ip address at locix wher ised as next hop in the routes. THE NEXT HOP TYHEY ADVERTSED WAS LOCIX, 2001:7f8:33::a102:1158:1/64 NOT KLEYREX 2001:7f8:33::a102:1158:1 OR 2a0c:9a40:1::413 SO IT IS ABSOLIUTELY CLEAR THAT THE ROUTE CAME VIA LOCIX PEERING. Therore i deaactivated them explicityl by "strengthen" the "forbidness" https://manager.locix.online/public-content/routeserver ! I knowthat Moedove works togther with the red light district cybermafia. may mail ibo was bombed with gigabytes of spam and therefore i uses the googlemail/hotmail and yahoo spf filtering mechinsm and the mail locix send me that they TEMPORARILY suspeneded my peering there for 4 weeks. AND NOW TO YOUR QUESION, THS SEEMS TO AVE BEEN WHAT YOU HAVE SEEN! THEY "SUSPENDED" THE PEERING "FOR 4 WEEKES" AND BY THEYR ACCIDENT THIS GOT FILTERED IN THE JSON-IXP-EXPORT THAT YOU IMPORT AT PEERINGDB I ALOS HAVE SEEN THAT A FOMER USPTERM OF MINE HATS MADE A WRONG RADB ENTRY AND IN RUSSIA MAY AS-NUMBER APPEARS IN AS-SET-OBJECTS WHERE IT SHOULD NOT! ANYHOW! I AM REALLY UPSET AND FAVE DECIDED TO LEAVE LOCIX COMPLETELY! I HAVE MORE THAN ENOUGH OTHER PEERINGS TO BE PREPARDE FOR SUCH CASES! Please see the attachd email-docu! Maximilian Baehering (for contact details see http://as21158.net all my contact detail info in the RIPE-DB is also accurate, for my blog see https://zentral-bank.eu/tumblr.com/ mainly the sch-einesystem.###.pdf s or https://blog.sch-einesystem.de/ ) -------- Weitergeleitete Nachricht -------- Betreff: Re: Fwd: Fwd: you are ILLEGALLY announcing 2001:678:de0::/48 route from my AS21158 Datum: Sun, 8 Dec 2024 14:11:23 +0100 Von: Maximilian Baehring <maximilian.baehring@yahoo.com> An: LOCIX NOC <noc@locix.online>, Maximilian Baehring <maximilian@baehring.at>, noc@moedove.com, ruben@ifog.ch Hello S.Zeit.! Your messages got sorted to my spam inbox which is not monitored as frequently as my inbox. use mayor email-providrs like hotmail, yahoo and g(oogle)mail regdring spamfilters so yous hold fix this issue as it may affect other ixp members as welll, at least potentially, if they forward emails for example to a wbamer inbox on a smartphone. you say that on decmber 02nd, 2024 the route "2001:678:de0::/48" was installd via an as path "44324 34927 21158" . this is not correct/true, the rouet was installed via an as path "44234 21158" altough the commitys set did not allow such an as path and event the peeringdb entry was inicatiog that perring policy is "selective" !!! and not "open" to everyone!!! i have attached this on screenshots !!! when i logged into my lcix conected router i found ot that the all 3 sessions were down and i was not even able to use teh webiterface manager.locix.online website afterrestteing my pwssowrt i got a message that te login is not asociated with a member. for EVIDENCE DOCUMENTATION i even made screenshots of http://bgp.he.net hat show that AS44324 (wich formerly has been used by a orute motring tool at ripe, say some outadated utilitys with name to numer resolution cache that's a bit older than the curret in ripe-db), now "MOEDOVE LLC", was without otehr hops inbetweendriectly annocung my AS21158 via itself to AS6939 which i have my own peering with on another IXP. Therefpre you can see it on the "http://bgp.he.net" screenshot appearing as an new upstream/trasit, so that is thrdparty evidence that MOEDOVE is actinga s a atraist for aosutnoise-system that tey ar not allowed to. i was that upset that i foudn out you simply seem to have cancelled my subscription withoput an warnig or information taht i completely took locix perinsg down (there is only AS58299 ACCEPT AS-OPEFACTORY at the moment still at locix wihc ist if minor impartnae) and wrote the following to ripe-db: diff –ru1N / whois -h whois.ripe.net -T aut-num AS21158 | sed -e '/^%/'d | sed -ne '/^aut-num/,$ p' | sed -e '/^$/,$ d‘ @@ -166,2 +166,3 @@ remarks: +remarks: remarks: AS41051 - Freetransit - LocIX Accelerated Frankfurt/M @@ -170,7 +171,11 @@ remarks: -import: from AS41051 action pref=100; accept ANY -export: to AS41051 announce AS21158 +remarks: import: from AS41051 action pref=100; accept ANY +remarks: export: to AS41051 announce AS21158 remarks: -mp-import: afi ipv6 from AS41051 accept ANY -mp-export: afi ipv6 to AS41051 announce AS21158 +remarks: mp-import: afi ipv6 from AS41051 accept ANY +remarks: mp-export: afi ipv6 to AS41051 announce AS21158 +remarks: +remarks: ----------------------------------------------------- +remarks: peering closed cos of session down without prior info +remarks: ----------------------------------------------------- remarks: @@ -187,2 +192,8 @@ remarks: +remarks: ----------------------------------------------------- +remarks: the locix peering was temprorarily closed on 20241208 +remarks: ----------------------------------------------------- +remarks: rs-peering closed cos of unprofessional ixp-managment +remarks: detected rs-peer AS44324 unwanted IPv6 transit 202412 +remarks: ----------------------------------------------------- remarks: @@ -192,4 +203,4 @@ remarks: -mp-import: afi ipv6 from AS202409 action pref=100; accept AS-LOCIX -mp-export: afi ipv6 to AS202409 announce AS21158 +remarks: mp-import: afi ipv6 from AS202409 action pref=100; accept AS-LOCIX +remarks: mp-export: afi ipv6 to AS202409 announce AS21158 remarks: @@ -409,5 +420,6 @@ remarks: changed: maximilian@baehring.at 20240201 +remarks: changed: maximilian@baehring.at 20241208 I am really upset. Max Baehring (for contact details see http://as21158.net , looking glass webpage is http://lg.as21158.net in 2001:678:de0::/48 + 193.109.132./23) Am 03.12.2024 um 01:39 schrieb LOCIX NOC: > Good Evening Mr. Baehring, > Good Day others, > > thank you for bringing this to our attention. > > It was not very clear why you forwarded this email to us, or what the > problem was. In the future, please do not forward us email without any > context. > > After investigation, it seems like you are complaining about the fact > that Moedove is *installing *the route 2001:678:de0::/48 via Locix. > This is due to the fact that the route, despite tagging 202409:0:44324 > on direct session with Locix RS, can still by seen by your upstream > as34927, who also sends the route towards RS, without 202409:0:44324 tagged: > >> >> Route Deteils - |2001:678:de0::/48| as received from protocol >> |pb_0137_as34927| >> >> *Network* 2001:678:de0::/48 >> *Gateway* 2001:7f8:f2:e1:0:a120:4927:1 PRIMARY >> *From Protocol* pb_0137_as34927 >> *Age* 2024-11-13 09:57:16 >> *Metric* 100 >> *Type* BGP univ >> *BGP :: AS Path* 34927 21158 >> *BGP :: Local Pref* 100 >> *BGP :: Communities* 34927:122 >> *BGP :: Large Communities* 202409:1000:2 RPKI UNKNOWN >> 202409:1001:1 IRRDB VALID >> > Note that this is *NOT *a hijack of any kind. AS44324 is *NOT > *redistributing the prefix. > ... NO LONGER YOU DAMNED IDIOT! ... > > Best Regards, > Lennart Seitz > > Am 02.12.2024 um 22:50 schrieb Maximilian Baehring: >> >> >> >> -------- Weitergeleitete Nachricht -------- >> Betreff: Fwd: you are ILLEGALLY announcing 2001:678:de0::/48 route >> from my AS21158 >> Datum: Mon, 2 Dec 2024 22:43:20 +0100 >> Von: webmaster@zentral-bank.eu <webmaster@zentral-bank.eu> >> An: noc@moedove.com >> >> to ensure it's not coming from locix frankfurt i do not announce ipv6 >> an longer there (with exceptions that are as6939, as41051 and as58299). >> >>> show route export as202409at100v6 all >> 2001:678:de0::/48 unreachable [as21158v6 2024-11-13 from >> 2001:678:de0::8] * (100/-) [AS21158i] >> Type: BGP unicast univ >> BGP.origin: IGP >> BGP.as_path: 21158 >> BGP.next_hop: 2001:7f8:f2:e1:0:2:1158:1 >> BGP.local_pref: 100 >> BGP.large_community: (202409, 0, 0) (202409, 0, 112) (202409, 1, [...] Die zeiter Email fidnet sich schon im Blog, ich glab 03.Dezber 2024 11:00 Uhr locix schreibt hier > > Note that this is *NOT *a hijack of any kind. AS44324 is *NOT > *redistributing the prefix. > das ist unfug. sie habn ds prefix redstributed sonst wäre es auf der website bgp.he.net nicht plötzlich (das mußmehr tsund/tag o agagneg sien) als upsteram schtbar geworden. mit denen peere ich am KleyRSX, nicht LocIX. Daher wdren dern route as-path prepende im LocIX Import und auch per BGPlrgevommuniyt. An der interface adresse man sehen daß AS44324 Moedove das ans ich weitreleiten wollt per LOcIX, dann häte die rote aber dne as path prepedn aufwisen müssen der über die routeserver gesetzt wird eigehnd iw per bGP large dommuyt ausgehend. das beduet inenrhlab as6939 gwinnt imer dasklyerexdie rote election es sie denn kelyrex wäre kpletet olffline. für denflls würden mutmaßich erstmal meine andren peerings übernehmen und es zumshcluß aäbe wirgndwn den fllback ausflocix. eifch weild er as patch zwo prpends hat asugend wieiegehnd. da fumelt jemdn an routen rum (das sit prinzipiellerlaubt so lange mandmait im eigen as bereich bleibt), schneidet communitys heraus udnserter si idch iegen, das ist im prinzip auch erlaubt, allerdngs darf amn es dann nicht weitegeben. "set community ADDITIVE" (cisco IOS syntax) wi sgta das ist alel kien problem so lange das im eigeen netz passiert aber er leitet das illegakl (sons würd es im aripe-aut-num objetc erlaubts sein rpsektve bei den ix cummuniyt) weiter. udn dhslabtcht das sl as path ^(6939_)44324_21158$ plötzlich bei "he.net" AS6939 auf. Anders als Locix behaute REDISTRIBUTE der typ mein rozte "KLAUT TRAFFIC" asl häte er herfür mit mri ien agreement was es nicht gibt. die beochtung vom lic daß am 03. dezber 2024 ignwnn abnd da problem nicht mehr besteht ist richtg, das lieg aber nicht daran daß es nich ebstdn hat vorher sodnr daß ichasl sofotge nofallmaßnamen die bgp comunires restriklive getunt habe. mien peering policy ist "selctive"nich "open". nru wiel die"ufallstelle" izscen uafgeräumt udner vekehr umegeleietist beduet das nicht daßsie voher nich existert ha. bsi der loicx sich enlich ums ticket küermte das ich am vorabend hscibe muste ja wa geschehen. ich hab gar nichtmehr mirt igendner form von antwort gerchent so lah wie der locix als IXPregaerte. eifc h mal schuenwnnichdui rste medung abstetzte udnanndi anwort kam. ich habes extr üer menre email konten erledgt um auszuschließen daß es im spafilerhägen blibt auf deren seite swot ich das vonhier aus kotrollirenkann. soagr üer dittenetze ie yahoo damit nicht weg routinproblem bestimtmmailsevr möglicher- weisenicht erreichbar sind. daß bgp das gnaze als trasit fürhrt auf de rbgp.he.net seitz is der BEWIS einer ditten partei daß illagkl ttarfic an di educhgricht wurde. | |