routing ospf instance set 0 router-id=172.16.1.2 routing ospf area add name=area13 area-id=0.0.0.13 If you see timeouts, check your connection and switch configuration. Now, assuming ether1 is connected to the EdgeSwitch’s 0/1 (access on VLAN 10) and link activity is good…you should be able to ping the VyOS router using /ping 172.16.10.1. ip address add address=172.16.1.2 interface=lo Start with the hostname, creating a bridge for the loopback interface and adding IP addresses. ![]() In the case of a no-defaults configuration, the only way to get at a Mikrotik device is either through a console cable, a Mikrotik protocol called mac-telnet (it’s telnet but uses mac addresses instead of IP addresses) or through Mikrotik’s GUI client called Winbox using the mac address of the device. These configurations are assuming a no-defaults reset has been performed. Configure RouterOS RB450GX4-1įor those who have never used RouterOS before, it may see a little strange. VyOS is not configured for basic OSPF function in a ROS setup. Set protocols ospf area 0.0.0.13 network 172.16.20.0/30įinally set the system hostname and activate the config and save the running config to the startup config. Now configure OSPF (remember, I have a network for Area 9 as well but it is not necessary for this lab). Now assign IP addresses to the interfaces (remember, I have eth0 as an OOB management interface, it is not needed for this lab). Set interfaces bond bond0 description "Port 3 & 3 LACP" ![]() Set interfaces bond bond0 hash-policy layer3-4 Login into the VyOS machine (serial console, local console or IP based if you have it available) and enter configuration mode using the configure command. ![]() Router ID: 172.16.1.1 RB450Gx4-1 Setup Hostname: mt.vlan10Īssuming a fairly default configuration (remember I have some extra stuff running on mine which is not needed for the lab and I will not be going over). Technically speaking, the Fitlet2 is configured as a Router On a Stick (ROS) meaning traffic goes in and out on the same interface (the LAG in this case). Each Mikrotik will simply be routers in the OSPF area with a client interface set on ether2 for performing throughput testing (this will come later). The Fitlet2 will also have Port 1 occupied with my home network just to get some more OSPF routes, remote access from my desktop via SSH and SNMP function. 0/1 will be an access port on VLAN 10 and 0/2 an access port on VLAN 20. The Fitlet2 will have an 802.3ad dual interface bond on Port 3 and Port 4 interfacing with the EdgeSwitch’s 0/7 and 0/8 interfaces (becomes 3/1 when the LAG is created) and pass tagged traffic on VLAN 10 and VLAN 20. To start with, the basic configuration overview looks like the following: The switch used here will be a Ubiquiti EdgeSwitch 8 running 1.8.5-Lite firmware with two ports setup in a 802.3ad LAG and an access port for each VLAN that will be assigned. Really any managed switch will work but this lab is really to load up the CPU of the Fitlet2 to get a better estimation of what it is actually capable of. Since VLANs will be used in this walkthrough, a managed switch will be used to provide access ports for the Mikrotik routers. Fitlet2 with rOtring 600 for scale Managed Switch ![]() The Fitlet 2 in question is the model with the E3950 quad core CPU with 8 GB memory (way overkill for this application but it’s been collecting dust for awhile now so I figured I’d pull it out). In this case, it will be a Compulab Fitlet2 with the dual NIC FACET-card for a total of 4 Gigabit Ethernet interfaces. RB450Gx4 with rOtring 600 for scale x86_64 PC or Server One will be named mt.vlan10 and the other mt.vlan20 and we will get into what the hostnames mean later on. In this case, it will be two Mikrotik RB450Gx4 RouterBoards running a current long term release of RouterOS (6.47.10). HardwareĪs this will be a physical lab, it will require some physical hardware to accomplish. This post is going to walk through the configuration of OSPF on VyOS, how it compares to Mikrotik’s RouterOS and how to get the two routing solutions working together. This is great as it can provide some additional flexibility that just isn’t present in the hardware provided by many vendors (such as upgradability, ability to easily virtualize, etc.). In a previous post we walked through Building VyOS Because…We Can as it is an open source routing platform and further, allows one to supply their own hardware.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |