The fix for values containing single backslashes has been merged for 1.5 in
https://github.com/vyos/vyos1x-config/pull/23
https://github.com/vyos/vyos-1x/pull/3035
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 19 2024
As discussed, this will wait before being backported to 1.4.
Show this commands output if that happens:
show interfaces pppoe pppoe0 show ip route show log pppoe
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 ?
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:-