Kristof Provost
- Login: kprovost
- Registered on: 02/01/2021
- Last connection: 07/06/2024
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 2 | 87 | 89 |
| Reported issues | 5 | 1 | 6 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| pfSense | Developer, Reporter | 02/01/2021 |
| Bootstrap | Reporter | 02/01/2021 |
| pfSense Docs | Developer, Reporter | 02/01/2021 |
| pfSense Plus | Developer, Reporter | 02/01/2021 |
Activity
07/08/2024
-
02:53 PM pfSense Bug #15601: Routes with IPv6 Address as Next Hop for IPv4 Destination Causes Kernel Panic
- I've proposed this upstream: https://reviews.freebsd.org/D45913 and copied the original author of the relevant code.
-
- Jim Pingle wrote in #note-2:
> How exactly is someone making that sort of entry? It can't be made in the GUI via sta... -
- The relevant bits from the (private) crash dump is this:...
06/25/2024
-
- Okay, so the issue is believed to be associated with an increase in thread count. That's new information. It would be...
06/18/2024
-
- Craig Coonrad wrote in #note-34:
> dtrace submitted based on: https://redmine.pfsense.org/issues/15196#note-21
> HS...
06/17/2024
-
- `can't allocate llinfo` is logged by arpresolve_full(), when lltable_alloc_entry() returns NULL. lltable_alloc_entry(...
06/14/2024
-
- Are the users affected by `kernel: arpresolve: can't allocate llinfo` running a routing daemon (openbgpd, frr, ...)?
... -
- Was there a `kernel: arpresolve: can't allocate llinfo ` in HS# 2828658261?
What sort of connection issues is it see...
06/10/2024
-
- I believe I see what's happening.
When rules are re-loaded we explicitly copy the counter state from the previous ...
06/03/2024
-
- So the log in comment 23 has "kernel: arpresolve: can't allocate llinfo for 172.21.253.1 on ena1". So I'm wondering i...
Also available in: Atom