-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rhein-neckar: unknown ASN announces networks for rhein-neckar networks #519
Comments
@nazco, @Nurtic-Vibe Btw. looks like it also fails having a direct connection:
So it is using an "incorrect" ASN (which is not in the icvpn-meta) file all the time. Here is the complete OPEN message from rhein-necker IPv6:
|
We are currently rebuilding our ICVPN setup, so there shouldn't be an announcement of our prefixes from our old peering point. But I see that the VPN connections and some peerings with the old ASN are still up. For the moment I will shut down the VPN to mitigate the wrong ASN problem. |
Will close this now. It wasn't a failure in the icvpn-meta data but a misconfiguration on the rhein-neckar server - which was disabled to work around the problem. |
This is most likely an old server still announcing this stuff with the wrong ASN. At least this one was used before 3a4a9b2 ("Update rhein-neckar (#475)")
This currently breaks the ROA checks on other BGP peers because icvpn's mkroa generates them from icvpn-meta
@nazco, @Nurtic-Vibe
The text was updated successfully, but these errors were encountered: