- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Thu, Nov 12
The change is up as a pull request and ready for review: https://github.com/vyos/vyos-1x/pull/5596
@najieb_haswell thanks, that is a thorough reproduction and it answers my open question: with PR #42 (which includes #44) the nat_pre_in2out_output crash is gone in your three cycles, so the earlier crash was most likely the accel-pppd/policer problem of T9502 and not the NAT44 output feature.
Can add as reference that OPNsense uses ZFS (and so does Proxmox, TrueNAS etc).
Reproduced here, and some data on the output-feature workaround, including the crash scenario from the description.
Wed, Nov 11
The task description above was truncated when I pasted it (the ends of long lines were cut off). I can't edit the description (edit policy), so here is the complete text. Please use this instead of the description.
The task description above was truncated when I pasted it (the ends of long lines were cut off). I can't edit the description (edit policy), so here is the complete text. Please use this instead of the description.
@hedrok Smallest case I have is two plain FRR routers, no VyOS. r2 (AS 65002) announces 10 prefixes to r1 (AS 65001); r1 has no soft-reconfiguration inbound, so each inbound policy change shows up as one ROUTE-REFRESH that r1 sends. Every change on r1 is made with frr-reload.py --reload <file>. Measured on FRR 10.5.2.
Thanks @najieb_haswell for the measurements, they answer the question about the NIC side.
Thanks @najieb_haswell for the measurements, they answer the question about the NIC side.
Some data from a VPP PPPoE BNG lab that may help here (VPP 26.10 with the VyOS PPPoE patches, accel-ppp-ng, BNG Blaster and TRex as testers, 10k-64k sessions, single- and double-tagged).
Tue, Nov 10
Has been implemented via https://vyos.dev/T9351
@a.kudientsov Could you provide sample FRR configs (before reload and after reload)? Or vyos commands for first and second commits? Thanks.
could we use systemd way to handle dependency and order ,as all the above are all systemd services .
another case for me is one container waiting for system mdns , if this service is not ready , all containers would failed ,and have to load manually .
Mon, Nov 9
I would prefer to have a startorder by default not depending on if the previous ones succeeded or not.