possible ttl bug in linux version of mgen #35
PatrickTague
started this conversation in
General
Replies: 1 comment 4 replies
-
I think this has been addressed in the more recent source code that is on GitHub. The intent was to have the _default_ TTL for _multicast_ to be 3 but at one point that also got mistakenly applied to unicast too.
…Sent from my iPhone
On Oct 3, 2021, at 6:41 PM, PatrickTague ***@***.***> wrote:
i'm trying to use mgen for traffic profiling in the CORE emulator. however, for every TCP flow i try to create, it sets the TTL field to 3, regardless of what parameter i provide as part of the flow definition. is there an easy way to fix this?
for context, i'm using the version of mgen that is installed via apt in ubuntu, i believe it's 5.02c.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
i'm trying to use mgen for traffic profiling in the CORE emulator. however, for every TCP flow i try to create, it sets the TTL field to 3, regardless of what parameter i provide as part of the flow definition. is there an easy way to fix this?
for context, i'm using the version of mgen that is installed via apt in ubuntu, i believe it's 5.02c.
Beta Was this translation helpful? Give feedback.
All reactions