Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flow entries appear even when link and admin state are DOWN #260

Open
hilmarm opened this issue Jun 10, 2020 · 0 comments
Open

Flow entries appear even when link and admin state are DOWN #260

hilmarm opened this issue Jun 10, 2020 · 0 comments
Labels

Comments

@hilmarm
Copy link
Contributor

hilmarm commented Jun 10, 2020

Expected Behavior

  • Adding an IP address on an interface that is not cabled should not trigger addition of flow table entries. Only after the port is UP, should there be flows in tables 10, 20 and 30.
  • Flow table entries in Tables 20 and 30 should disappear when the port is set down.
  • Flow table entries in Table 10 should be removed once an interface is set down.

Actual Behavior

  • Adding an IP address on an interface where link or admin state is down triggers the creation of flow table entries in Table 10, 20 and 30.
  • Removing the IP address (regardless of state UP or DOWN) correctly removes flows in tables 20 and 30. Table 10 entries are still present.
  • Setting an interface from up to down does not delete flow entries for the port in table 10, 20 and 30.

Steps to Reproduce the Problem

Pick a port, say port 2, which has a cable connected. Set interface down on both server side and switch side. (ip link set port2 down). Start with clean switch, reboot if necessary. The command 'client_flowtable_dump' should only show entries in Table 60.

Add an IP to the port on the switch side:
ip a a 10.0.0.1/24 dev port2

Check flow entries in table 10, 20 and 30 with client_flowtable_dump. Flows should not be there.

Remove IP on the switch side:
ip a del 10.0.0.1/24 dev port2

Check flow entries in table 10, 20 and 30 with client_flowtable_dump. Entries from table 20 and 30 are deleted, but table 10 still remains.

Specifications

  • Version: baseboxd 1.5.0
  • Platform: tested on both agema-ag7648 and accton-as4610
  • Subsystem:
@hilmarm hilmarm added the bug label Jun 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant