Skip to content

DSDV: implement paper extensions and base-station routes - #1455

Open
mgonzalezlopezudc wants to merge 20 commits into
inet-framework:masterfrom
mgonzalezlopezudc:feat/dsdv-paper-extensions
Open

mgonzalezlopezudc wants to merge 20 commits into
inet-framework:masterfrom
mgonzalezlopezudc:feat/dsdv-paper-extensions

Conversation

@mgonzalezlopezudc

@mgonzalezlopezudc mgonzalezlopezudc commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

The UDP-based DSDV model in #1444 can leave sequence updates waiting behind lower addresses, wait for a timeout after a failed delivery, and send full tables at a fixed rate. This extends it with fair selection, optional MAC failure feedback and optional adaptive updates, plus external-network access through one configured base station.

Dependency: #1444 is still pending. This PR includes its prerequisite implementation, including the incompatible migration from legacy Hello packets to IPv4/UDP and historical fingerprint changes. The prerequisite corrections are included in #1444. feat/dsdv-routing and its PR branch end at ab395478ab, which is a direct ancestor of this branch. See the migration guide and evidence. The extension starts after ab395478ab.

Small updates keep urgent changes first and rotate less urgent entries when space runs out. MAC feedback withdraws routes through the failed receiver. Adaptive timing sends full tables less often in quiet periods, within configured limits. The base station advertises whether its wired uplink is available, so mobiles can add or remove their default route.

flowchart LR
    M[Mobile] <-->|Wireless| R[Relay]
    R <-->|Wireless| B[Base station]
    B <-->|Wired uplink| W[Wired router]
    W <--> E[External host]
Loading

MAC feedback, adaptive timing and base-station support start disabled. The extension retains #1444's version-1 format for ordinary networks. Base-station networks require version 2 and the same base-station identity on every participant, plus a wired return route. Uplink availability means a usable local route, not a probe of Internet health.

The short plan explains the four extensions.

Extension commits

Commit Contribution and direct check
ad874294ff Records the design, boundaries and verification plan before implementation.
e8a93caab1 Rotates optional sequence updates after required entries when space is scarce, retaining address order when all fit. DsdvIncrementalFairness supplies three pending destinations with one spare slot: the parent repeats the first, while this commit delivers all three. The identical parent fixture fails its rotation assertion.
3b9cbc0c5b Consumes failed-receiver hints without invalidating routes that switched successors. DsdvMacFailure breaks a real delivery: the parent retains the route at the early-removal assertion, while this commit withdraws it. Only unavailable new INI assignments are omitted on the parent. The feature also passes timeout-only and ad hoc DCF controls; the parent run stops in the first Acking MAC group.
2084ba7a30 Bounds full-dump timing using route changes and actual packet cost. DsdvAdaptiveDumps observes a quiet receiver: the parent keeps 1 s spacing and fails the required 2 s spacing, while this commit passes. Only new adaptive INI assignments are omitted on the parent. Churn, payload, urgent-withdrawal and heterogeneous-peer cases add coverage.
e81556809f Advertises sequenced base-station capability and derives an owned IPv4 default. DsdvBaseStation checks real forwarding along the diagram, capability loss/recovery, stale input, foreign defaults and controller restart. The parent cannot run this new wire/interface profile unchanged, so no measured parent forwarding failure is claimed.
b253aa6266 Records final validation, exact-parent comparisons and evidence limits without changing protocol behavior.
109e6b3946 Archives the completed plan and summary in plan/done without changing their contents.
eef1c8279f Updates the execution record to link to the archived plan.
Prerequisite implementation from #1444, in review order
Commit Contribution
adf3200c1e Establishes independent route and wire state, selection, graph checks and serialization.
68e8cf2dba Connects the routing state to UDP control messages and IPv4 host forwarding.
0e2fd14fe1 Checks expiry, stop and restart behavior through kernel/lifecycle tests.
5366d99931 Checks dissemination deadlines, payload submission and paper examples.
e0b555b029 Demonstrates partition and rejoin recovery in a mobile example.
9e09556f65 Archives the completed base implementation plan.
79b245e590 Aligns MANET documentation and control visualization with UDP DSDV.
8e7a09d983 Refreshes routes more frequently in the MANET showcase.
d56b3a6d00 Exposes route and scheduling state to inspectors.
238b176049 Applies a minimum settling delay to deferred advertisements.
d0beed9276 Removes obsolete Hello support and uses the current serializer.
ab395478ab Explains test scenarios and topologies for reviewers.

