The old backend doesn't allow it to do it for 1.3 Release.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 28 2023
@Sonicbx As I remember, HyperV is not affected.
But thanks anyway,
Could you provide your policy route?
Not sure that it is a good idea.
At least not for the LTS release.
I close it until we don't really need it and there are no use cases to do it.
Reopen it if required.
@kroy What is wrong here?
set policy prefix-list foo rule 10 action 'permit' set policy prefix-list foo rule 10 prefix '10.0.0.0/8'
In T1311#157738, @syncer wrote:@Viacheslav will you backport this to 1.3 ?
@Sonicbx Is it an actual bug?
Implemented in previous versions, https://github.com/vyos/vyos-1x/blob/a5c5998a84917cc45f9fb3234607f53b27a109fc/interface-definitions/include/interface/mirror.xml.i#L1-L25
vyos@r1# set interfaces ethernet eth0 mirror Possible completions: egress Mirror the egress traffic of the interface to the destination interface ingress Mirror the ingress traffic of the interface to the destination interface
@n.fort Add please a PR for 1.3 or delete the 1.3 tag if it is not required
It is not a task for 1.3 LTS releases.
For 1.4, there a new feature that was implemented in https://vyos.dev/T5228
get_config_dict and add argument with_defaults
Route leaking for dynamic protocols won't be implemented in VyOS 1.3 due to the old backend.
You can set a table in the route-map or use virtual-ethernet interfaces
PR https://github.com/vyos/vyos-1x/pull/2182
vyos@r1:~$ show pppoe-server interfaces
interface: connections: state:
-----------------------------------
eth0 1 active
vyos@r1:~$The cluster feature will be deprecated, as we use systemd we should avoid init.d scripts.
All logic should be rewritten to VRRP
@dmaasland @jestabro Can we close it?
The event handler was rewritten to python3 and doesn't use pipes.
@runar Can we close it?
vyos@r1# set interfaces bridge br0 member interface eth1 Possible completions: + allowed-vlan Specify VLAN id which is allowed in this trunk interface cost Bridge port cost isolated Port is isolated (also known as Private-VLAN) native-vlan Specify VLAN id which should natively be present on the link priority Bridge port priority
There are not such options in FRR
r14(config-route-map)# set ip next-hop A.B.C.D IP address of next hop peer-address Use peer address (for BGP only) unchanged Don't modify existing Next hop address r14(config-route-map)#
It must be next-hop
The best option is to use containers https://docs.vyos.io/en/latest/contributing/build-vyos.html#build-container
Close it as out of date.
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2181
I don't see any errors in VyOS 1.3-stable-202308240442
vyos@r1# set firewall group network-group FW-OUT network '191.200.161.8/31' [edit] vyos@r1# set firewall group network-group FW-OUT network '191.200.161.8/32' [edit] vyos@r1# commit [edit] vyos@r1# delete firewall group [edit] vyos@r1# commit [edit] vyos@r1#
limitations of old backend
Fixed
[edit] vyos@r1# set policy route-map TEST rule 10 set metric -10 [edit] vyos@r1# commit [edit] vyos@r1# sudo vtysh -c "show run" Building configuration...
This task for the ldpd
https://vyos.dev/T4020
The smoketest was in the same PR https://github.com/vyos/vyos-1x/pull/2162/files#diff-59a88cf4e56c56db9de173bbdeb31600f9733d8598570831364d2d368402af77
Aug 27 2023
Aug 25 2023
PR f or 1.3.4 https://github.com/vyos/vyos-1x/pull/2168
@zsdc Can we backport it to 1.3?
Aug 24 2023
Will be fixed in https://vyos.dev/T5506
In my internal tests, it works even without listen-address
set container name c1 image 'docker.io/ealen/echo-server' set container name c1 network NET01 set container name c1 port web destination '80' set container name c1 port web source '8080' set container network NET01 prefix '10.0.0.0/24' set container network NET01 prefix '2001:db8:2222::/64' set interfaces dummy dum0 address '2001:db8:1111::1/64' set interfaces dummy dum0 address '203.0.113.1/32'
@Apachez, I got your point. The thing is, we don't have cisco-like CLI and can modify any seq rule.
It possibly could be from op-mode (not sure) because otherwise, you get resequence per each commit. That is definitely wrong.
If it is only per migration, you can change it in migration or rewrite the rules once.
The firewall will not be autoconfigured by bgpd or something else. We are not going to do it.
Aug 23 2023
It is not VyOS bug
I don't get this thing.
You can use any number that you want.
Could you explain what exactly Is wrong and why you can't use your own declared numbers?
Does it do what you want?
vyos@r14# set system frr snmp Possible completions: bgpd BGP isisd IS-IS ldpd LDP ospf6d OSPFv3 ospfd OSPFv2 ripd RIP zebra Zebra (IP routing manager)
For example
vyos@r14:~$ show conf com | match ldp set system frr snmp ldpd vyos@r14:~$ vyos@r14:~$ ps ax | grep ldp 1006 ? S<s 0:00 /usr/lib/frr/watchfrr -d -F traditional zebra mgmtd bgpd ripd ripngd ospfd ospf6d isisd babeld ldpd eigrpd staticd bfdd 1075 ? S< 0:00 /usr/lib/frr/ldpd -L -u frr -g frr 1076 ? S< 0:00 /usr/lib/frr/ldpd -E -u frr -g frr 1079 ? S<s 0:00 /usr/lib/frr/ldpd -d -F traditional --daemon -A 127.0.0.1 -M snmp 3124 pts/0
I don't get which exact issue with VRRP
but if you have an issue, please add a separate task.
Provide sudo nft list ruleset before and after the bug version. Bug with VRRP definitely not clear for now.
It seems that only one address could be set
--publish, -p=[[ip:][hostPort]:]containerPort[/protocol]
https://docs.podman.io/en/latest/markdown/podman-create.1.html#publish-p-port
Aug 22 2023
Aug 18 2023
The similar task https://vyos.dev/T4797