Forgot that my PR for WLB was still a draft. That the jump does seem to be created properly with this PR in place.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Jan 11 2022
Jan 11 2022
sarthurdev changed the status of T4160: Firewall - Error in rules that matches everything except something from Open to In progress.
That build at 08:11 UTC was a couple of hours before the commit was merged: https://github.com/vyos/vyos-1x/commit/f97144259335102c3d96b232cbb0af4970120d62
yes , i'm using this version :
Unknown Object (User) added a comment to T4167: DMVPN apply wrong param on the first configuration.
Seems to be working on my latest build?
Unknown Object (User) changed the status of T4167: DMVPN apply wrong param on the first configuration from Open to In progress.
I've checked with this new build , it works with validator ranges/port :
bjw-s updated the task description for T4174: Validation fails when entering port range with upper port 65535.
I've been testing and it works :
sarthurdev changed the status of T4164: PBR: network groups (as well as address and port groups) don't resolve in `nftables_policy.conf` from Open to Needs testing.
Thanks, I really like the include idea and have implemented it in the attached PR. Also added a check in firewall.py to reload policy-route script to keep any group changes updated.
sarthurdev changed the status of T4159: Empty firewall group (address, network & port) generates invalid nftables config, commit fails, a subtask of T2199: Rewrite firewall in new XML/Python style, from Open to Needs testing.
sarthurdev changed the status of T4159: Empty firewall group (address, network & port) generates invalid nftables config, commit fails from Open to Needs testing.
PR removes the empty line when there are no group members, also adds a warning message when empty groups are used in rules.
sarthurdev changed the status of T4131: Show firewall group incorrect format members from Open to Needs testing.
@Viacheslav Not using exact ipset format, however addresses are sorted and output one per line.
sarthurdev changed the status of T4144: Firewall address-group - Improve error messages from In progress to Needs testing.
Should resolve the rest of the error messages.
well , I think it should be something like this :
c-po changed the status of T4171: Interface config migration error on 1.2.8 -> 1.4 upgrade from Open to In progress.
erkin closed T3950: CLI backtrace on update if DNS not defined , a subtask of T3356: Script for remote file transfers, as Resolved.
Chained exceptions are covered too (and backported to Equuleus).
Invalid - already available - I looked into an 1.2.8 image.
erkin reopened T3950: CLI backtrace on update if DNS not defined , a subtask of T3356: Script for remote file transfers, as In progress.
Unknown Object (User) assigned T4168: IPsec VPN is impossible to restart when DMVPN is configured to Viacheslav.
Unknown Object (User) created T4168: IPsec VPN is impossible to restart when DMVPN is configured.
Unknown Object (User) created T4167: DMVPN apply wrong param on the first configuration.
Hi, I've just submitted a pull request (https://github.com/vyos/vyos-1x/pull/1154) to hopefully complete this bugfix.
Jan 10 2022
Jan 10 2022
jestabro triaged T4166: Debug output missing when frr.py called under vyos-configd as Normal priority.
@fernando Thanks, do you have any idea about syntax?
Viacheslav changed the status of T4152: NHRP shortcut-target holding-time does not work from In progress to Needs testing.
johannrichard updated the task description for T4164: PBR: network groups (as well as address and port groups) don't resolve in `nftables_policy.conf`.
sarthurdev changed the status of T4144: Firewall address-group - Improve error messages from Open to In progress.
IPv4 address range error messages are included in PR: https://github.com/vyos/vyos-1x/pull/1152
sarthurdev changed the status of T4148: Firewall - Error messages not that clear as it were in old firewall from Open to Needs testing.
Error for rule being in use when deleting base node was fixed in https://github.com/vyos/vyos-1x/pull/1151
sarthurdev changed the status of T4137: Firewall group configuration allows to set incorrect port range and invalid port from Open to Needs testing.
this PR https://github.com/vyos/vyos-1x/pull/1088 only include how to enable daemon , but it doesn't add VyOS-cli commands in BGP (the daemon only allows you to enable it).
@Viacheslav / @vindenesen that is a bug I have also seen in the old iptables based implementation. Can you please file a bug report towards VyOS 1.2 and 1.3?
There is PR which includes this feature https://github.com/vyos/vyos-1x/pull/1088
sarthurdev changed the status of T4149: [Firewall-IPV6] Error delete Fw rules on VIF/INT from In progress to Needs testing.
sarthurdev changed the status of T4155: PBR: `set table main` fails in `firewall.py` with newer rolling releases , a subtask of T2199: Rewrite firewall in new XML/Python style, from Open to Needs testing.
sarthurdev changed the status of T4155: PBR: `set table main` fails in `firewall.py` with newer rolling releases from Open to Needs testing.
Thanks for catching that!
sarthurdev changed the status of T4149: [Firewall-IPV6] Error delete Fw rules on VIF/INT from Open to In progress.
Previous example was expanded, in order to test filtering between native bridge interface and vlans interface on bridge.
Filtering rules:
- Filter traffic from vlan br0.55 to br0.66
- Filter traffic from vlan1 to br0.55
- Allow all
I'm experiencing this with a custom ISO built from the stable 1.3 sources. Haven't done further debugging yet, a bgpd restart helped every time.
Unknown Object (User) added a comment to T4100: Firewall increase maximum number of rules.
In 1.3 (VyOS 1.3-rolling-202201030317) the rules are handled correctly (except for the numbers in description).
Viacheslav moved T3299: Allow the web proxy service to listen on all IP addresses from Need Triage to Finished on the VyOS 1.3 Equuleus ( 1.3.1) board.
Ah! ok, I will close this. Looking at the man pages, seems like open nhrp doesn't have a no-unique registration feature?
We don’t use frr nhrpd, more details T2326
We use opennhrp
johannrichard added a comment to T4159: Empty firewall group (address, network & port) generates invalid nftables config, commit fails.
I just realize it's getting more complicated as python/vyos/firewall.py will later write out the rules for these empty groups and when reading-them in, nftables will complain (again) when trying to resolve them, e.g.
Pythonic reimplementation complete. Now only the XML op-mode definition and the auto-complete script remain.
johannrichard renamed T4159: Empty firewall group (address, network & port) generates invalid nftables config, commit fails from Rewrite firewall in new XML/Python style: Empty firewall group (address, network & port) generate invalid nftables config, commit fails to Empty firewall group (address, network & port) generates invalid nftables config, commit fails.
johannrichard added a comment to T4159: Empty firewall group (address, network & port) generates invalid nftables config, commit fails.
To my understanding, the template data/templates/firewall/nftables.tmpl is probably the culprit, as it doesn't check whether group_conf.address (and similarly the others) has any elements at all and introduces the offending white-space:
Jan 9 2022
Jan 9 2022
In ISC dhcpd this corresponds to the boot-size option http://www.ipamworldwide.com/ipam/isc-dhcpv4-options.html
c-po moved T3924: VRRP stops working with VRF from Need Triage to Finished on the VyOS 1.3 Equuleus ( 1.3.1) board.
c-po changed Why the issue appeared? from none to third-party on T3924: VRRP stops working with VRF.
c-po moved T4141: Set high-availability vrrp sync-group without members error from Need Triage to Finished on the VyOS 1.3 Equuleus ( 1.3.1) board.
c-po moved T4128: keepalived: Upgrade package to add VRF support from Need Triage to Finished on the VyOS 1.3 Equuleus ( 1.3.1) board.
c-po added a project to T4128: keepalived: Upgrade package to add VRF support: VyOS 1.3 Equuleus ( 1.3.1).
Package upgraded
c-po moved T3914: VRRP rfc3768-compatibility doesn't work with unicast peers from Need Triage to Finished on the VyOS 1.3 Equuleus ( 1.3.1) board.
c-po edited projects for T3914: VRRP rfc3768-compatibility doesn't work with unicast peers, added: VyOS 1.3 Equuleus ( 1.3.1); removed VyOS 1.3 Equuleus (1.3.0).