Reopen it you are working on it.
Closes it as wontfix because there are no opensource codes that I found which was provided
On the main page only some prices and " All plans come with a free 14-day trial. "
It is not clear what is required and which CLI is proposed
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jan 19 2024
@shthead add an example of "set| commands to reproduce
@aalmenar Explain the required feature in more detail
@bbabich Are you working on it?
Can you create a PR?
@Apachez Could you recheck if it works as you expected?
vyos@r4# set high-availability vrrp group FOO garp
Possible completions:
interval Interval between Gratuitous ARP (default: 0)
master-delay Delay for second set of gratuitous ARPs after transition to
master (default: 5)
master-refresh Minimum time interval for refreshing gratuitous ARPs while
beeing master (default: 5)
master-refresh-repeat
Number of gratuitous ARP messages to send at a time while beeing
master (default: 1)
master-repeat Number of gratuitous ARP messages to send at a time after
transition to master (default: 5)Fixed:
vyos@r4:~$ show interfaces wireless info No Wireless interfaces configured vyos@r4:~$ vyos@r4:~$ vyos@r4:~$ show version Version: VyOS 1.5-rolling-202401190024 Release train: current
@I-n-d-y Try to get it working without VyOS CLI.
Provide the required contrack config. As I'm not sure that it will work correctly at all.
Fixed
vyos@r1# set interfaces ethernet eth1 description test [edit] vyos@r1# time commit
If the problem exists, it should be fixed on accel-ppp site.
I am not sure that I can help here as it is written on C
Use the persist option as after each interface, recreation indexes are created dynamically.
Tested in latest 1.5-rolling-202401190024 release, the commit fails when duplicate static-mapping is configured as expected.
@sdev Quick question on this issue.
Jan 18 2024
PR https://github.com/vyos/vyos-1x/pull/2852 basic implementation
Will be fixed in 1.4.0-rc3
After some research, I have concluded that the error was caused by the string's violation of RFC 3986, which recommends using percent encoding instead. I'll look into the feasibility of implementing percent encoding/decoding (which urllib natively supports) for spicy characters if there's demand, but the recommended method in VyOS right now is using the protocol-agnostic REMOTE_USERNAME and REMOTE_PASSWORD environment variables, which bypass the URL decoding step. The alternative would involve messing with urllib.parse's internal parser to implement a laxer and less greedy regexp to accept passwords like this, which is probably a bad idea.
What are you expecting
This should pretty much explain it
Expecting minimal working config:
set qos policy shaper-hfsc SHAPE bandwidth '400mbit' set qos policy shaper-hfsc SHAPE class 10 linkshare m2 '200mbit' set qos policy shaper-hfsc SHAPE class 10 match DST ip destination address '192.0.2.1/32' set qos policy shaper-hfsc SHAPE default linkshare m2 '111mbit'
It causes the issue with no qos config after update (from 1.3.5)
Before migration
set traffic-policy shaper-hfsc SHAPE-10mbit bandwidth '400mbit' set traffic-policy shaper-hfsc SHAPE-10mbit class 10 linkshare m2 '200mbit' set traffic-policy shaper-hfsc SHAPE-10mbit class 10 match MARK mark '10' set traffic-policy shaper-hfsc SHAPE-10mbit default linkshare m2 '200mbit'
Waiting for the stable release Release v2.20
Jan 17 2024
Sounds good. I'll do some updates and testing to see if I can move the chains to a dedicated inet table for upnp. The IPv6 use case is probably just to use UPnP/NAT-PMP/PCP to open firewall ports but for completion reasons I'll implement it.
Sounds like a great solution to me, happy to review your PR.