VyOS command definitions, scripts, and utilities (mirror of https://github.com/marekm72/vyos-1x.git) https://git.amelek.net/marekm72/vyos-1x.git/atom?h=1.3.1 2021-10-31T12:51:17+00:00 2021-10-31T12:51:17+00:00 Christian Poessinger christian@poessinger.com 2021-10-31T12:48:22+00:00 urn:sha1:60775392123a0253863ab7af5accd3b61285d84e We can no longer use bash veriable string code vor string manipulation. Move to a more robust "cut" implementation. (cherry picked from commit 513e951f3e1358ec6ff5424d03e8f4e9aa7c3388) 2021-06-13T14:41:04+00:00 Christian Poessinger christian@poessinger.com 2021-06-10T17:11:15+00:00 urn:sha1:c6ed4ff0191b9ebaab6d9d225a66eabf8411b60c (cherry picked from commit 011f8ede55311e08d42f5afed9a2e8c44fd6d301) 2021-03-18T16:55:09+00:00 Christian Poessinger christian@poessinger.com 2021-03-18T16:54:55+00:00 urn:sha1:13005fb6c2beb1e87200e31aadbbd62de4f33729 Turns out we still need it, else a MC7710 card won't work on an APU4 device. This reverts commit f9e0fb6bffd41c143ff5454c3b73cca4a588ca86. 2020-11-12T21:03:05+00:00 Christian Poessinger christian@poessinger.com 2020-11-12T21:03:05+00:00 urn:sha1:f9e0fb6bffd41c143ff5454c3b73cca4a588ca86 This is no longer required after commit for the VyOS Kernel configuration https://github.com/vyos/vyos-build/commit/3fa7fe6926a538a8b4f25 2020-06-07T09:55:14+00:00 Christian Poessinger christian@poessinger.com 2020-05-29T20:22:55+00:00 urn:sha1:1fc4aadb5d87643d6e64805b19a5a9e7671737ba During testing it was discovered that on 5 out of 10 reboots the USB enumeration/mapping from physical port to /dev/ttyUSB is different. The root cause is that it's a FIFO so first found/loaded driver module will be assigned ttyUSB0. This mixed up the serial interfaces of my FTDI chips and my connected Sierra Wireless MC7710 card which was no longer functioning as it now was mapped to a different USB interface. The solution is a udev rule which persistently maps the USB-tree-device to a device file in /dev. Wait? isn't this what /dev/serial/by-{id,path} is for? Correct, it does the very same thing but the problem is as follows: * by-path uses device file names which also incorporate the parent bus system, this results in "pci-0000:00:10.0-usb-0:2.4:1.0-port0" * by-id will overwrite the assigned device symlink if a new USB device with the same name appears. This happens to some FTDI devices with no serial number programmed so the device added last wins and will be the only one in the by-id folder - cruel world! This commit adds a new directory /dev/serial/by-bus which holds the following device files (as example): $ ls -1 /dev/serial/by-bus/ usb0b1.3p1.0 usb0b1.3p1.2 usb0b1.3p1.3 usb0b2.4p1.0 usb0b2.4p1.1 usb0b2.4p1.2 usb0b2.4p1.3 2020-03-28T19:48:32+00:00 Christian Poessinger christian@poessinger.com 2020-03-10T18:50:00+00:00 urn:sha1:ced45949bc282d23b0767f698f31b580602f0c9c