- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 9 2023
May 8 2023
May 6 2023
May 5 2023
In T5082#148096, @onedr0p wrote:@c-po I know we're on rolling for 1.4 but is there any way to communicate breaking changes like this in the future? If this was mentioned in the PR or ticket I don't think there would have been any confusion.
As for this tickets status it can be closed.
May 4 2023
@dcplaya yeah that was a transitional error/quirk as we renamed that one during the development cycle.
May 3 2023
Hi, the reason why the modem does not show up is because usb0 interfaces do not match the prefix we use to distinguish between interfaces.
Apr 30 2023
Added requested config option to Kernel for 1.4
Apr 29 2023
In either case when trying to PING or TRACEROUTE from a device on my LAN network I can PING and TRACEROUTE 192.168.254.2.
No iptables installed, and also no vyos-1x-smoketest package.
Apr 28 2023
can you add some more detials? I just used your above container config and upgraded from a VyOS version that came with CNI to a version with netavark and I do not see that error.
netavark was added 2023-04-02.
Apr 27 2023
Your CLI config is valid in general but FRR will refuse it with the error message: This command is only supported under EVPN VRF
Apr 26 2023
Do you know how to tell Linux to use nameservers within a VRF?
What you mean IPSec/OpenVPN "punch a tunnel through a VRF" ? So the underlay should run via a VRF? source-interface binding does not work?