Validation and scope

Fresh debug and release builds pass. All 18 focused debug cases pass: 4 unit, 8 module and 6 protocol cases. Four module cases deliberately reject invalid configuration and pass only when the expected diagnostic and exit code match. Deterministic protocol cases use run/seed 0.

All 13 selected stored fingerprints match across five DSDV configurations (tplx, ~tNl, ~tND, run 0). Existing visual fingerprints were not rerun. The extension commits do not update baselines.

An isolated debug build also passes with only IPv4/UDP enabled and DSDV disabled, with no DSDV objects or dynamic symbols. This checks the minimal disabled profile, not every feature combination.

The execution record contains commands, exact parent comparisons and evidence limits. The four new protocol scenarios are explained in fairness, MAC failure, adaptive dumps and base station. These checks do not establish a performance improvement, whole Ethernet-node reboot support or arbitrary-loss correctness.

Routing decisions remain in DsdvTable; Dsdv handles packets, timers and IPv4 routes. The extension changes DSDV, its tests, feature-test dependencies and documentation. It changes no MAC/IPv4 core algorithm, sealed source or fingerprint baseline.

Scoped architecture, naming, links and series checks pass. Repository-wide architecture, naming and interface gates report existing findings outside the changed paths; the global link gate also lacks external standards files. These limits are disclosed in the execution record.


Devin Review

Establish Perkins/Bhagwat route selection and a finite-run UDP wire profile before attaching a routing module. Keep forwarding, advertised state and full-dump comparisons under one owner, with independent byte and graph oracles.

This foundation introduces a single route tuple contract with the table operations and byte encoding used by the later UDP controller. Keeping tuple declarations, invariant checks and encoding oracles together makes that contract reviewable before production attachment; no module changes forwarding behavior in this step.

Plan: plan/pending/dsdv-from-scratch.md

Change: src.routing.dsdv | behavior.add | test whatsnew | dsdv-from-scratch
Attach the independent state owner through the UDP dispatcher and publish owned IPv4 host routes immediately. Preserve sequence floors across suspension and construct every advertisement synchronously from eligible state. Migrate node and showcase attachment to the socket contract.

The controlled four-node line verifies owned next hops, both intermediate ingress paths and echo replies; its otherwise identical disabled line has no remote route and receives no replies. The pair and disconnected fixtures bound basic convergence claims.

The module/socket contract, its NED attachment and every node caller must switch from Hello to UDP together; retaining either half would leave production nodes wired to the removed controller contract. DsdvForwarding.md beside its protocol fixture explains the controlled topology, assertions and limits in this same commit.

Plan: plan/pending/dsdv-from-scratch.md

Allow simultaneous startup transmissions in the legacy example so immediate startup dumps undergo the radio collision model rather than aborting on the diagnostic check.

