Skip to main content

IPv6 Announcement for AS205866 via AS206873 on RouterOS

Introduction​

This document describes how to announce IPv6 subnets belonging to autonomous system AS205866 through the main transit AS206873 using MikroTik RouterOS routers.

Requirements​

  • Working router on RouterOS (versions 6.x or 7.x)
  • Access to BGP session with provider (AS206873)
  • IPv6 subnets delegated to your AS205866
  • Configured IPv6 stack

Step 1. IPv6 Address Configuration​

  1. Go to IPv6 > Addresses menu and add addresses from your IPv6 subnet to the required interface:
/ipv6 address add address=2a09:a502:0:1::1/64 interface=ether1 advertise=yes

Step 2. BGP Configuration for IPv6​

  1. Go to Routing > BGP (or via CLI):
  2. Configure BGP instances if both AS (main and client) are announced on the same router (e.g., 194.150.234.1):
/routing bgp instance
set default as=206873 router-id=194.150.234.1
add name=AS205866 as=205866 router-id=194.150.234.1

Step 3. BGP Network Configuration​

Add your IPv6 networks to BGP:

/routing bgp network
add instance=AS205866 network=2a09:a502::/32
add instance=AS205866 network=2a09:a503::/32

Step 4. BGP Peer Configuration​

Configure BGP peer for AS205866:

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

Step 5. Route Filtering​

Set up route filters to control announcement:

/routing filter
add chain=AS205866-out action=accept bgp-communities=9049:*
add chain=AS205866-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