

The “edge” router is peering with the “core” through their loopbacks, and just advertising a default to it (or cores, on a future stage), and accepting the entire 198.51.100.0/24.


Set router-id=10.0.1.1Īdd interface=ether1 network-type=point-to-pointĪdd default-originate=always in-filter=core-01-in name=core-01 out-filter=core-01-out remote-address=10.1.1.1 remote-as=65000 update-source=lo0Īdd action=accept chain=core-01-in prefix=198.51.100.0/24Īdd action=accept chain=core-01-out prefix=0.0.0.0/0 All devices are MikroTik RouterOS 6.48.6 CHR instances. This lab network comprises 2 AGG/BNG routers, a single core router (which will perform additional aggregation), and a single edge router. Just plain BGP that can be implemented on most vendors, either via hardaware appliances or virtualized network devices.įor the following examples, I’ll simulate a public /24 prefix using the 198.51.100.0/24 which is reserved by IANA as TEST-NET-2 for documentation. The idea is to save IPv4 addresses, without other methods than standard routing protocols. On a previous post we saw an example of a network access topology running anycast default gateways.
