Can we add checks?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 14 2020
@dmbaturin Can you put it back on the rolling? We periodically have many appeals on this issue.
Mar 13 2020
Successfully tested on VyOS 1.2.5-epa1
@rherold do you have any additional info how I can reproduce this issue?
Works properly on VyOS 1.2.5-epa1 (FRRouting 7.2-20200121-02-g031c58) and 1.3-rolling-202003130217(FRRouting 7.3)
Mar 12 2020
Thanks @jestabro , works well with this change. After passing all the tests, I will write docs about VyOS in container.
Works correct on the latest rolling.
Mar 11 2020
@Dmitry The simplest workaround for the moment is to add the following to your load steps:
@c-po Sure, I can assist with that.
I've tracked this down to a bug in libboost-filesystem, versions < 1.56, that occurs if the locale is not properly set, as is the case within the Docker environment:
The code is now merged. Can somebody update this task?
PR88 should add this.
Mar 10 2020
I haven't encountered this since, but the single 1.2 router is still on rc11, which has updated pdns-recursor 4.2, before being reverted: https://phabricator.vyos.net/R3:8c22ceead487b745d6b7c058c4d1c0a0eaa051c8 so it may still possibly be an issue in 1.2.
I've never encountered it on 1.3 rolling.
I once wrote a script as PoC to list build dependencies:
I'm not in the VyOS core team so I'm not able to make direct decisions on the resolution, but as I see it, there are several possible ways to approach this.
Max positive value for Integer32 = 2147483647
Max negative value = -2147483648
Mar 9 2020
I'd like to know what the long term plan is here. How are "small time" developer supposed to be able to build the kernel related packages? I was in the middle of testing some change to wireguard, but now everything is on hold because I can't build the current kernel anymore without a significant effort. I'm open to help but I would need to know what the plan is for builds without Jenkins.
Thanks for the quick fix c-po, I noticed this also needs to be fixed in /usr/libexec/vyos/op_mode/reset_openvpn.py in case someone runs for example:
Hi @SteveP , VyOS has own CLI for ping command, use ping and <TAB>
vyos@R1:~$ ping 1.1.1.1 Possible completions: <Enter> Execute the current command adaptive Ping options allow-broadcast audible bypass-route count deadline flood interface interval mark no-loopback numeric pattern quiet record-route size timestamp tos ttl verbose