Release 1.9.1

README.md

@@ -6,17 +6,15 @@
 * Create *containerlab* configuration file
 * Create Ansible inventory and configuration file
 * Create IPv4 and IPv6 addressing plan and OSPFv2, OSPFv3, EIGRP, IS-IS, and BGP routing design
-* Configure IPv4, IPv6, DHCP, DHCPv6, VLANs, VRFs, VXLAN, LLDP, BFD, OSPFv2, OSPFv3, EIGRP, IS-IS, BGP, RIPv2, VRRP, anycast gateways, route maps, prefix lists, AS-path prefix lists, MPLS, BGP-LU, L3VPN (VPNv4 + VPNv6), 6PE, EVPN, SR-MPLS, or SRv6 on your lab devices.
+* Configure IPv4, IPv6, DHCP, DHCPv6, VLANs, VRFs, VXLAN, LLDP, BFD, OSPFv2, OSPFv3, EIGRP, IS-IS, BGP, RIPv2, RIPng, VRRP, anycast gateways, route maps, prefix lists, AS-path prefix lists, route redistribution, default route origination, MPLS, BGP-LU, L3VPN (VPNv4 + VPNv6), 6PE, EVPN, SR-MPLS, or SRv6 on your lab devices.
 
 Instead of wasting time creating lab topology in a GUI and configuring boring details, you'll start with a lab preconfigured according to your specifications.
 
 Interested? [Read the documentation](https://netlab.tools) and [installation guidelines](https://netlab.tools/install/).
 
 ## Releases
 
-The latest release is [release 1.9.0-post1](https://github.com/ipspace/netlab/releases/tag/release_1.9.0-post1). The 1.9.0 release contains tons of new features, and although we ran the most extensive integration tests ever, it might still have a few bugs.
-
-Should you encounter one of those creatures, please report it with [a GitHub issue](https://github.com/ipspace/netlab/issues/new/choose) and use release [release 1.8.4-post2](https://github.com/ipspace/netlab/releases/tag/release_1.8.4-post2) or [1.8.3](https://github.com/ipspace/netlab/releases/tag/release_1.8.3).
+The latest release is [release 1.9.1](https://github.com/ipspace/netlab/releases/tag/release_1.9.1). It should be pretty stable, but if you encounter bugs, please report them as [GitHub issues](https://github.com/ipspace/netlab/issues/new/choose) and use release [1.9.0-post1](https://github.com/ipspace/netlab/releases/tag/release_1.9.0-post1) or [1.8.4-post2](https://github.com/ipspace/netlab/releases/tag/release_1.8.4-post2).
 
 <!--
 If you encounter bugs using release 1.7.x, please downgrade to [1.6.4](https://github.com/ipspace/netlab/releases/tag/release_1.6.4) and [open a GitHub issue](https://github.com/ipspace/netlab/issues).
@@ -34,14 +32,17 @@ If you encounter bugs using release 1.7.x, please downgrade to [1.6.4](https://g
 : Restart and/or reconfigure the virtual lab. [More details](https://netlab.tools/netlab/restart/)
 
 **netlab config**
-: Applies additional Jinja2 configuration templates to network devices.
+: [Applies additional Jinja2 configuration templates](https://netlab.tools/netlab/config/) to network devices.
 
 **netlab collect**
-: Using Ansible fact gathering or other device-specific Ansible modules, collects device configurations and saves them in the specified directory (default: **config**).
+: Using Ansible fact gathering or other device-specific Ansible modules, [collects device configurations](https://netlab.tools/netlab/collect/) and saves them in the specified directory (default: **config**).
 
 **netlab connect**
 : Use SSH or **docker exec** to [connect to a lab device](https://netlab.tools/netlab/connect/) using device names, management network IP addresses (**ansible_host**), SSH port, and username/passwords specified in lab topology or *netlab* device defaults.
 
+**netlab capture**
+: [Perform packet capture](https://netlab.tools/netlab/capture/) on VM- and container interfaces
+
 **netlab report**
 : Creates a report from the transformed lab topology data.  [More details](https://netlab.tools/netlab/report/)
 

docs/index.md

@@ -11,19 +11,21 @@ Using *netlab* you can:
 
 Based on your lab topology the **[netlab up](netlab/up.md)** command will:
 
-* Create IPv4 and IPv6 addressing plan and OSPFv2, OSPFv3, EIGRP, IS-IS, BGP, MPLS/VPN, and EVPN routing design
+* Create IPv4 and IPv6 addressing plan and OSPFv2, OSPFv3, EIGRP, IS-IS, RIPv2/RIPng, BGP, MPLS/VPN, and EVPN routing design
 * Prepare all the necessary configuration files to start the lab
 * Start the lab using Vagrant or containerlab
 * Create additional virtual networking infrastructure needed to support your lab
 * Deploy initial configurations (interfaces, IPv4 and IPv6 addresses, usernames...) to your lab devices
-* Configure VLANs, VRFs, VXLAN, LLDP, BFD, OSPFv2, OSPFv3, EIGRP, IS-IS, BGP, VRRP, anycast gateways,
+* Configure VLANs, VRFs, VXLAN, LLDP, BFD, OSPFv2, OSPFv3, EIGRP, RIPv2, RIPng, IS-IS, BGP, VRRP, anycast gateways,
   MPLS, BGP-LU, L3VPN (VPNv4 + VPNv6), 6PE, EVPN, SR-MPLS, or SRv6 on your lab devices.
+* Configure prefix lists, AS-path filters, BGP community filters, route maps, route redistribution, and default route origination.
 * Start external network management tools specified in lab topology like Graphite or SuzieQ
 
-When the lab is fully configured, you can:
+When the lab is fully configured, you can use the:
 
-* Use the **[netlab connect](netlab/connect.md)** command to connect to network devices via SSH or **docker exec**
-* Use the **[netlab config](netlab/config.md)** command to deploy custom configuration snippets
+* **[netlab connect](netlab-connect)** command to connect to network devices via SSH or **docker exec**
+* **[netlab config](netlab-config)** command to deploy custom configuration snippets
+* **[netlab capture](netlab-capture)** command to capture packets on VM- or container interfaces
 
 Before shutting down your lab with the **[netlab down](netlab/down.md)** command, you might want to run the **[netlab collect](netlab/collect.md)** command to save the configuration changes you made.
 

docs/release.md

@@ -1,12 +1,11 @@
 Release Notes
 =============
 
-**[Release 1.9.1](release-1.9.1) (XXXX-XX-XX)**
+**[Release 1.9.1](release-1.9.1) (2024-10-05)**
 
-* [IS-IS route import](isis-node) ([redistribution](routing_import))
-* [IS-IS VRF instances](isis-platform)
-* [RIP VRF instances](rip-vrf)
-* [RIPng route import](rip-params)
+* [**netlab capture**](netlab-capture) command implements packet capture on VM- or container interfaces
+* IS-IS [route import](isis-node) ([redistribution](routing_import)) and [IS-IS VRF instances](isis-platform)
+* RIPv2/Ripng [route import](rip-params) and [VRF instances](rip-vrf)
 * [Configurable RIPv2/RIPng protocol timers](rip-timers)
 * Support for [Cisco IOSv layer-2 image](https://developer.cisco.com/docs/modeling-labs/iosvl2/#iosvl2)
 

docs/release/1.9.md

@@ -11,6 +11,7 @@
 (release-1.9.1)=
 ### Release 1.9.1
 
+* [**netlab capture**](netlab-capture) command implements packet capture on VM- or container interfaces
 * [IS-IS route import](isis-node) ([redistribution](routing_import))
 * [IS-IS VRF instances](isis-platform)
 * [RIP VRF instances](rip-vrf)
@@ -75,6 +76,7 @@ Arista EOS:
 
 Dell OS10:
 * Increase the VM RAM to 4GB according to vendor recommendations
+* Fix login credentials for vrnetlab containers
 
 FRRouting:
 * Limit ARP response scope when using VRRP on FRRouting
@@ -262,6 +264,7 @@ VyOS:
 * 'valid' validation test option should deal with list results
 * Create Vagrant box metadata in device/version-specific JSON file
 * Set routing protocol address families in VRF RP data
+* Use the existing 'SSH-in-VM-in-container' check for OS10
 
 (bug-fixes-1.9.0-post1)=
 ### Bug Fixes in Release 1.9.0-post1
@@ -306,6 +309,8 @@ VyOS:
 * Describe newer Fortinet caveats
 * Stress the importance of using the hellt fork of vrnetlab
 * Explain the details of setting Graphviz/D2 output defaults
+* Add Linux Host Networking caveats
+* Add favicon
 
 (doc-fixes-1.9.0-post1)=
 ### Documentation Fixes in Release 1.9.0-post1

legacy/setup.py

@@ -5,7 +5,7 @@
 
 sys.path.append('..')
 
-version="1.9.0-post1"
+version="1.9.1"
 
 long_description = (Path(__file__).parent / "README.md").read_text()
 

netsim/__init__.py

@@ -2,7 +2,7 @@
 
 import sys
 
-__version__ = "1.9.1-dev1"
+__version__ = "1.9.1"
 
 try:
   import box