Check if it exists in the kernel.
zcat /proc/config.gz | grep PARPORT
Check if it exists in the kernel.
zcat /proc/config.gz | grep PARPORT
@Apachez Thanks!
set system option keyboard-layout se-latin1
Verified in vyos-1.4-rolling-202307060317-amd64.iso but Im biased :-)
Just tried to upgrade from April image and its failed with this error :(
Right, i found in modules ArchLinux support it.
Implementation here:
https://github.com/vyos/vyos-1x/compare/current...jestabro:from-defaults
@cuongdt1994
I installed Arch linux, there is already a parport_pc in the kernel, the device is perfectly defined.
Why it doesn’t work here, I don’t understand, despite the fact that there is no parport module in lsmod
vyos@vyos:~$ show version Version: VyOS 1.4-rolling-202307051212 Release train: current
Hi @marekm - Hope you are well.
In talking with the vendor, this appears to be an incompatibility with the WiFi card and the coreboot BIOS installed on the device. Tested with a second device that had a different card installed, and no such errors are present now.
basic configuration :
Merged with current: https://github.com/vyos/vyos-1x/commit/8afdb5ad5515a0a1ae716204f397f3d974cec714
In preparing/testing a revised pull-request to fix a merge conflict, with version 1.4-rolling-202307050317, the testing commands need to be slightly modified.
Pull request created: https://github.com/vyos/vyos-1x/pull/2075
Actual file to modify for commit: https://github.com/vyos/vyos-1x/blob/current/interface-definitions/system-option.xml.in
@cuongdt1994 Thanks a lot, I'll definitely check it out.
Verified this particular request by modifying node.def and be able to select se-latin1.
Selectable keymaps are available in /usr/share/keymaps/i386/
Try and report, it's included in kernel:
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
Ok, I will try
@cuongdt1994
The kernel has assembled, as a result, the image now cannot be assembled
vyos-build/data/defaults.json change version 6.4.0
It can work if you use
Version: VyOS 1.4-rolling-202307040317
There are several layouts
se-fi-ir209 se-fi-lat6 se-ir209 se-lat6
Under normal operations the VyOS box looks like this for OSPF:
Added new commands and documentation
PR submitted for review:
In T5325#151572, @aztec102 wrote:@cuongdt1994 I did not build the kernel, I built the image and specified the modules in the file. Which you were talking about earlier.
I can update the documentation when the feature is implemented.
@cuongdt1994 I did not build the kernel, I built the image and specified the modules in the file. Which you were talking about earlier.
@daniil could you re-check?
set qos interface eth0 ingress '1G-in' set qos policy limiter 1G-in default bandwidth '1gbit' set qos policy limiter 1G-in default burst '125000000b'
Could you explain the use case?
Can you archive it with the class?
vyos@r14# set qos policy limiter test class video match 1 ip dscp Possible completions: <0-63> Differentiated Services Codepoint (DSCP) value default match DSCP (000000) reliability match DSCP (000001) throughput match DSCP (000010) lowdelay match DSCP (000100) priority match DSCP (001000) immediate match DSCP (010000) flash match DSCP (011000) flash-override match DSCP (100000) critical match DSCP (101000) internet match DSCP (110000) network match DSCP (111000) AF11 High-throughput data AF12 High-throughput data AF13 High-throughput data AF21 Low-latency data AF22 Low-latency data AF23 Low-latency data AF31 Multimedia streaming AF32 Multimedia streaming AF33 Multimedia streaming AF41 Multimedia conferencing AF42 Multimedia conferencing AF43 Multimedia conferencing CS1 Low-priority data CS2 OAM CS3 Broadcast video CS4 Real-time interactive CS5 Signaling CS6 Network control CS7 None EF Expedited Forwarding
@aztec102 Do you have build kernel again?
Good afternoon
Unfortunately it didn't help.
The policy route works only with an interface (inbound direction) and doesn't work otherwise.
It's always been like this.
In T5324#151418, @greenpsi wrote:I think I found the real problem:
The 62-temporary-interface-rename.rules udev rule runs in initramfs before the USB modem is detected:
Jun 30 14:32:11 vyos kernel: r8169 0000:03:00.0 e3: renamed from eth1 Jun 30 14:32:11 vyos kernel: r8169 0000:02:00.0 e2: renamed from eth0 [...] Jun 30 14:32:11 vyos kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd Jun 30 14:32:11 vyos kernel: ata2: SATA link down (SStatus 4 SControl 300) Jun 30 14:32:11 vyos kernel: ata1: SATA link down (SStatus 4 SControl 300) Jun 30 14:32:11 vyos kernel: usb 1-1: New USB device found, idVendor=12d1, idProduct=1f01, bcdDevice= 1.02 Jun 30 14:32:11 vyos kernel: usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0 Jun 30 14:32:11 vyos kernel: usb 1-1: Product: HUAWEI HiLink Jun 30 14:32:11 vyos kernel: usb 1-1: Manufacturer: HUAWEISo the modem does not get renamed to eX and thus, if the modem has an ethX name that conflicts with the configuration from the 65-vyos-net.rules udev rule, the renaming of the interfaces from eX to ethX fails because a duplicate already exists.
So in conclusion, if VyOS wants to support USB Ethernet devices, the 62-temporary-interface-rename.rules udev rule should be deferred until the USB devices are detected or something like that.
It did work in the test enviroment, I just returned from a long vacation and will be deploying that update to some production boxes and enabling it on there tomorrow.
VyOS 1.4-rolling-202306280317 show the following additional dmesg items
Tried the following:
echo 1 > /sys/bus/pci/devices/0000:03:00.0/remove
echo 1 > /sys/bus/pci/rescan
Attempted a modprobe -r ath10k_pci and the re-load the module. The following dmesg is what I saw after.
Yes, checked it working, please closed it.
@ServerForge Could you check if it works as expected?
If yes you can close it.
@cuongdt1994 Could you check it? If it works as expected, we can close it.
Requires to rewrite PIM to get_config_dict https://github.com/vyos/vyos-1x/blob/current/src/conf_mode/protocols_pim.py