Skip to main content

IPv6 Announcement for AS205828 via AS206873 on RouterOS

Introduction​

This document describes how to announce IPv6 subnets of autonomous system AS205828 through the main transit AS206873 using MikroTik RouterOS on the same border router 194.150.234.1.

AS205828 aggregates:

  • 2a0d:f847::/32
  • 2a09:a504::/32
  • 2a0c:9485::/32
  • 2a12:38c2::/32
  • 2a12:39c0::/32
  • 2a12:3042::/32

Requirements​

  • RouterOS (6.x or 7.x)
  • Access to BGP session with provider (AS206873)
  • Delegated IPv6 subnets AS205828
  • Enabled IPv6 stack

Step 1. IPv6 Address on Interface​

Add an IPv6 address from your pool to the required interface (example — /64 from 2a0d:f847::/32):

/ipv6 address add address=2a0d:f847:0:1::1/64 interface=ether1 advertise=yes

Can be skipped if not needed to work on the interface​

Step 2. BGP Instance Configuration​

On the same router, both AS are announced: transit 206873 (as default).

/routing bgp instance
set default as=206873 router-id=194.150.234.1
  • default — main AS (transit, 206873) with router-id 194.150.234.1

Step 3. Add Local Route to FIB Table​

/routing bgp network
add instance=AS205828 network=2a0d:f847::/32
add instance=AS205828 network=2a09:a504::/32
add instance=AS205828 network=2a0c:9485::/32
add instance=AS205828 network=2a12:38c2::/32
add instance=AS205828 network=2a12:39c0::/32
add instance=AS205828 network=2a12:3042::/32

This adds all AS205828 aggregates to the BGP network table for announcement.

Step 4. BGP Peer Configuration​

Configure BGP peer for AS205828:

/routing bgp peer
add name=AS205828 instance=AS205828 remote-address=194.150.234.1 remote-as=206873

Step 5. Route Filtering​

Set up route filters to control which routes are announced:

/routing filter
add chain=AS205828-out action=accept bgp-communities=9049:*
add chain=AS205828-out action=reject

Step 6. Verification​

Check BGP status and announced routes:

/routing bgp peer print
/routing bgp advertisements print

Troubleshooting​

Common Issues​

  1. Routes not announced: Check BGP peer status and network configuration
  2. Wrong communities: Verify community configuration in route filters
  3. IPv6 not working: Ensure IPv6 is enabled and addresses are configured

Debug Commands​

/routing bgp peer print detail
/routing bgp advertisements print detail
/ipv6 route print

Security Considerations​

  • Always use proper route filtering
  • Monitor BGP sessions regularly
  • Keep RouterOS updated
  • Use strong authentication for BGP sessions

Additional Resources​