Nonvisual fingerprint updates on the upstream base, debug mode, run/seed 0. Visual expectations are unchanged:
- examples/manetrouting/dsdv, omnetpp.ini, DynamicIPv4, run 0, 22s, tplx: b5fe-a1b2 -> 028c-95ee. The UDP controller replaces Hello forwarding with full/incremental dissemination and expiry, changing event times and packet trajectories.
- examples/manetrouting/dsdv, omnetpp.ini, IPv4, run 0, 10s, tplx: 2d1b-0515 -> fe44-d006. The UDP controller replaces Hello forwarding with full/incremental dissemination and expiry, changing event times and packet trajectories.
- examples/manetrouting/dsdv, omnetpp.ini, MultiIPv4, run 0, 10s, tplx: a35f-3c51 -> 9d2b-c13d. The UDP controller replaces Hello forwarding with full/incremental dissemination and expiry, changing event times and packet trajectories.
- showcases/routing/manet, omnetpp.ini, Dsdv, run 0, 100s, tplx: 84f0-9aea -> c75a-49fb. The UDP controller replaces Hello forwarding with full/incremental dissemination and expiry, changing event times and packet trajectories.
- examples/manetrouting/dsdv, omnetpp.ini, DynamicIPv4, run 0, 22s, ~tNl: 3e2c-1eee -> 4551-50ce. UDP/IP route-entry advertisements replace Hello messages, changing the selected inter-node timing and length stream.
- examples/manetrouting/dsdv, omnetpp.ini, IPv4, run 0, 10s, ~tNl: 1ba1-8398 -> 052c-d3e9. UDP/IP route-entry advertisements replace Hello messages, changing the selected inter-node timing and length stream.
- examples/manetrouting/dsdv, omnetpp.ini, MultiIPv4, run 0, 10s, ~tNl: 9f80-f16d -> be75-f184. UDP/IP route-entry advertisements replace Hello messages, changing the selected inter-node timing and length stream.
- showcases/routing/manet, omnetpp.ini, Dsdv, run 0, 100s, ~tNl: bdad-9a28 -> 00fb-77c9. UDP/IP route-entry advertisements replace Hello messages, changing the selected inter-node timing and length stream.
- examples/manetrouting/dsdv, omnetpp.ini, DynamicIPv4, run 0, 22s, ~tND: 0af5-5bc7 -> 42a9-af97. The versioned UDP header and route entries replace Hello wire fields, changing selected packet bytes and timestamps.
- examples/manetrouting/dsdv, omnetpp.ini, IPv4, run 0, 10s, ~tND: bed0-9954 -> 6975-ddb0. The versioned UDP header and route entries replace Hello wire fields, changing selected packet bytes and timestamps.
- examples/manetrouting/dsdv, omnetpp.ini, MultiIPv4, run 0, 10s, ~tND: 92cb-62b4 -> a9c7-4579. The versioned UDP header and route entries replace Hello wire fields, changing selected packet bytes and timestamps.
- showcases/routing/manet, omnetpp.ini, Dsdv, run 0, 100s, ~tND: fefe-9ffb -> bda7-8bee. The versioned UDP header and route entries replace Hello wire fields, changing selected packet bytes and timestamps.

Measured parent values distinguish inherited baseline drift from the controller transition. Packet fingerprints also include time; their movement alone does not prove a length or byte change.

Change: src.routing.dsdv | behavior.change | test whatsnew migration fingerprint | dsdv-from-scratch
Exercise timestamp ties, independent destination freshness, interface recovery and real node lifecycle operations through the production routing module. Check retained floors, withdrawal repetition, timer cancellation and foreign-route ownership without using the legacy model as an oracle.

Plan: plan/pending/dsdv-from-scratch.md

Change: tests.module | behavior.add | - | dsdv-from-scratch
Use controlled production callbacks and real kernel timers to distinguish forwarding state from full-dump advertisements. Verify immediate corrections, non-sliding deadlines, atomic rejection and bounded synchronous overflow submission. Reconstruct the original paper tables as an independent algorithm oracle.

Plan: plan/pending/dsdv-from-scratch.md

Change: tests | behavior.add | - | dsdv-from-scratch
Supply a deterministic mobile line with static addresses, local ARP and no bypass routes, plus a production-path delivery-window check. Record the new example fingerprint only after independent forwarding, graph, lifecycle, timer and encoding checks pass.

The full and isolated-feature campaigns bound the documented IPv4 profile. Preserve existing trajectory baselines and report unrelated global gate findings and missing tools explicitly.

The beside-test reviewer document tests/protocol/dsdv/DsdvMobile.md describes the moving-relay input, delivery-window assertions and their limits in this same behavior commit.

Plan: plan/pending/dsdv-from-scratch.md

Nonvisual fingerprint updates on the upstream base, debug mode, run/seed 0. Visual expectations are unchanged:
- examples/dsdv, omnetpp.ini, Mobile, run 0, 32s, tplx: new -> 2bf5-fcd0. The new Mobile example records the event trajectory through partition and rejoin; its protocol test checks delivery before, during and after that partition.

Change: examples.dsdv | behavior.add | - | dsdv-from-scratch
Change: plan | location | - | dsdv-from-scratch
Select DSDV control packets in the green visualizer and replace obsolete hello-only documentation and parameter includes. Identify the existing videos as historical recordings.

Keep the nonvisual expectations with the UDP-controller migration that causes their changes. The visualization filter does not change these fingerprints. Preserve the visual expectation and record its separate validation limits explicitly.

Change: examples.routing.manet | behavior.change.fix | -
The moving relays in the MANET showcase can outpace route updates with the existing 1s dump interval and default 500ms jitter. Use a 250ms interval with at most 50ms jitter to disseminate fresh routes more frequently.

Nonvisual fingerprint updates on the upstream base, debug mode, run/seed 0. Visual expectations are unchanged:
- showcases/routing/manet, omnetpp.ini, Dsdv, run 0, 100s, tplx: c75a-49fb -> 3f89-3651. The MANET full-dump interval changes from 1s to 250ms and jitter from 500ms to 50ms, changing advertisement times and sequence progression.
- showcases/routing/manet, omnetpp.ini, Dsdv, run 0, 100s, ~tNl: 00fb-77c9 -> 519f-5d99. The MANET full-dump interval changes from 1s to 250ms and jitter from 500ms to 50ms, changing advertisement times and sequence progression.
- showcases/routing/manet, omnetpp.ini, Dsdv, run 0, 100s, ~tND: bda7-8bee -> 272c-55b9. The MANET full-dump interval changes from 1s to 250ms and jitter from 500ms to 50ms, changing advertisement times and sequence progression.

Change: examples.routing.manet | behavior.change | fingerprint
DSDV inspection currently hides the freshness, settling and advertisement state needed to explain route choices. Register watches for the controller, route records, neighbors, full-dump baseline, pending destinations and timer deadlines. Provide read-only table accessors and record formatting so inspectors can display that state without changing routing decisions.

Change: src.routing.dsdv | refactor | -
Repeated destination sequences without metric improvements drive the adaptive settling estimate toward zero, so a later route change can receive a picosecond-scale holdoff. Add a configurable minSettlingDelay, defaulting to 10ms, to bound new deferred advertisement deadlines while preserving the settling cap, existing deadlines and immediate urgent updates. Reject nonpositive minima and minima above the cap.

Extend the dissemination test with a zero-estimate history, minimum/cap boundaries, advertised-view preservation and urgent withdrawal. Document the new parameter, migration requirements and changed simulation trajectories.

Nonvisual fingerprint updates on the upstream base, debug mode, run/seed 0. Visual expectations are unchanged:
- examples/manetrouting/dsdv, omnetpp.ini, DynamicIPv4, run 0, 22s, tplx: 028c-95ee -> ea2a-cd36. The 10ms floor postpones new deferred deadlines and changes advertisement timing and coalescing. Urgent advertisements and existing deadlines retain their rules.
- showcases/routing/manet, omnetpp.ini, Dsdv, run 0, 100s, tplx: 3f89-3651 -> e7a2-1b3d. The 10ms floor postpones new deferred deadlines and changes advertisement timing and coalescing. Urgent advertisements and existing deadlines retain their rules.
- examples/manetrouting/dsdv, omnetpp.ini, DynamicIPv4, run 0, 22s, ~tNl: 4551-50ce -> ec39-cd04. The 10ms floor postpones new deferred deadlines and changes advertisement timing and coalescing. Urgent advertisements and existing deadlines retain their rules.
- showcases/routing/manet, omnetpp.ini, Dsdv, run 0, 100s, ~tNl: 519f-5d99 -> 7c88-78ac. The 10ms floor postpones new deferred deadlines and changes advertisement timing and coalescing. Urgent advertisements and existing deadlines retain their rules.
- examples/manetrouting/dsdv, omnetpp.ini, DynamicIPv4, run 0, 22s, ~tND: 42a9-af97 -> 9cfd-b9e8. The 10ms floor postpones new deferred deadlines and changes advertisement timing and coalescing. Urgent advertisements and existing deadlines retain their rules.
- showcases/routing/manet, omnetpp.ini, Dsdv, run 0, 100s, ~tND: 272c-55b9 -> 3b16-c25e. The 10ms floor postpones new deferred deadlines and changes advertisement timing and coalescing. Urgent advertisements and existing deadlines retain their rules.

Change: src.routing.dsdv | behavior.change | test whatsnew migration fingerprint
The UDP DSDV implementation uses DsdvHeader, but the old DsdvHello message and serializer still remain in the source tree. Remove these unused artifacts and their serializer-test fillers, exclusion entry and coverage note so the test library no longer depends on the retired packet type.

Update the migration guide to state that the old classes have been removed and direct custom code and tooling to DsdvHeader and DsdvHeaderSerializer.

Change: src.routing.dsdv | behavior.remove | migration
The DSDV check list is too terse to explain the fixtures without reading their test sources. Expand it with topology diagrams, controlled inputs, timelines, expected observations and coverage limits for all eight correctness tests.

