oxidecomputer / oxidecomputer/opte
incorrect inbound flow list after ping in testbed topo
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
After creating the opte-ddm-x2 topo and setting up TGs: send ping from 10.0.0.1 to 10.0.0.3. Then dump the UFT for the 10.0.0.1 port (on sled1). Notice there is an inbound flow from 10.0.0.1: that shouldn't be there.
root@sled1:/opt/cargo-bay# ./opteadm dump-uft -p xde0
Unified Flow Table
======================================================================
Inbound Flows [2/8192]
----------------------------------------------------------------------
PROTO SRC IP SPORT DST IP DPORT HITS ACTION
ICMP 10.0.0.1 0 10.0.0.3 0 0 decap,
ICMP 10.0.0.3 0 10.0.0.1 0 0 decap,
Outbound Flows [1/8192]
----------------------------------------------------------------------
PROTO SRC IP SPORT DST IP DPORT HITS ACTION
ICMP 10.0.0.1 0 10.0.0.3 0 0 ,encap
Contributor guide
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
Reproduce the opte-ddm-x2 testbed flow by pinging 10.0.0.1 to 10.0.0.3, then run ./opteadm dump-uft -p xde0 on sled1. Inspect how the UFT records inbound and outbound ICMP flows; done means the 10.0.0.1 port no longer shows the unexpected inbound flow while the expected outbound flow remains.
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
- Mostly clear
- Newbie friendliness
- 35/100