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.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 2 2023
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.
The same bug was with ipoe-server https://vyos.dev/T5283
It is the actual address x.x.x.0 for UNIX devices and PPP interfaces, but it could be issue work Windows clients
There is a simple fix https://github.com/vyos/vyos-1x/commit/8a79769bf447cb18d456f061afd6a7997b8264f8
I'm sorry.
I tested this is VyOS 1.3.3.
I tested mutliple configurations, from subnet /23 all the way up to /32 with the command "set service pppoe-server client-ip-pool subnet <x.x.x.x/x>"
After setting the subnet i'd connect multiple clients to VyOS and check wether all the available IP addresses were used, and they were.
Which version?
Which tested config? Which generated config?
It would be more clear if you provided tangible examples.
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.