| Age | Commit message (Collapse) | Author |
|---|
|
|
|
PPPoE server supports setting the MPPE preferences, it is implemented as node
with leafNodes for require, prefer and deny. This will render a wrong AccelPPP
configuration as it will be "None" if specified.
pppoe-server {
ppp-options {
mppe {
deny
require
}
}
}
instead it must be:
pppoe-server {
ppp-options {
mppe require
}
}
|
|
T2826: frr: frr python lib error in replace_section
|
|
because of a bug in frr.py the default before_re will not be working.
it is by default without a group, but will be used in a match that needs a group.
The whole string could be matched in the group, so the fix is easy to implement.
|
|
... this reduces CPU load.
|
|
... required for smoketest and ConfigParser
|
|
|
|
|
|
This is faster implementation then using jmespath.search('foo.bar', dict).
|
|
|
|
Commit b082a6fb21 ("lcd: T2564: flatten CLI interface") by accident replaced
the template for hostapd which an LCD configuration during implementation of
T2564.
This has been corrected by restoring the content of the service configuration
from commit 8efb8ba1e (one commit earlier).
|
|
|
|
DHCPv6 client was not started as it used the old dict keys.
|
|
This reverts commit 5a5974d5a00b482cabd3dee92bc365d3c9f399bc.
Required for operational mode "show interfaces" command.
|
|
* 'dhcpv6-pd-cli-adjustment' of github.com:c-po/vyos-1x:
dhcpv6-pd: T2677: add support for rapid-commit option
dhcpv6-pd: T2821: support dhcpv6-pd without "address dhcpv6"
ifconfig: T2653: drop unused vyos.ifconfig.pppoe
dhcpv6-pd: T2677: optimize CLI interface for PD configuration
|
|
When rapid-commit is specified, dhcp6c will include a rapid-commit option in
solicit messages and wait for an immediate reply instead of advertisements.
|
|
Currently DHCPv6-PD requires an interface address configured to dhcpv6 on the
CLI. This is not required also sometimes there is either no dhcpv6 interface
addressing available (PPPoE) or wanted. This limitation was artificial due to
the old interface code.
Change the implementation to spawn the DHCPv6 client and request a prefix even
when there is no address request configured.
|
|
|
|
The current CLI did not support multiple prefix-delegations per interface. Some
ISPs only send one /64 to a client per prefix-delegation request, but they
allow the customer to request multiple prefixes.
The 'dhcpv6-options prefix-delegation' node has been renamed and converted to a
tag node named 'dhcpv6-options pd'. The tag node specifies a PD request (>=0).
In the past the user needed to know what prefix will be assigned and required
to calculate the sla-len by himself. The 'sla-len' node was dropped and is now
calculated in the background from the 'dhcpv6-options pd 0 length' node.
It is no longer mandatory to supply the 'sla-id' node, if sla-id is not
specified it is 'guessed' by counting upwards.
Example configuration:
----------------------
ethernet eth1 {
address dhcpv6
dhcpv6-options {
pd 0 {
length 56
interface eth2 {
address 1
}
}
}
}
This will request a /56 assignment from the ISP and will delegate a /64 network
to interface eth2. VyOS will use the interface address ::1 on the delegate
interface (eth2) as its local address.
|
|
|
|
|
|
VRRP: T2761: Extend "show vrrp" op-mode command with router priority
|
|
|
|
|
|
|
|
anyconnect: T2811: Return None if anyconnect not configured
|
|
mpls-ldp: T915: Add discovery hello timers
|
|
|
|
|
|
|
|
op-mode: T2791: Add monitor traceroute explicit for ipv4-ipv6 and vrf
|
|
|
|
|
|
|
|
|
|
DHCP service was not stopped when an DHCP address got removed from the
interface. DHCP service is now always stopped if it is not configured
explicitly.
|
|
* 'T2723' of https://github.com/jack9603301/vyos-1x:
tcptraceroute: T2723: Modify port description
tcptraceroute: T2723: Improve command line options, support execution without port
tcptraceroute: T2723: Support VRF
tcptraceroute: T2723: Fix the problem that tcptraceroute6 cannot be executed
|
|
vyos.template: T2720: Rework vyos.template Python library
|
|
|
|
When connected to VyOS by SSH through any VRF, every command is executed
in the VRF context thus e.g. ping will run in VRF context but no VRF was
defined on the CLI.
ping should always run in the default VRF no matter where it is executed,
unless a VRF instance is explicitly defined by CLI.
|
|
nat: T2764: increase maximum rule number to 999999
|
|
|
|
* 't2564-lcd' of github.com:c-po/vyos-1x:
lcd: T2564: flatten CLI interface
system display: T2564: Added test model
system display: T2564: Dictionary code update
system display: T2564: Conf files to /run
system display: T2564: Changed "duration" to "time"
system display: T2564: py code cleanup
system display: T2564: Replace "config (enabled|disabled)" with "display disabled"
system display: T2564: Lowercase model names
system display: T2564 Extend VyOS to support appliance LCDs
|
|
|
|
|
|
|
|
Add missing verify() check that at least one interface must be defined to
listen to PPPoE data.
|
|
* set system lcd device <device>
* set system lcd model <modeml>
Both device and model have completion helpers for supported interfaces and LCD
displays.
|
|
monitor-ndp:T2706: Modify the comment of `monitor ndp type`
|
|
dhclient: T2277: Hook for default route in vrf
|
