Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now that b40c52682a256 ("config: T2636: get_config_dict() returns a list on
multi node by default") is implemented the workarounds can be removed.
|
|
|
|
|
|
(https://github.com/Jacajack/mkjson.git)
|
|
|
|
Depending on the underlaying Kernel version load the corresponding Kernel
module.
|
|
rip: T2833: Fix distribute-list filter
|
|
|
|
|
|
|
|
|
|
|
|
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).
|
|
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.
|
|
|
|
|
|
anyconnect: T2811: Return None if anyconnect not configured
|
|
mpls-ldp: T915: Add discovery hello timers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
* '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.
|
|
|
|
|
|
t2564-lcd
* 'system-display' of https://github.com/fmertz/vyos-1x:
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
|
|
|
|
|
|
When running SSH from the VyOS system the source IP address can be set by:
set system options ssh-client source-address x.x.x.x
|
|
Problem was introduced in commit 740ace13 ("router-advert: T2609: add missing
verify() for prefix lifetime"). The 'infinity' literal was not converted to its
corresponding integer 0xffffffff (4294967295) for the check.
|
|
|
|
Commit 787879ba ("configure: op-mode: move XML here") migrated the op-mode
command "configure" to vyos-1x. The used shell snipped in turn sometimes
complained about: "_vyatta_op_do_key_bindings: command not found".
This is now resolved by moving the code entirely into the node.def file.
|
|
Move sshd_config file to /run so it must be generated on every boot and is
not stored accidently.
|
|
The problem exists when LLDP is not configured but one wants to run the detail
command. Running "show lldp neighbors" is not possible when LLDP is not running.
This case is already handled for "show lldp neighbors" and has been extended
for "show lldp neighbors detail".
|