Comparison with legacy priority.pl can be seen with priority.py --legacy-format, below; note that priority of 0 is default for interface-definitions lacking a priority element, as is assigned in legacy commit algorithm.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Mar 21 2024
I have checked in with @sharpd, he mentioned that it might not be supported to use v4 nexthop for v6 route.
From local testing:
vova | ip r default via 192.168.0.1 dev wlp4s0 proto dhcp metric 600 192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.102 metric 600
PR for subtask bug merged:
https://github.com/vyos/vyos1x-config/pull/24
PR for this task will follow the update/rebuild of libvyosconfig.
Mar 20 2024
This likely because the global state policy being reintroduced was not accounted for in the firewall check in conf script. I'll check this week.
We have something like this already for !in! interfaces:
PR https://github.com/vyos/vyos-1x/pull/3155
set service config-sync secondary address 192.0.2.1 set service config-sync secondary timeout 3600
Mar 19 2024
As discussed, this will wait before being backported to 1.4.
PR https://github.com/vyos/vyos-1x/pull/3150
vyos@r4:~$ show conntrack table ipv4 Id Original src Original dst Reply src Reply dst Protocol State Timeout Mark Zone ---------- ----------------- ------------------- ------------------- -------------------- ---------- ----------- --------- ------ ------ 2589405901 192.0.2.14:37122 34.206.168.146:123 34.206.168.146:123 192.168.122.14:37122 udp 99 0 931438034 192.168.122.14:22 192.168.122.1:56010 192.168.122.1:56010 192.168.122.14:22 tcp ESTABLISHED 431999 0 4269448361 192.0.2.14:43882 34.117.118.44:80 34.117.118.44:80 192.168.122.14:43882 tcp TIME_WAIT 116 0 821718377 192.0.2.14:36208 1.1.1.1:53 1.1.1.1:53 192.168.122.14:36208 udp n/a 0 vyos@r4:~$ vyos@r4:~$
In T6136#180149, @n.fort wrote:And a simple note for your usage @wenzk
Change
set firewall ipv4 name WAN_IN rule 30 icmp
to this:
set firewall ipv4 name WAN_IN rule 30 protocol icmp
Mar 18 2024
👍
Thanks
Fix to docs pending:
https://github.com/vyos/vyos-documentation/pull/1331
Well that is a fault of the docs; I will add now. Thanks !
@jestabro this is perfect, I am so sorry for creating a false feature request. The doc does not mention it, I should have looked into the server code to check first. My bad, all good now.
curl -k -X POST -Fkey=baz -Fdata='{"op": "exists", "path": ["service","no","such","subpath"]}' https://192.168.122.238/retrieve|jq
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 340 100 47 100 293 547 3414 --:--:-- --:--:-- --:--:-- 4000
{
"success": true,
"data": false,
"error": null
}@penetal does the operation 'exists' not suffice for your needs ?
And a simple note for your usage @wenzk
Change
set firewall ipv4 name WAN_IN rule 30 icmp
to this:
set firewall ipv4 name WAN_IN rule 30 protocol icmp
Mar 17 2024
Here's the generated configuration from /run/conntrackd/conntrackd.conf:
# Synchronizer settings
Sync {
Mode FTFW {
DisableExternalCache on
}
Multicast {
IPv4_address 225.0.0.50
Group 3780
IPv4_interface 192.168.15.3
Interface bond0.110
SndSocketBuffer 104857600
RcvSocketBuffer 104857600
Checksum on
}
}
Helper {
Type rpc inet tcp {
QueueNum 3
Policy rpc {
ExpectMax 1
ExpectTimeout 300
}
}
Type rpc inet udp {
QueueNum 4
Policy rpc {
ExpectMax 1
ExpectTimeout 300
}
}
Type tns inet tcp {
QueueNum 5
Policy tns {
ExpectMax 1
ExpectTimeout 300
}
}
}