On 1.3-beta-202102210443 and 1.4-rolling-202102202002 all work properly and don't require any changes, mark as resolved.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 23 2021
Feb 21 2021
I found a similar issue related to this topic in 1.2.6-S1, script on-dhcp-event.sh can't to determine pdns_recursor PID
vyos@vyos# ps ax | grep pdns 6626 ? Ssl 0:00 /usr/sbin/pdns_recursor --daemon=no --write-pid=no --disable-syslog --log-timestamp=no [edit] vyos@vyos# pgrep "pdns_recursor" [edit] vyos@vyos# pgrep pdns_recursor [edit] vyos@vyos#
We need to use pgrep pdns
vyos@vyos# pgrep pdns 6626 [edit]
Feb 19 2021
Feb 17 2021
SolarFlare modules present in the kernel for 1.3 and 1.4
vyos@vyos:~$ sudo modinfo sfc filename: /lib/modules/5.10.14-amd64-vyos/kernel/drivers/net/ethernet/sfc/sfc.ko license: GPL description: Solarflare network driver author: Solarflare Communications and Michael Brown <[email protected]> alias: pci:v00001924d00001B03sv*sd*bc*sc*i* alias: pci:v00001924d00000B03sv*sd*bc*sc*i* alias: pci:v00001924d00001A03sv*sd*bc*sc*i* alias: pci:v00001924d00000A03sv*sd*bc*sc*i* alias: pci:v00001924d00001923sv*sd*bc*sc*i* alias: pci:v00001924d00000923sv*sd*bc*sc*i* alias: pci:v00001924d00001903sv*sd*bc*sc*i* alias: pci:v00001924d00000903sv*sd*bc*sc*i* alias: pci:v00001924d00000813sv*sd*bc*sc*i* alias: pci:v00001924d00000803sv*sd*bc*sc*i* alias: pci:v000010EEd00001100sv*sd*bc*sc*i* alias: pci:v000010EEd00000100sv*sd*bc*sc*i* depends: mdio retpoline: Y intree: Y name: sfc vermagic: 5.10.14-amd64-vyos SMP mod_unload modversions parm: vf_max_tx_channels:Limit the number of TX channels VFs can use (uint) parm: max_vfs:Reduce the number of VFs initialized by the driver (int) parm: mcdi_logging_default:Enable MCDI logging on newly-probed functions (bool) parm: rx_refill_threshold:RX descriptor ring refill threshold (%) (uint) parm: irq_adapt_low_thresh:Threshold score for reducing IRQ moderation (uint) parm: irq_adapt_high_thresh:Threshold score for increasing IRQ moderation (uint) parm: interrupt_mode:Interrupt mode (0=>MSIX 1=>MSI 2=>legacy) (uint) parm: rss_cpus:Number of CPUs to use for Receive-Side Scaling (uint) parm: efx_separate_tx_channels:Use separate channels for TX and RX (bool) parm: phy_flash_cfg:Set PHYs into reflash mode initially (bool) parm: debug:Bitmapped debugging message enable value (uint)
Feb 16 2021
As a solution proposed to use TTL by default equivalent 16, but also add the possibility to change it via VyOS CLI
Feb 15 2021
Feb 12 2021
Feb 11 2021
Feb 9 2021
We need to change this and for CRUX
vyos@RTR1# run show version | match Version Version: VyOS 1.2.6-S1 [edit] # Log Feb 9 15:12:16 RTR1 ipsec_starter[2036]: # unknown keyword 'disableuniqreqids'
Feb 8 2021
@ajgnet which exactly version used in this case?
Feb 7 2021
Emergency recovery procedure:
grub> ls (hd0,msdos1)/boot/ #Figure out directory name, in this case, this is 1.4-rolling-202102040221
Feb 5 2021
PR https://github.com/vyos/vyos-1x/pull/722
Added sort command which provides some clarification on what the XML definition file will first in the list. It sorts by name.
So, in this case, the first XML file will be bcast-relay.xml
Feb 4 2021
Own build crux version from 13 Jan 2021 19:08 UTC - works properly
1.2.6-S1 - works properly
1.2.6 - affected (does not works)
1.4-rolling-202102040221 - works properly
1.3-beta-202102040443 - works properly
Jan 30 2021
I think we definitely need to try because this reproducible. @Viacheslav did you reproduce this on the ESXi hypervisor?
Jan 29 2021
Jan 28 2021
PR with smoketest check https://github.com/vyos/vyos-1x/pull/706
Jan 27 2021
Jan 26 2021
Tested on 1.4-rolling-202101240218, works as expected.
Jan 25 2021
@jack9603301 follow forum topic, all data randomized.
Jan 23 2021
Jan 15 2021
@GregGreg you describe definitely another issue that needs another topic. Will be better to discuss troubleshooting on the forum.
As for this topic, I pan to add some checks in the verify function.
Jan 11 2021
Jan 10 2021
Why not add this by default?
Jan 7 2021
Jan 6 2021
Jan 4 2021
@victorhooi try to build a stable version for yourself, on the stable version is defined by udev rules https://github.com/vyos/vyos-build/blob/crux/tools/vendors_udev/64-vyos-SAF51015I-net.rules
Or you can use way with binding hw-id as noticed @jack9603301 (but not mac)
Dec 31 2020
So we have configured option max-mtu this means
ppp-max-mtu=n Set the maximum MTU value that can be negotiated for PPP over L2TP sessions.
But I think we need to provide possibility set min-mtu
[ppp] min-mtu=n
Dec 30 2020
Dec 29 2020
Dec 24 2020
Does it possible to cherry-pick to 1.3? Because in 1.3 rollings we have the same bug.
Dec 23 2020
Successfully tested on 1.3-rolling-202012230217
Dec 22 2020
Dec 21 2020
Dec 17 2020
Dec 5 2020
successfully tested on the self-build image from crux branch and the latest rolling image
Dec 3 2020
Thanks, @c-po , works as expected.
vyos@vyos:~$ show lldp neighbors Capability Codes: R - Router, B - Bridge, W - Wlan r - Repeater, S - Station D - Docsis, T - Telephone, O - Other
Dec 2 2020
It seems related to this patch https://github.com/vyos/vyos-1x/commit/b39d623170377b2e99fd7e88b627afea71e4d00c#diff-e4557e4a7b41f0e9328ac0e7d7c0305416f0f1e42d46af27c2135ca976434fce
Appears only if you have 2 or more lldp neighbors.
Ok, with cisco device and added vif 1 I can reproduce this issue
vyos@vyos# run show lldp neighbors Traceback (most recent call last): File "/usr/libexec/vyos/op_mode/lldp_op.py", line 121, in <module> config_text = tmpl.render(parse_data(neighbors)) File "/usr/libexec/vyos/op_mode/lldp_op.py", line 50, in parse_data for local_if, values in data.items(): AttributeError: 'list' object has no attribute 'items'
I still can't reproduce this issue.
vyos@vyos:~$ show configuration commands | match lldp set service lldp interface eth1 set service lldp legacy-protocols cdp set service lldp management-address '192.168.255.31' set service lldp snmp enable vyos@vyos:~$ show lldp neighbors Capability Codes: R - Router, B - Bridge, W - Wlan r - Repeater, S - Station D - Docsis, T - Telephone, O - Other
@thadrumr please provide your lldp configuration. show configuration commands | match lldp
I can't reproduce this issue in lab with the latest rolling. Provide please detailed reproducing steps, also will be helpful to get an output
sudo lldpcli show neighbors