Add a central index and a README beside the tests so reviewers can find the forwarding and mobile-recovery explanations already delivered with their behavior commits. This changes documentation only.

Change: doc | comment | -
Record the approved four-feature implementation scope, companion human summary and execution ledger. Preserve the existing DSDV topic and unrelated working-tree changes.

Change: plan | behavior.add | -
Small incremental updates can repeatedly select the lowest-address sequence-only destination while higher addresses wait for a full dump. Keep one address cursor in DsdvTable so spare slots rotate through optional entries. When all optional entries fit, their destination order stays unchanged. Required changes retain priority, zero spare capacity consumes no turn, and full dumps or session resets clear the cursor without changing send scheduling.

DsdvIncrementalFairness supplies three same-metric sequence changes and successive corrective send opportunities over real UDP/radio links. It observes destinations 4, 5 and 6 in turn, required-only capacity and full-dump reset. The parent traverses optional entries from the beginning on every send, so the same rotation assertion is expected to fail there; this parent comparison is source-based, not executed. DsdvDissemination checks candidate removal, wraparound and uniqueness.

Plan: plan/pending/dsdv-paper-extensions.md

Change: src.routing.dsdv | behavior.change.fix | test whatsnew
A unicast MAC delivery failure can leave DSDV routes installed until their timeout. Add optional consumption of existing linkBroken notifications, identify the transmitted receiver through retained packet metadata and local ARP, and urgently withdraw every route whose current successor is that neighbor. Reuse the table transition for expiry while preserving its return order. Disabled feedback resolves no ARP dependency and retains timeout behavior.

DsdvMacFailure separates AckingMac feedback-on/off lines and an ad hoc DCF feedback-on line. After a next hop leaves range, the same early-withdrawal and received odd-sequence assertions distinguish feedback from the timeout control. The parent does not consume the MAC hint and is expected to miss that early deadline; the exact-parent comparison is not yet executed. Module checks additionally cover unusable hints, switched successors, repeated notifications and restart. The disabled line deliberately names a missing ARP module to exercise conditional dependency resolution.

Plan: plan/pending/dsdv-paper-extensions.md

Change: src.routing.dsdv | behavior.add | test whatsnew
Fixed full-dump spacing cannot reduce periodic overhead in quiet periods or respond to substantial selected-route churn. Add an optional bounded policy using a saturating transition counter and actual submitted payload bytes. Quiet windows lengthen the interval, substantial churn shortens it, and a bitrate target and configured bounds limit the result. Preserve urgent sends, overflow dumps, self-sequence advancement and the disabled-mode event/random path.

DsdvAdaptiveDumps checks quiet, churn, byte-cost and clamp trajectories through real UDP packets and callback timing. Its quiet receiver requires a two-second gap before checking the new statistic; with only new settings omitted, the fixed-period parent is expected to fail that same packet-spacing assertion. This parent comparison is source-grounded until executed. A heterogeneous peer case guards against an invalid receiver-timeout versus own-send-interval restriction. Scheduling and initialization fixtures cover restart and rejected bounds/budget. These cases exercise one policy and its interactions, so they stay with the policy rather than split into independently incomplete behavior commits.

Plan: plan/pending/dsdv-paper-extensions.md

Change: src.routing.dsdv | behavior.add | test whatsnew
Host-only DSDV cannot carry traffic from a multihop mobile network to a wired base station. Add a configured single-base-station profile whose finite host route carries sequenced external-access capability. Project a local default toward that origin while preserving more-specific routes and foreign defaults; withdraw capability urgently when the modeled uplink or wired default disappears, without withdrawing the still-reachable base host.

Version 2 adds a reserved-bit-checked flags byte per entry while version 1 stays unchanged. Keep metadata immutable within an origin sequence, invalidate whole tuples on path loss, and use one conditional deferred reconciliation event to avoid mutation during IPv4 route deletion/replacement callbacks. The core DSDV feature retains its dependencies; only the test feature adds Ethernet.

