DN42 Registry
Find a file
Simon Marsh dfc48288e9
- Update as-set with latest peerings
- Too many nodes, not enough IPs:
   - Assign 172.20.129.0/27, to be used for burble.dn42 services
   - Add route object for 172.20.129.0/27
   - Update existing IPv4 inetnum & route descriptions
2019-04-12 12:31:49 +01:00
data - Update as-set with latest peerings 2019-04-12 12:31:49 +01:00
utils/schema-check
.gitignore
check-my-stuff Revert "initial commit" 2018-11-17 23:13:09 +01:00
check-pol
check-remote
fmt-my-stuff
install-commit-hook
README.md Update README with tip to avoid RFC4193 section 3.2. violation 2019-01-01 03:17:38 +00:00

Tips for a successful Pull Request

  1. Bonus: Randomly generate IPv6 prefix for new allocations to avoid RFC4193 section 3.2. violation (script)
  2. Squash your commits -- Keep the changes simple to read.
  3. Run the schema check -- Make sure the changes are valid! Run ./check-my-stuff YOUROWN-MNT
  4. BONUS: install the commit hook! Run ./install-commit-hook YOUROWN-MNT
  5. Sign your commit -- Makes it easier to verify.
  6. Bonus: add your pgp fingerprint to your MNT auth: pgp-fingerprint <pgp-fingerprint> [See XUU-MNT example]
  7. ???
  8. Profit!