* fix: Fix pattern to handle long system identity names
When the system identity string is too long, the terminal output may be
truncated. The truncated output is marked by multiple carriage returns
(`\r`) and a `<` symbol.
This is a example of a truncated output:
`\r\n\r\r\r\r<MY_VERYVERY-LONG-SYSTEM-IDENTIY-NAME] > `
The existing regex failed to match these truncated prompts.
This update introduces a more flexible regex that matches both, the truncated and the preserved output.
* add change-log fragment for pr 386
* refactoring change-log fragment for pr 386
* Update changelogs/fragments/386-fix-pattern-to-handle-long-identity.yml
Co-authored-by: Felix Fontein <felix@fontein.de>
---------
Co-authored-by: Felix Fontein <felix@fontein.de>
* Since RouterOS 7.17 VRF is supported for OVPN server. It now supports
multiple entries and single-value is now obsolete. This demands for a
versioned API.
* Add change fragment
* Add change fragment
* add license field
* Update changelogs/fragments/385-vrf-support-for-ovpn-server
Co-authored-by: Felix Fontein <felix@fontein.de>
* rename
* remove license field
---------
Co-authored-by: Felix Fontein <felix@fontein.de>
The behaviour of the `passthrough` property in `ip/firewall/mangle` has
changed in RouterOS 7.19:
```
*) firewall - always show "passthrough" when exporting mangle table;
```
Per the documentation at [1] the default is `true`.
[1] https://help.mikrotik.com/docs/spaces/ROS/pages/48660587/Mangle
From the RouterOS 7.17 changelog:
*) ipv6 - added IPv6 settings related to stale IPv6 neighbor cleanup;
*) ipv6 - added support for manual link-local address configuration;
And from the RouterOS 7.18 changelog:
*) ipv6 - added FastTrack support;
*) ipv6 - added support for neighbor removal and static entries;
The change also removes the default value for the `max-neighbor-entries`
field. It's documented to vary depending on the RAM size.
* Update _api_data.py
Add /interface/bridge property "port-cost-mode" which is supported since RouterOS 7.13.
See changelog for details: https://mikrotik.com/download/changelogs
* Create 371-add-bridge-port-cost-mode.yml
* Update changelogs/fragments/371-add-bridge-port-cost-mode.yml
Co-authored-by: Felix Fontein <felix@fontein.de>
* Support for /interface ethernet switch port-isolation
RouterOS has supported the /interface ethernet switch port-isolation path since version 6.43.
This feature enables hardware offloaded Layer‑2 port isolation on supported switch chips
Support for /routing bfd configuration
Since RouterOS 7.11 it supports stable bfd support.
See: https://iparchitechs.com/mikrotik-routeros-v7-11-stable-released/
* .
* Add change file
* attr order
* Add name to fields
* PEP8
* Update changelogs/fragments/375-port_isolation-and-routing_bfd_configuration.yml
Co-authored-by: Felix Fontein <felix@fontein.de>
* Update changelogs/fragments/375-port_isolation-and-routing_bfd_configuration.yml
Co-authored-by: Felix Fontein <felix@fontein.de>
---------
Co-authored-by: Felix Fontein <felix@fontein.de>
Co-authored-by: Michael Jenny <mjenny@ansible.zvcloud.de>
* Update _api_data.py
Add /interface/bridge property "port-cost-mode" which is supported since RouterOS 7.13.
See changelog for details: https://mikrotik.com/download/changelogs
* Create 371-add-bridge-port-cost-mode.yml
* Update changelogs/fragments/371-add-bridge-port-cost-mode.yml
Co-authored-by: Felix Fontein <felix@fontein.de>
---------
Co-authored-by: Felix Fontein <felix@fontein.de>
* Field name change in 'routing bgp connection' (from 'address-families' to 'afi')
* Field name change in 'routing bgp connection' (from 'address-families' to 'afi')
From the RouterOS 7.17 changelog:
> *) cloud - changed ddns-enabled setting from "no" to "auto" (service
> is enabled when BTH is enabled);
`no` is not supported anymore, only `yes` and `auto` are.
* Add new parameters from RouterOS 7.16 release
h3. /interface/bridge
- `forward-reserved-addresses` with default value `False`
- `max-learned-entries` with default value `auto`
h3. /ip/neighbor/discovery-settings
- `lldp-mac-phy-config` with default value `False` (from Router OS 7.15
release)
- `discover-interval` with default value `30s`
- `lldp-vlan-info` with default value `False`
h3. /ip/settings
- `ipv4-multipath-hash-policy` with default value `l3`
h3. /ipv6/settings
- `multipath-hash-policy` with default value `l3`
h3. /ip/dhcp-server/option
- `comment`
h3. /ip/dhcp-server/option/sets
- `comment`
h3. /ip/dhcp-server/matcher
- `comment`
h3. /tool/netwatch
- `acccept-icmp-time-exceeded` with default value `False`
- `ttl` with defaut value `255`
h3. /ip/service
- `max-sessions` with default value `20`
Add changelog fragment
* Update changelogs/fragments/323-add-ros-7.16-parameters.yml
Co-authored-by: Felix Fontein <felix@fontein.de>
---------
Co-authored-by: Felix Fontein <felix@fontein.de>
* Add default to snmp community api_data
* Add changelog fragment
* fix typo
* suggestion from felixfontein
* suggestion from felixfontein
* Apply suggestions from code review
---------
Co-authored-by: Felix Fontein <felix@fontein.de>
* Added support for 'routing filter num-list'
* Added support for 'routing filter num-list', changelog
* Added support for 'routing filter num-list', changelog
* Allow to restrict api_info output.
* Allow to restrict what api_modify modifies.
* Add changelog.
* Fix docs.
* Move shared code/docs to module utils and doc fragments.
* Refactor and allow to match by regex.
* Simplify rules, allow to invert rule matcher.
* Add more tests.
From the RouterOS 7.15 changelog:
```
*) wireguard - added option to mark peer as responder only;
*) wireguard - added peer "name" field and display it in logs;
```
* Fix typos in comment on IPsec policy "template" field
* Move IPv4 DHCP server API data next to other DHCP APIs
* Set default for "force" field on DHCP options
Without the default value removing it from the options after it's been
set once leads to an error:
> Key "force" cannot be removed for name="…"
* Add IPv4 DHCP option matcher
RouterOS 7.4 and newer implement matchers for the Vendor ID provided by
DHCP clients. RouterOS 7.16 will add a new `matching-type` property, but
it's not in a stable release yet.
Upstream documentation:
https://help.mikrotik.com/docs/display/ROS/DHCP#DHCP-Genericmatcher
