- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Yesterday
Thanks rherold 😊
I was still wondering, is there any take of the VyOS devs on the above?
Fri, Oct 9
Not reproducible
Update: in our case this was not an FRR bug, it was a firewall problem on our side.
The status changes only if the system is rebooted. The situation is the same in the opposite direction. After rebooting, I cannot bring up the disabled vti interface.
@DuxOv8 as you could see on the PR link is it not merged yet.
In T6563#234214, @marvin wrote:Thanks @Viacheslav.
FWIW, it looks like Jool's official documentation site is now https://nicmx.github.io/Jool/en/index.html (not jool.mx anymore).
I think this specific task has now been made redundant by the move towards netlinkd being responsible for performing reconnections off of kernel events. Therefore I recommend this ticket be closed
Thu, Oct 8
Or maybe it hasn't been implemented in the code yet
Hello all
Thanks for response but i have a bug
set service dhcp-server client-class Yealink_T42S hostname substring value 'T42S'
@evgmol do we have any reason to have this task?
There are no PRs, implementation and so on. Can we close it?
We can use a custom script to get these values
Example for developers on how we get the firewall rules, interfaces, and services https://github.com/vyos/vyos-1x/tree/rolling/src/etc/telegraf/custom_scripts