Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bielefeld: Incorrect ASN for announced networks #520

Closed
ecsv opened this issue Sep 9, 2017 · 2 comments
Closed

bielefeld: Incorrect ASN for announced networks #520

ecsv opened this issue Sep 9, 2017 · 2 comments

Comments

@ecsv
Copy link
Contributor

ecsv commented Sep 9, 2017

The networks are set in ICVPN to 65529. But instead 4242420022 is used for them this currently breaks ROA checks on other BGP peers. icvpn's mkroa uses the data from icvpn-meta to generate this table. The icvpn-meta information must therefore be in sync with ASN used for the announcements.

  • 10.26.48.0/20 ASN 4242420022
  • 10.26.64.0/18 ASN 4242420022
  • fdef:17a0:ffb1:ffff::/64 ASN 4242420022

Maybe this could be used as an example for find a workaround for other communities like

  • 10.31.0.0/24 ASN 4242421279
  • fda1:384a:74de::/48 ASN 4242423214
@mweinelt
Copy link
Member

mweinelt commented Sep 9, 2017

At least 10.31.0.0/24 is a colliding space that some dn42 user announces, not freifunk related at all. So ROA is right about blocking that.

This was referenced Sep 9, 2017
Closed
Merged
@ecsv
Copy link
Contributor Author

ecsv commented Sep 17, 2017

Seems that the bielefeld stuff was merged.

@ecsv ecsv closed this as completed Sep 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mweinelt @ecsv