This is addressed in a PR for T5319:
https://github.com/vyos/vyos-1x/pull/2131
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 2 2023
cool! it's interesting understand this complex scenery and how it works an real environment ,Additionally, the way it handle the zebra with the next-hop group ,int fact , I genuinely appreciate your valuable feedback so far!
From last night tests it seems to be solved. Though i'd prefer to test the node in production for a few weeks to be sure.
as I recall ,this case can be associate with this task : https://vyos.dev/T5077
@twan Can we close it?
Yesterday I tested the latest 1.4-rolling-202308011218-image which includes CONFIG_VIRTIO_FS=m, and was successfully able to (manually) activate LXD Agent in my VM.
Thank you for the quick fix.
Aug 1 2023
Done!
yes , sorry!
Cherry-pick https://github.com/vyos/vyos-1x/pull/2125
@fernando Can we close it?
We are against "raw" options. As it is a bad design.
Specify which exactly options you want to configure. It is better to implement them separately.
@troggie Could you confirm that you expect "0"
Regarding documentation, it should be "-1" https://github.com/accel-ppp/accel-ppp-docs/blob/master/configuration/pppoe.rst
Could you close the task if the issue is solved?
Jul 31 2023
@a.apostoliuk found that actually this is silently discarded in the Kernel - so a proper error message is a good addition here.
Jul 30 2023
Just to sync this task to PR 2118:
As mentioned in https://vyos.dev/T5419 the offloading should not only apply for NAT.
Duplicate of the task https://vyos.dev/T4502
And there also a PR https://github.com/vyos/vyos-1x/pull/2062
It is waiting for merging firewall refactoring
Jul 29 2023
This particular case was resolved by adding:
For "show dhcp client" command https://github.com/vyos/vyos-1x/pull/2120
I added this comment to PR 2118:
A not too uncommon workaround for this is to disable the lease-file (if possible) and give out leases based on option82 information instead.
Is this a limit of wireguard?
I'm using the *-parameters in isc-dhcp to manage ddns updates to an external nameserver. This way dns-entries supplied by dhcp-server will be kept in sync, even when using dhcp-failover.
I would love to still be able to keep this functionality with Kea in some way. Either by providing corresponding custom-parameters, or adding native support for this scenario.
Jul 28 2023
I have submitted PR 2118 for this issue.
You skip this warning and delte version number line
// Warning: Do not remove the following line // vyos-config-version: "bgp@4:broadcast-relay@1:cluster@1:config-management@1:conntrack@3:conntrack-sync@2:container@1:dhcp-relay@2:dhcp-server@6:dhcpv6-server@1:dns-dynamic@1:dns-forwarding@4:firewall@10:flow-accounting@1:https@4:ids@1:interfaces@29:ipoe-server@1:ipsec@12:isis@3:l2tp@4:lldp@1:mdns@1:monitoring@1:nat@5:nat66@1:ntp@2:openconnect@2:ospf@2:policy@5:pppoe-server@6:pptp@2:qos@2:quagga@11:rip@1:rpki@1:salt@1:snmp@3:ssh@2:sstp@4:system@26:vrf@3:vrrp@4:vyos-accel-ppp@2:wanloadbalance@3:webproxy@2" // Release version: 1.4-rolling-202307090317
I've recently migrated from a PCEngines APU2C4 to a Wyse 5070 with a X520 card, as well as upgrading to VyOS 1.4-rolling-202305081003
After which I was unable to reproduce this issue. Roaming now works fine without the ICMP check.