Thanks @Viacheslav, that makes sense.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Feb 11 2023
Feb 10 2023
Take a look at this T4165
Maybe the same issue but per rule. Different order of "comment"
Thanks for reporting.
We will take a look at it.
I have the same issue
Some adjustments made for command output; re-testing for PR.
Feb 9 2023
Running smoketests; PR's to follow:
eth0 -> PPPoE (Primary link)
eth1 -> DHCP (Backup link)if I use default-route 'auto' for pppoe then default route via pppoe is not getting configured. That's why I am defining the static default route for pppoe with default-route 'none' option.
I have two wan links as following-
It looks like mine issue with wan load balancing - reply for dnat-ed packets from secondary interfaces was sent by vyos from "primary" https://phabricator.vyos.net/T4587 . Could you dump traffic and check that possibility
@fernandolcx Will be present in the next rolling release, could you test it (after 20230209)?
Feb 8 2023
@c-po Do you have any idea for CLI?
@skoenman Could you write some examples of configuration?
@Usman there is a root task for op-mode rewriting https://phabricator.vyos.net/T4564
https://github.com/vyos/vyos-1x/blob/1042fc32c371a74f048ffaf9a551b5d13c227f45/src/op_mode/bgp.py#L77-L80
@Viacheslav Thanks, that works great!
@Usman You have to update to the latest rolling.
https://vyos.net/get/nightly-builds/
Thanks for the reply.
Hi perhaps it is better to get JSON format
I would prefer a different syntax, in order to avoid the necessity attaching it to an interface. Maybe something like:
Error detected in forum: https://forum.vyos.io/t/unable-to-query-snmp-anymore-in-a-more-recent-1-4-version/10388/3
Fix for that bug: https://github.com/vyos/vyos-1x/pull/1805
Why did you delete this option and add a static route? Is there any use case?
This option has more priority than others.
Rewritten in 1.4
We are not planning to modify it in 1.3
Got it; it is impossible for now after this migration https://phabricator.vyos.net/T3090
We are working on the re-design firewall CLI
Feb 7 2023
I built a 1.4 ISO after my change was merged and deployed it to my home network. Setting a restrictive allow list works as expected, only the allowed IPs/subnets are able to use NTP. Removing all allow IPs prevents chrony/ntp from even listening to port 123. I don't think the "deny all" is needed in the code at all, but it is also not preventing the service to run as expected so I'll leave it.
@c-po is this an S3 bucket policy issue, or do the files not exist?