netlab
netlab copied to clipboard
Making virtual networking labs suck less
Example: ``` links: - s1: s2: vlan.trunk: [ irb, route ] vlan.native: irb - s1: lag.id: 1 lag.peer: s2 h1: - s2: lag.id: 1 lag.peer: s1 h1: ``` For discussion...
``` core1# show running-configuration ! [cut] ! ip vrf blue ip route-export 65000:2 ip route-import 65000:2 ip route-import 65000:1 ! ip vrf common ip route-export 65000:1 ip route-import 65000:3 ip...
Check what happens when you use named prefixes with bgp.originate plugin
I don't know if it's me (maybe yes), but cannot find the `allocation` specific documentation. _Originally posted by @ssasso in https://github.com/ipspace/netlab/pull/1235#discussion_r1685357684_
bgp.policy plugin provides a shortcut way of adding route-maps (or standalone attributes like 'weight') to BGP sessions. It defines the same attributes as the 'routing' module does for the 'rp_entry'...
Nobody touched Fortinet implementation in a long long time, and the vendor moved on ;) Here are the versions that work: * fortios v7.0.15 (built with https://github.com/mweisel/fortigate-vagrant-libvirt) * ansible-core==2.16.7, ansible==9.6.1...
netlab has runtime- and developer requirements. Have to mention that the developers should install the development requirements as well.
The current documentation assumes the gateway module works on Cat8Kv, but it would be nice to know that's true ;)
CSR 1000v does not support routed VLAN subinterfaces, and as Cat8Kv is its clone, you cannot use them on Cat8Kv as well... but maybe they work? Time to test it...