Fixed temporarily for now in https://phabricator.vyos.net/R3:1c4414dd363bdb268038ae238686be3e0b7f988b
We should re-add building it from upstream to fix T1538.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Mar 1 2020
Feb 29 2020
The changes are also part of the patch for T2057 which was merged.
All my apologies for this stupid bug.
Feb 28 2020
Sorry, I titled the task wrong. The error is in building conntrack-tools.
I think you're right, I couldn't find any package depending on it, vyatta-conntrack-sync only depends on conntrack.
I also found this https://phabricator.vyos.net/T1538 in which the conclusion is we should upgrade conntrack-tools.
I guess that one is deprecated as we also don‘t have it in our CI at https://ci.vyos.net/
looks for my like an frr bug. Has someone contacted upstream?
As PPPoE is now denested the logic in Vyatta::Interfaces needs to be adjusted
I can confirm this bug also with VyOS 1.2.4
Feb 27 2020
For TLS crypt please see T2075
This should actually be possible after the PPPoE interface rewrite in the latest rolling image.
No answer from user.
Feb 26 2020
Yes there are definately other places like DHCP.
I personally don't mind the raw options, and there are other people using them too (T127, T1246, T1383, T1421, T1430).
There is no option for tls-crypt, just tls-auth. Also I'm experimenting with the various mtu options (tun-mtu, link-mtu, mssfix, fragment) and keepalive options (ping-restart, ping) that can't be set through the existing keepalive options (keepalive doesn't take 0 as a value if I want ping-restart 0 for example, and there's no way to not have keepalive be set with default vaules). So yeah, if all of these options were integrated, I personally wouldn't need the openvpn-options. But I think there are other places that use raw values with quotes that are affected by the autocompletion bug too, dhcp-server for example.
Thats the downside of those nodes which allow passing raw values down the config. I never liked them and they should be removed. The CLI should be extended to support the raw options instead.
Feb 25 2020
Feb 24 2020
PR for 1.3-rolling https://github.com/vyos/vyos-1x/pull/228
FWIW, this issue is still occuring on 1.3 rolling (1.3-rolling-202002180217) for interfaces with DHCP set. While the above referenced repository is archived, the script here https://github.com/vyos/vyos-vmwaretools-scripts/blob/current/scripts/resume-vm-default.d/ether-resume.py seems to be the latest version.
For any interface with DHCP enabled, it will try to run
ip address add dhcp dev ethX
Since dhcp is not a valid address this fails and after the interface loses it's IP until dhclient is run manually or the system reboots. The script linked by @dmaasland works correctly.
The patch is ready for inclusion.
This work raised an issue with the current pattern of using Interface(..).remove() which is used in VLANIf as it requires Interface to know that EthernetIf can not be deleted (an implementation detail which should remain in EthernetIf).
@hagbard thanks, works as expected. I think this might be backport candidate to 1.2.X
https://github.com/vyos/vyos-1x/commit/d9fa3fb7d7613cd5d6297115da0dc63462d4cf69
@Dmitry next rolling will have it enabled, let me know if it works for you as intended.