VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=c-po-patch-1 2024-11-20T16:33:48+00:00 2024-11-20T16:33:48+00:00 sarthurdev 965089+sarthurdev@users.noreply.github.com 2024-11-20T16:33:48+00:00 urn:sha1:f6ee516ca4409265b8b2b883c132357bf76655a3 2022-05-01T17:13:55+00:00 Christian Poessinger christian@poessinger.com 2022-05-01T17:13:55+00:00 urn:sha1:c621175631ab23b7218d1aef7ad0f46a46cb77bc 2020-06-09T19:00:39+00:00 Christian Poessinger christian@poessinger.com 2020-06-08T20:45:04+00:00 urn:sha1:bafa91b945ac77e2e1d000e356ca819bd5f87460 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.