How to melt a laptop:

5 dynamips cisco 7200s, 1 VIRL IOSvL2 (so, QEMU), 2 Debian QEMU instances, and 2 Debian Docker containers.

(Yes I know technically not every icon, namely the Open vSwitch controller and IXP router, aren't correct. They help me remember what does what)

If anyone is wondering: Heck with these labs teaching things like routing and BGP by just plugging routers together. I'm probably going to end up building a scale internet model (if I can) with all the layers and working parts and O̶̩̐̊h̴͉́̉ ̶͍͔͙͛́̓g̴͓͕̟̍o̸̩͆̌ͅd̶̡͇̰̍̃͌ ̶̳̈́̐͑h̵̨̯̃̑e̷̢͙̳̓̃̕l̴̨̳̃̓͂p̸͚̼̍̍ ̵̘͉̇̇m̴͙̟͙̽̓e̶͈͇̋́ ̵̢͔̏̌̀p̴̺̗̗̌ļ̶͍̿ĕ̵̪ȧ̴̡̯͍s̴̲̞̎e̵͕̦̽.

Currently, both AS30036 and AS13335 are BGP peers with the IXP acting as a transparent route server (so even though that's the gateway of last resort for both ASBRs, nobody cares about it for routing). AS30036 redistributes OSPF external type-2 routes to BGP (aka, consumer routes), and redistributes BGP routes to OSPF as type-1. Only has OSPF area 0 for now, thigh as I expand them they might go to IS-IS.

The PE router there is connected to "me" over _serial_ with PPP (for the heck of it) with unidirectional (CE to PE) CHAP auth.

PE router redistributes its connected routes into OSPF, meaning my assigned IP block is sent to the ASBR, who redistributes that into BGP.

Fun fact: the AS13335 router is the origination point of it's announced prefixes (for and with loopback interfaces. AS30036 doesn't announce anything "internal" (yet)

Sign in to participate in the conversation
Tek's Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!