👍
Thanks
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Mar 18 2024
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 ?
It looks like the local broken build.
At least it is not reproducible.
You can try to set it on some test VM to be sure if is it an issue with the node or the image itself.
In T6126#180142, @Viacheslav wrote:Can you try the same link as in my example and provide the full output?
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
@Viacheslav I'm not super familiar with git, so hopefully I did everything correctly. Here is the PR:
https://github.com/vyos/vyos-1x/pull/3145
Can you try the same link as in my example and provide the full output?
In T6126#180130, @Viacheslav wrote:Could you show show version?
Could you show show version?
Never had this bug with 1.4.0-epa.
vyos@r1-right:~$ show ver Version: VyOS 1.4.0-epa1 Release train: sagitta
@matthewr Thanks for confirming!
Closing it as resolved now. Feel free to reopen or create a new one if this bug remains again.
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
}
}
}Fixed in https://github.com/vyos/vyos-1x/commit/84b520dd580b7725de4c9e62b11ec490cb8d3f4f. The 1.4.0-epa2 build was created before the patch was applied.
Just in case it helps, after a migration from 1.3 to 1.4.0-epa2, the migrated config ends up as:-
See T6131 for a report of the VTUN/OSPF issue with a simple lab config, which occurs separately from a migration.
Mar 16 2024
We'll update the key and make a post about it soon, sorry for the lengthy mix-up.
comments above are for https://vyos.net/get/nightly-builds/
Bumped into another instance of this issue:
curl -k --location --request POST "https://$VYOS_HOST/configure" --form key="$VYOS_KEY" --form data='[{"op":"set","path":["policy", "access-list", "2", "rule", "5", "description", "2024-03-16T14:52:44Z"]}]' {"success": false, "error": "[[policy]] failed\nCommit failed\n", "data": null}
@jestabro I have tested my usecase now and it seems the problem is fixed and the API no longer segfaults. Thank you so much for the fix and the fantastic turn around on this.
Mar 15 2024
Should add the ability to view the default action log would be nice as well.