DsdvBaseStation exercises a real mobile/relay/base/wired-router/external-host path, unavailable-uplink startup, urgent loss, stale input, foreign defaults and DSDV-controller restart. The parent cannot run the new wire/two-interface profile unchanged, so its initialization rejection is missing capability rather than a measured forwarding defect. Existing version-1 controls establish compatibility. Module and unit cases additionally cover origin default replacement, unchanged notifications, 32/33-byte bounds, 50-byte fairness/overflow and replay. The wire, freshness, route-projection and lifecycle checks implement one external-access contract and stay together; most of the diff is its self-contained fixtures.

Plan: plan/pending/dsdv-paper-extensions.md

Change: src.routing.dsdv | behavior.add | test whatsnew migration
The extension design needs an execution record that separates measured support from proposed checks and untested behavior. Record the final source revisions, focused build and test evidence, exact-parent fixture adaptations and the limits of repository-wide gates. Update the plan summary and coverage claims to describe the implemented features without implying performance or unrestricted protocol correctness.

This is documentation only. Runtime evidence and its provenance belong in the execution ledger; protocol behavior, test expectations and fingerprint baselines are unchanged.

Plan: plan/pending/dsdv-paper-extensions.md

Change: doc | behavior.change | -

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 2 potential issues.

1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

Devin Review

Comment on lines +192 to +195
int budget = std::min(par("payloadBudget").intValue(), int64_t(routingInterface->getMtu() - 28));
int entryBytes = DsdvTable::getEntryBytes(getWireVersion());
if (budget < DsdvTable::HEADER_BYTES + entryBytes)
throw cRuntimeError("DSDV payload budget/MTU cannot hold one entry plus IPv4/UDP overhead");

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Startup failure with unlimited interface MTUs

With mtu = 0, start() computes a negative budget and aborts initialization. Ipv4::fragmentAndSend treats zero as unlimited; several broadcast-capable MACs use that default.

Suggested change
int budget = std::min(par("payloadBudget").intValue(), int64_t(routingInterface->getMtu() - 28));
int entryBytes = DsdvTable::getEntryBytes(getWireVersion());
if (budget < DsdvTable::HEADER_BYTES + entryBytes)
throw cRuntimeError("DSDV payload budget/MTU cannot hold one entry plus IPv4/UDP overhead");
int budget = par("payloadBudget").intValue();
if (routingInterface->getMtu() != 0)
budget = std::min(budget, routingInterface->getMtu() - 28);
int entryBytes = DsdvTable::getEntryBytes(getWireVersion());
if (budget < DsdvTable::HEADER_BYTES + entryBytes)
throw cRuntimeError("DSDV payload budget/MTU cannot hold one entry plus IPv4/UDP overhead");

Devin Review


Was this helpful? React with 👍 or 👎 to provide feedback.

Comment on lines +543 to +547
if (interfaceUsable()) {
if (active && routingInterface->getProtocolData<Ipv4InterfaceData>()->getIPAddress() !=
table.getSelf().current.destination)
throw cRuntimeError("DSDV does not support changing its IPv4 identity");
start();

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Oversized updates after interface MTU reductions

After an active interface's MTU decreases, receiveSignal leaves capacity unchanged. start returns immediately while active. Subsequent oversized updates retain Don't Fragment, so Ipv4::fragmentAndSend drops them.

Learn more

DSDV's datagram capacity is the maximum number of routing entries submitted in one UDP packet. start computes it only when the controller becomes active. NetworkInterface::setMtu emits a configuration notification when the MTU changes, but this handler cannot refresh capacity because startup returns while active. sendAdvertisement continues using that capacity and marks every packet nonfragmentable. Ipv4::fragmentAndSend drops packets larger than the new MTU.

Example: Start a version-1 router with MTU 228 bytes and payloadBudget 1400 bytes. Its capacity is 11 entries, producing a 220-byte IPv4 packet when full. Reduce the usable interface's MTU to 100 bytes without taking it down. Capacity remains 11, and full fragments are dropped rather than split into packets containing at most three entries.

Recommended fix: Recompute and validate packet capacity on an ad hoc interface MTU notification, without restarting routing state or resetting sequence floors. Keep adaptive change-history bounds consistent with the new capacity. Add a module test that reduces the MTU while active and verifies subsequent control packets fit the new limit.

Devin Review


Was this helpful? React with 👍 or 👎 to provide feedback.

Change: plan | location | - | dsdv-paper-extensions
The completed extension plan now lives in plan/done. Update the execution record so its plan link resolves after archival.

Change: doc | comment | - | dsdv-paper-extensions

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant