8000 Can't reset TCLink to zero loss and delay · Issue #881 · mininet/mininet · GitHub
[go: up one dir, main page]

Skip to content

Can't reset TCLink to zero loss and delay #881

Open

Description

@snizovtsev

This optimization prevents zeroing loss or delay link parameters after non-zero period because "not 0 = True" in Python:

mininet/mininet/link.py

Lines 352 to 354 in e203808

if ( bw is None and not delay and not loss
and max_queue_size is None ):
return

It should be compared to None or running value instead.

Activity

  1. cheriimoya commented on Feb 2, 2022

    @cheriimoya
    Contributor

    you are right

  2. lantz commented on Apr 1, 2022

    @lantz
    Member

    I believe the intent was to not add an unnecessary queuing discipline.

    Is there a workaround if you set the loss to 0%?

  3. janev94 commented on Nov 18, 2022

    @janev94

    addLink currently by default makes loss to 0%. This is not an issue in the current build at least @lantz .

  4. lantz commented on Nov 19, 2022

    @lantz
    Member

    @cheriimoya
    Is setting the loss to 0% a reasonable workaround?

  5. greenbigfrog commented on Apr 1, 2025

    @greenbigfrog

    Setting loss via a str doesn't work in mn 2.3.1b4.

    What kind of works as a semi workaround for me for now, is setting it to a tiny tiny float value. Although being able to go back to 0% loss would be preferred.

  6. janev94 commented on Apr 1, 2025

    @janev94

    Setting loss via a str doesn't work in mn 2.3.1b4.

    What kind of works as a semi workaround for me for now, is setting it to a tiny tiny float value. Although being able to go back to 0% loss would be preferred.

    As I said above, when you do not provide value for loss for addLink it does not add loss, by default. If you want to apply loss dynamically you should use the patch that @cheriimoya quoted in the thread.

  7. greenbigfrog commented on Apr 1, 2025

    @greenbigfrog

    Alright, thanks.
    I understood this issue to be purely about resetting link loss, which implies dynamically changing loss back to 0.
    I'll use the fix in the PR.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0