PR for CRUX https://github.com/vyos/vyatta-wireless/pull/14
Tested on 1.2.5-epa1 own build ISO.
sudo cat /var/log/vyatta/vyatta-commit.log [ interfaces wireless wlan0 ] Warning! system : missing regulatory domain country code
PR for CRUX https://github.com/vyos/vyatta-wireless/pull/14
Tested on 1.2.5-epa1 own build ISO.
sudo cat /var/log/vyatta/vyatta-commit.log [ interfaces wireless wlan0 ] Warning! system : missing regulatory domain country code
Can we add checks?
@dmbaturin Can you put it back on the rolling? We periodically have many appeals on this issue.
@rherold do you have any additional info how I can reproduce this issue?
Works correct on the latest rolling.
@c-po Sure, I can assist with that.
PR88 should add this.
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
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:
Good topic. Hopefully can be done as soon as possibly :)
sorry for this oversight.
is this still actual?
i propose to close it
VRF route leaking needs to be added to CLI. Routes can be leaked using:
already resolved in latest rolling due to rename of the node from secret to key.
Fixed via T2089