This is addressed in a PR for T5319:
https://github.com/vyos/vyos-1x/pull/2131
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
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.
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.