Age | Commit message (Collapse) | Author |
|
|
|
vti: T2576: show interfaces missed VTI
|
|
|
|
|
|
The "to" qualifier did not get rendered when using source ports in masquerade
targets. This case was totally missed out when porting.
|
|
|
|
|
|
List all processes running in given VRF
vyos@vyos:~$ show vrf black processes
4624 sshd
4404 ntpd
|
|
|
|
|
|
Only IP prefixes are allowed to be added by the CLI thus we can drop the
same check inside the Python script to validate the prefix.
|
|
|
|
Commit 5deb12c509be ("ssh: T2321: add VRF support") restructured the Port
assignment (cleanup from the early days) but it accesses a string with methods
used for a list, resulting in the funny default port 2.
|
|
We specify NFT source/destination ports within a { } group, but if the port
range in question is negated, we need to move the != fraction out of { } and
infront of that group, else NFT loading will fail big time.
|
|
This reverts commit 927c054d9236c2c34ca43c1cbfff10fcfd7f5077.
|
|
After commit 1c7d7cb ("wwan: T2529: migrate device from ttyUSB to
usbXbY.YpZ.Z") the up/down scripts did not properly parse the passed tty
for setting up default routes.
|
|
|
|
|
|
|
|
tested using:
set nat destination rule 399 description 'Redirect DNS iot VLAN'
set nat destination rule 399 destination address '!192.168.67.243-192.168.67.244'
set nat destination rule 399 destination port '53'
set nat destination rule 399 inbound-interface bond10.204
set nat destination rule 399 log
set nat destination rule 399 protocol 'tcp_udp'
set nat destination rule 399 translation address '192.168.67.243'
set nat destination rule 399 translation port '53'
set nat destination rule 400 description 'Redirect DNS lan VLAN'
set nat destination rule 400 destination address '!192.168.67.243-192.168.67.244'
set nat destination rule 400 destination port '53'
set nat destination rule 400 inbound-interface bond10.204
set nat destination rule 400 log
set nat destination rule 400 protocol 'tcp_udp'
set nat destination rule 400 translation address '192.168.67.243'
set nat destination rule 400 translation port '53'
set nat destination rule 401 description 'Redirect DNS guest VLAN'
set nat destination rule 401 destination address '!192.168.67.243-192.168.67.244'
set nat destination rule 401 destination port '53'
set nat destination rule 401 inbound-interface bond10.204
set nat destination rule 401 log
set nat destination rule 401 protocol 'tcp_udp'
set nat destination rule 401 translation address '192.168.67.243'
set nat destination rule 401 translation port '53'
|
|
|
|
|
|
|
|
* 'serial-console' of github.com:c-po/vyos-1x:
console: T2569: run VGA console powersave on tty1
console: T2569: replicate console settings to grub.cfg
Debian: fix warning about undefined substitution variables
console: T2569: only start serial console if device exists
console: T2529: migrate from ttyUSB device to new device in /dev/serial/by-bus
console: T2570: remove support for Hayes Modems
netconsole: T2561: use migrator to delete config nodes
console: T2569: initial implementation with XML and Python
|
|
|
|
|
|
warning: Depends field of package vyos-1x: substitution variable
${shlibs:Depends} used, but is not defined
warning: Depends field of package vyos-1x-vmware: substitution variable
${shlibs:Depends} used, but is not defined
Remove variables from dependency list as we have explicit non architecture
dependend dependencies.
|
|
BFD: T2573: Fixed show command for BFD peers
|
|
As vtysh does not have a vrf option for "show bfd peer" command, the vrf part will be cut before passing a line to the vtysh.
|
|
1xppp09062020
|
|
|
|
|
|
Only start console if it exists on the running system. If a user detaches a
USB serial console and reboots - it should not fail!
|
|
During testing it was discovered that there is a well known problem (we had for
ethernet interfaces) also in the serial port world. They will be enumerated and
mapped to /dev/ttyUSBxxx differently from boot to boot. This is especially
painful on my development APU4 board which also has a Sierra Wireless MC7710
LTE module installed.
The serial port will toggle between ttyUSB2 and ttyUSB5 depending on the
amount of serial port extenders attached (FT4232H).
The shipped udev rule (/usr/lib/udev/rules.d/60-serial.rules) partly solves
this by enumerating the devices into /dev/serial/by-id folder with their name
and serial number - it's a very good idea but I've found that not all of the
FT4232H dongles have a serial number programmed - this leads to the situation
that when you plug in two cables with both having serial number 0 - only one
device symlink will appear - the previous one is always overwritten by the
latter one.
Derive /usr/lib/udev/rules.d/60-serial.rules and create a /dev/serial/by-bus
directory and group devices by attached USB root port.
|
|
Support for Hayes modems has been long gone (1.2.x) and nobody cared. It was
removed in commit d582bbaf3 ("update console settings for systemd") of
vyatta-cfg-system.
So as there have been zero complaints - cleanup the CLI.
|
|
The current implementation only works once the system has been fully booted
up and the config nodes have been process. So there is no "early" kernel
debugging. It is started with priority 400 (after all network stuff) - thus it
has a questionable at all for Kernel debugging.
It would only make sense if the entire system is changed to supply the config
stuff to the Kernel commandline and then send it to a dedicated MAC address
target as network will be initialized late.
As there are zero Phabricator tasks available and we do not know any user using
this - the "feature" will be removed.
|
|
Migrate the serial console subsystem to XML and Python.
|
|
|
|
T2559: Make the sensors automatically load necessary modules
|
|
|
|
l2tp: T2565: Add missing gw-ip-address
|
|
|
|
|
|
Instead of using "show version" as catch-all command for information rather
add "show system cpu" op-mode command which is analogous to "show system memory"
which deals with RAM.
|
|
|
|
Commit 1c7d7cbd39 ("wwan: T2529: migrate device from ttyUSB to usbXbY.YpZ.Z")
added a new completion helper path for USB based serial interfaces. If no USB
based serial port was available on the system this produced the following
error: "ls: cannot access '/dev/serial/by-bus': No such file or directory"
Only list USB based serial interfaces if there is at least one connected to
the system.
|
|
Commit 886a986a122e ("isis: T2495: exclude generated nodes from package") missed
calling rm -rf, instead only rm -f was called leaving the directory intact.
|
|
* 'udev' of github.com:c-po/vyos-1x:
usb: op-mode: T2560: display USB interface information
pppoe: op-mode: T2488: retrieve log info from journalctl
wwan: op-mode: T2488: retrieve log info from journalctl
wwan: T2241: interface is not bond- or bridgeable
wwan: T2488: remove generation of dedicated logfile
wwan: T2529: migrate device from ttyUSB to usbXbY.YpZ.Z
udev: T2490: add persistent USB device files
|
|
|
|
vyos@vyos:~$ show system usb
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 4, If 0, Class=Vendor Specific Class, Driver=qcserial, 480M
|__ Port 3: Dev 4, If 2, Class=Vendor Specific Class, Driver=qcserial, 480M
|__ Port 3: Dev 4, If 3, Class=Vendor Specific Class, Driver=qcserial, 480M
|__ Port 3: Dev 4, If 8, Class=Vendor Specific Class, Driver=qmi_wwan, 480M
vyos@vyos:~$ show system usb serial
No USB to serial converter connected
vyos@vyos:~$ show system usb serial
Device Model Vendor
------ ------ ------
usb0b1.3.3.4p1.0 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.3.3.4p1.1 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.3.3.4p1.2 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.3.3.4p1.3 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.3.4p1.0 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.3.4p1.1 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.3.4p1.2 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.3.4p1.3 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.3p1.0 MC7710 Sierra Wireless, Inc.
usb0b1.3p1.2 MC7710 Sierra Wireless, Inc.
usb0b1.3p1.3 MC7710 Sierra Wireless, Inc.
usb0b1.4p1.0 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.4p1.1 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.4p1.2 Quad_RS232-HS Future Technology Devices International, Ltd
usb0b1.4p1.3 Quad_RS232-HS Future Technology Devices International, Ltd
|