oxidecomputer / oxidecomputer/dendrite
drop_ports and drop_reason don't match
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 4
Description
For each dropped packet, we should be bumping two counters: one for the reason and one for the ingress port. The total count in each table should match. However:
root@oxz_switch1:~# swadm counters get Drop_Reason
Counter Packets
ipv4_switch_addr_miss 0
ipv6_switch_addr_miss 0
bad_ping 0
nat_header_error 0
arp_mapping_null 0
arp_miss 2
ndp_mapping_null 0
ndp_miss 0
multicast_to_local_interface 0
ipv4_checksum_err 0
ipv4_ttl_invalid 0
ipv4_ttl_exceeded 56
ipv6_ttl_invalid 0
ipv6_ttl_exceeded 0
ipv6_unrouteable 0
ipv4_unrouteable 20
root@oxz_switch1:~# swadm counters get Drop_Port | grep qsfp
qsfp0/0 6239
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the mismatch with swadm counters get Drop_Reason and swadm counters get Drop_Port, comparing totals for the same traffic. Trace where dropped packets update the reason and ingress-port counters; done means both tables report the same total for each dropped packet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100