diff options
| author | Dimitri Staessens <dimitri@ouroboros.rocks> | 2025-08-04 22:01:59 +0200 |
|---|---|---|
| committer | Sander Vrijders <sander@ouroboros.rocks> | 2025-08-06 10:34:28 +0200 |
| commit | 2c077312b4f6236288da7df1caeb6cbaf6f83afd (patch) | |
| tree | 0b72a1dc049bbe94d0f2bdb650528607ffd483a8 /src/ipcpd/ipcp.h | |
| parent | 7933d742221fd44cc6eb0c82ff4a1a9795927de6 (diff) | |
| download | ouroboros-2c077312b4f6236288da7df1caeb6cbaf6f83afd.tar.gz ouroboros-2c077312b4f6236288da7df1caeb6cbaf6f83afd.zip | |
lib: Fix flow timeouts after flow allocation
There were two timeout bugs in the flow allocation steps.
Found these when debugging why some links were always timing out in
one direction.
The first bug only affects flows going through the connection manager
in the IPCP (such as the management flow used by the link state
routing component. The connection manager was setting a timeout on the
flow for its handling connection establishment, but didn't reset that
timeout before handing the flow to the internal component after the
CEP was complete. The link-state routing component was showing flow
read timeouts (ETIMEDOUT) without setting one. This was not causing
the links to time out.
The second one was that the IPCP was keeping the qosspec from on the
np1 flow, which, when the qosspec requested for the applicatoin had a
keepalive set, would always time out. This bug was the root cause for
some link advertisements not to be read and links to time out in the
link-state routing component.
Signed-off-by: Dimitri Staessens <dimitri@ouroboros.rocks>
Signed-off-by: Sander Vrijders <sander@ouroboros.rocks>
Diffstat (limited to 'src/ipcpd/ipcp.h')
0 files changed, 0 insertions, 0 deletions