Age | Commit message (Collapse) | Author |
|
generate wireguard mobile-config wg0 server wg.vyos.net address 1.2.2.2/24
WireGuard client configuration for interface: wg0
[Interface]
PrivateKey = AEXrZ4b3xFVLg1lql3hy/93+d43q3+3vPdSMUGI6/Fo=
Address = 1.2.2.2/24
[Peer]
PublicKey = h1HkYlSuHdJN6Qv4Hz4bBzjGg5WUty+U1L7DJsZy1iE=
Endpoint = wg.vyos.net:41751
AllowedIPs = 0.0.0.0/0, ::/0
The servers public key and port are automatically extracter from the running
config.
|
|
When deleting a route-map, prefix-list or access-list, we must ensure that
this routing policy is not referenced by any other protocol or policy.
When trying to remove a policy still in use, raise an error.
|
|
T3356: Add support for custom source address for connections
|
|
|
|
container: T2216: Rewrite op-mode to python
|
|
|
|
|
|
|
|
This commit is a cleanup and refinement of the container hosting implementation.
- Renamed CLI node ipv4-prefix -> prefix so both IPv4 and IPv6 prefix can be
supplied in the future. This is currently limited to IPv4 only as when using
IPv6 networks in combination with IPv4 the IPv4 prefix is altered randomly
- De-nested if clauses
- Use "for foo, bar in baz.items()" to more easily iterate of dictionary
values, this means "bar" can be used to access "baz[foo]"
|
|
|
|
|
|
dhclient: T3471: Fixed process search for IPv4
|
|
|
|
The previously used regex allowed an address value of "dhcpfoo" which is invalid
and will raise an OSError. Harden the regex that it explicitly must be dhcp or
dhcpv6.
|
|
Some software starts dhclient without IP protocol flag (`-4`, `-6`),
this commit adds the ability to find such processes as well as with a
protocol flag.
Additionally, to handle rare situations when PID file may not exists
(most likely, when multiple dhclient processes started with the same
PID file path), added last-resort action to kill such dhclients.
|
|
This reverts commit 619c518bfc904b060b5b59180940a804fe1beafd.
|
|
|
|
When rendering a dynamic routing protocol ensure the context, e.g. "router bgp"
or "router ospf" is proberly exited before applying any zebra route-map.
|
|
When we match on a community-list, extended community-list or even a large
community-list ensure that the referenced list exists on the CLI.
|
|
|
|
The following options one can specify in a route-map not got rendered as they
have been missed out:
* set comm-list
* set community
* set extcommunity (both route-target and site-of-origin)
* set table
|
|
* community-list gained proper valueHelp nodes
* route-map set community gained proper valueHelp nodes
* route-map set comm-list now has a completion helper searching in
"policy community-list"
|
|
|
|
|
|
get_config_dict()
|
|
|
|
|
|
* 't2425-policy' of github.com:c-po/vyos-1x:
policy: T2425: re-implement "policy" tree from vyatta-cfg-quagga in XML/Python
|
|
|
|
smoketest: T2216: Containers set ip to test01
|
|
|
|
|
|
|
|
T3472: Move over commit-confirm-notify.py from vyatta-config-mgmt
|
|
|
|
config: T3481: add switch to prevent mangling of tag node values
|
|
|
|
util: T3356: Fix password variables
|
|
containers: T2216: Static ip for conteiner smoketest
|
|
|
|
|
|
|
|
As all routing protocol definitions have been moved from the soon deprecated
vyatta-cfg-quagga package to vyos-1x, we also need to take care about all the
dependencies.
Add missing frr-rpki-rtrlib and frr-snmp dependency and enforce a FRR version
of at least 7.5 which holds all the features we currently support.
|
|
In the vyatta-cfg-quagga days the access-list(6) or prefix-list(6) sequence
numbers have been made up artifically. The new implementation from vyos-1x will
re-use the rule number specified on the CLI as the sequence number, this we have
to alter the tast cases to get a proper match from the beginning - covering
both the old and new world.
This can be done by using rule numbers that are multiples of 5.
|
|
containers: T2216: Add smoketest
|
|
|
|
In this commit we add more address families within
BGP. This should bring VyOS the ability to enable
the rest of the capabilities within FRR.
Co-authored-by: Cheeze_It <none@none.com>
|
|
dhclient: T3392: Changed dhclient-script hooks for VRF
|
|
There were two problems with VRF support inside dhclient-script:
- VRF check inside the `01-vyos-cleanup` hook was needless because it will be done inside the `03-vyos-ipwrapper` anyway;
- VRF was ignored for in-kernel routes in `03-vyos-ipwrapper`. Theoretically, there must be no situation now when this can leads to a real problem, but better will be to keep both kernel and FRR backends in sync.
Also, the way to get and use a VRF name was changed to an easier one.
|
|
|