Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
-+-
 Reporter:  irl  |  Owner:  acute
 Type:  enhancement  | Status:  closed
 Priority:  Low  |  Milestone:
Component:  Metrics/Onionperf|Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:  metrics-team-roadmap-2020, metrics-  |  Actual Points:  0.5
  team-roadmap-2020-june |
Parent ID:  #33321   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor59
-+-
Changes (by acute):

 * actualpoints:  0.3 => 0.5


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
-+-
 Reporter:  irl  |  Owner:  acute
 Type:  enhancement  | Status:  closed
 Priority:  Low  |  Milestone:
Component:  Metrics/Onionperf|Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:  metrics-team-roadmap-2020, metrics-  |  Actual Points:  0.3
  team-roadmap-2020-june |
Parent ID:  #33321   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor59
-+-
Changes (by karsten):

 * status:  accepted => closed
 * resolution:   => wontfix
 * actualpoints:  0.1 => 0.3


Comment:

 Thanks for the patch! Merged after fixing a typo and a few trailing
 spaces. Feel free to add your actual points to mine.

 Closing with reason wontfix as something we considered carefully but
 decided against. See the comments above for more details. Thanks,
 everyone!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
-+-
 Reporter:  irl  |  Owner:  acute
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Low  |  Milestone:
Component:  Metrics/Onionperf|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-team-roadmap-2020, metrics-  |  Actual Points:  0.1
  team-roadmap-2020-june |
Parent ID:  #33321   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor59
-+-

Comment (by acute):

 Attached a patch that describes how to use other TGen models. You can also
 see how the formatting looks here:

 https://github.com/ana-cc/onionperf/tree/docs

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
-+-
 Reporter:  irl  |  Owner:  acute
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Low  |  Milestone:
Component:  Metrics/Onionperf|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-team-roadmap-2020, metrics-  |  Actual Points:  0.1
  team-roadmap-2020-june |
Parent ID:  #33321   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor59
-+-
Changes (by acute):

 * Attachment "0001-Adds-arbitrary-traffic-model-documentation.patch"
 added.


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
-+-
 Reporter:  irl  |  Owner:  acute
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Low  |  Milestone:
Component:  Metrics/Onionperf|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-team-roadmap-2020, metrics-  |  Actual Points:  0.1
  team-roadmap-2020-june |
Parent ID:  #33321   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor59
-+-

Comment (by karsten):

 Replying to [comment:18 phw]:
 > Replying to [comment:16 karsten]:
 > > Thanks for the patch! I applied it together with another minor patch
 to also remove the `--traffic-model` parameter from the documentation.
 > [[br]]
 > I think we also need to remove the
 
[https://gitweb.torproject.org/onionperf.git/tree/onionperf/onionperf?id=17b0cf422adc81d356d1db4aba46b495e9487d0b#n331
 if condition] that checks for `args.model`.

 Oh, good point!
 
[https://gitweb.torproject.org/onionperf.git/commit/?id=e580cb885d9bb18298f65c04e541d2152a8e7a0e
 Fixed here.] Thanks!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
-+-
 Reporter:  irl  |  Owner:  acute
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Low  |  Milestone:
Component:  Metrics/Onionperf|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-team-roadmap-2020, metrics-  |  Actual Points:  0.1
  team-roadmap-2020-june |
Parent ID:  #33321   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor59
-+-

Comment (by phw):

 Replying to [comment:16 karsten]:
 > Thanks for the patch! I applied it together with another minor patch to
 also remove the `--traffic-model` parameter from the documentation.
 [[br]]
 I think we also need to remove the
 
[https://gitweb.torproject.org/onionperf.git/tree/onionperf/onionperf?id=17b0cf422adc81d356d1db4aba46b495e9487d0b#n331
 if condition] that checks for `args.model`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
-+-
 Reporter:  irl  |  Owner:  acute
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Low  |  Milestone:
Component:  Metrics/Onionperf|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-team-roadmap-2020, metrics-  |  Actual Points:  0.1
  team-roadmap-2020-june |
Parent ID:  #33321   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor59
-+-
Changes (by acute):

 * owner:  metrics-team => acute
 * status:  new => accepted


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
-+-
 Reporter:  irl  |  Owner:
 |  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Low  |  Milestone:
Component:  Metrics/Onionperf|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-team-roadmap-2020, metrics-  |  Actual Points:  0.1
  team-roadmap-2020-june |
Parent ID:  #33321   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor59
-+-
Changes (by karsten):

 * status:  reopened => new


Comment:

 Thanks for the patch! I applied it together with another minor patch to
 also remove the `--traffic-model` parameter from the documentation.

 I also added comments to #33432 and #30798 with references to this ticket.

 What remains is to '''write documentation for using other models we don't
 support as proposed above'''. I think we can keep this ticket open until
 that is done. Setting ticket status to new for that last part.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.1
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--
Changes (by acute):

 * Attachment "0001-Removes-unused-traffic-model-argument.patch" added.


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.1
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--

Comment (by karsten):

 Agreed with what you write, robgjansen.

 Replying to [comment:13 acute]:
 > > If researchers need to change parts of a model that cannot be
 configured using the OnionPerf command line interface, they will have to
 change the OnionPerf sources to do what they want. I'd say that that's
 still easier than editing a TGen XML file. If the missing piece is better
 documentation, we should provide that.
 > That is exactly what I had in mind for doing this.

 Great!

 > > My suggestions are that we:
 > >  - make the current bulk transfer model more configurable by adding
 parameters like initial pause, transfer count, or filesize as part of
 #33432;
 > >  - develop a ping model as internal model where OnionPerf generates
 TGen files, plus analysis and visualization code, as part of #30798,
 assuming there's need for developing such a model; and
 > >  - remove the `-m/--traffic-model` parameter from the codebase and
 close this ticket as something we considered carefully but decided
 against.
 >
 > This all sounds good, but I'd add to this writing some documentation for
 using other models we don't support as proposed above.

 Yes, good point! Updated next steps are:
  - make the current bulk transfer model more configurable by adding
 parameters like initial pause, transfer count, or filesize as part of
 #33432;
  - develop a ping model as internal model where OnionPerf generates TGen
 files, plus analysis and visualization code, as part of #30798, assuming
 there's need for developing such a model;
  - write documentation for using other models we don't support as proposed
 above; and
  - remove the `-m/--traffic-model` parameter from the codebase and close
 this ticket as something we considered carefully but decided against.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.1
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--

Comment (by acute):

 > If researchers need to change parts of a model that cannot be configured
 using the OnionPerf command line interface, they will have to change the
 OnionPerf sources to do what they want. I'd say that that's still easier
 than editing a TGen XML file. If the missing piece is better
 documentation, we should provide that.
 That is exactly what I had in mind for doing this.

 >
 > My suggestions are that we:
 >  - make the current bulk transfer model more configurable by adding
 parameters like initial pause, transfer count, or filesize as part of
 #33432;
 >  - develop a ping model as internal model where OnionPerf generates TGen
 files, plus analysis and visualization code, as part of #30798, assuming
 there's need for developing such a model; and
 >  - remove the `-m/--traffic-model` parameter from the codebase and close
 this ticket as something we considered carefully but decided against.

 This all sounds good, but I'd add to this writing some documentation as
 proposed above.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.1
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--

Comment (by robgjansen):

 Sorry, I don't know if "self-contained" is the right phrasing here. I mean
 that we should focus our efforts on building OnionPerf for the immediate
 needs of Tor metrics, rather than for many general use-cases. Reducing our
 scope will help us create a tighter, more polished tool.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.1
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--

Comment (by robgjansen):

 Replying to [comment:10 karsten]:

 > Thinking about different traffic models, what if we wanted to measure
 something like an `HTTP POST` rather than the `HTTP GET`? I'd assume that
 we'd have to provide a different TGen ''server'' model file as well, but I
 don't know for sure.

 I think this only requires changes to the client side model, i.e., you
 would increase the `sendsize` and reduce the `receivesize` values.

 > If that's still possible with replacing just the TGen client model,
 there's probably another model that requires a custom TGen server model
 which we just didn't think of yet.

 I designed TGen so that the server config is minimal: log level, how often
 to print a heartbeat message, and the port it should listen on. (See the
 [https://github.com/shadow/tgen/blob/master/doc/TGen-Options.md#start-
 options start options table].) Otherwise it just responds to commands send
 from the client.

 More complicated models than we have been discussing are possible, though,
 through the use of Markov models. Creating Markov models for TGen is even
 more complicated than creating TGen config files, but also really really
 powerful. I did my best to [https://github.com/shadow/tgen/blob/master/doc
 /TGen-Markov-Models.md document how to create the Markov models], but I'm
 hoping that we won't need them for OnionPerf. (I use them to generate
 traffic flows in Shadow that are based on actual traffic flows that we
 measured at Tor relays.)

 > All in all, it's more than just ''the'' TGen model. We'd have to write a
 fair amount of code in order to implement a useful ping model in
 OnionPerf.

 Agreed.

 > The internally generated model also has the advantage that it's easier
 to use. All it takes to start a measurement is a (potentially quite long)
 command with several parameters. But it doesn't require a (still
 potentially long) command plus one or two files. Describing the experiment
 would then be a matter of listing all software versions and the OnionPerf
 command used to start measurements.
 >
 > My suggestions are that we:
 [snip]

 Agreed with all of this too! I think that as much as we can, we should
 make OnionPerf a self-contained tool that is primarily useful for
 generating and visualizing Tor metrics data. But, we could document that
 other models are possible but unsupported. If some researchers want to use
 OnionPerf to help them answer some research problems, they could fairly
 easily adapt OnionPerf to their specific needs.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.1
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--

Comment (by karsten):

 Thank you, robgjansen and acute, for your comments above! The more I think
 about this feature, the more I come to the conclusion that we do not need
 it.

 I'll start with addressing acute's thoughts:

 Replying to [comment:9 acute]:
 > Having a pass-through feature could be very useful for research. For
 example, evaluating Tor performance with clients in mobile or other type
 of bandwidth-constrained networks would require a model that minimises the
 used bandwidth; or if a user wanted to fill the pipe for a congestion
 control experiment a larger file size model would be needed etc.

 I can see how different network environments would require different
 measurement models. But maybe we can identify how these models should
 differ and then add parameters to OnionPerf's command line that feed into
 the generated TGen models. For example, the file size of the downloaded
 file could easily be a `--filesize` parameter on the command line.

 > If there is no appetite for implementing this feature, what we could
 have instead is documentation that explains to users how to use their own
 model if they want to, and keep our own models (including oneshot)
 internally as suggested here.

 If researchers need to change parts of a model that cannot be configured
 using the OnionPerf command line interface, they will have to change the
 OnionPerf sources to do what they want. I'd say that that's still easier
 than editing a TGen XML file. If the missing piece is better
 documentation, we should provide that.

 Now to robgjansen's thoughts:

 Replying to [comment:8 robgjansen]:
 > The use case was to allow OnionPerf to measure traffic patterns other
 than the usual "file download" pattern (the model that OnionPerf generates
 for itself internally). So, for example, you could set up a tgen traffic
 model to act like a ping utility, sending a few bytes to the server side
 and back to the client to measure circuit round-trip times.

 The ping model is something that we're considering to implement in #30798,
 so let's consider what that would entail:
  - We would need a different TGen client model that sends a few bytes
 every second or every configurable amount of time.
  - We would also need to update the analysis code in OnionPerf. We'd no
 longer be interested in elapsed seconds between start and reaching a
 certain stage of the download. We'd want to extract the time between
 sending a ping and receiving a pong, for every one of them.
  - In fact, we might want to parse the TGen server logs as well, to learn
 when a ping arrived and the pong was sent back. We have that information,
 which is not available to the typical ping application, so why not use it.
  - We would have to update the visualization code to extract and display
 different metrics than in the bulk download case.

 Thinking about different traffic models, what if we wanted to measure
 something like an `HTTP POST` rather than the `HTTP GET`? I'd assume that
 we'd have to provide a different TGen ''server'' model file as well, but I
 don't know for sure. If that's still possible with replacing just the TGen
 client model, there's probably another model that requires a custom TGen
 server model which we just didn't think of yet.

 All in all, it's more than just ''the'' TGen model. We'd have to write a
 fair amount of code in order to implement a useful ping model in
 OnionPerf.

 > My initial idea was not to make OnionPerf generate these models, but
 rather to create them externally and have OnionPerf just "pass them
 through" to tgen. That means whoever generated the models would need to
 correctly set the server addresses and SOCKS ports, etc.
 >
 > I'm not sure that Tor wants this feature for OnionPerf. An alternative
 could just be to wait until you have a specific model in mind that you've
 decided you want to start measuring, and then generate that model
 internally as we do now with the 5MiB downloads. In that case the pass-
 through feature would not be needed, and you wouldn't have to maintain
 something that you don't use.
 >
 > Do you think the pass-through feature is actually useful for Tor, or
 does generating models internally make more sense?
 >
 > (The tgen models in Shadow are generated with the correct
 addresses/ports 

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.1
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--

Comment (by acute):

 Replying to [comment:8 robgjansen]:
 >
 > My initial idea was not to make OnionPerf generate these models, but
 rather to create them externally and have OnionPerf just "pass them
 through" to tgen. That means whoever generated the models would need to
 correctly set the server addresses and SOCKS ports, etc.
 >
 > I'm not sure that Tor wants this feature for OnionPerf. An alternative
 could just be to wait until you have a specific model in mind that you've
 decided you want to start measuring, and then generate that model
 internally as we do now with the 5MiB downloads. In that case the pass-
 through feature would not be needed, and you wouldn't have to maintain
 something that you don't use.
 >
 > Do you think the pass-through feature is actually useful for Tor, or
 does generating models internally make more sense?

 Having a pass-through feature could be very useful for research. For
 example, evaluating Tor performance with clients in mobile or other type
 of bandwidth-constrained networks would require a model that minimises the
 used bandwidth; or if a user wanted to fill the pipe for a congestion
 control experiment a larger file size model would be needed etc.

 If there is no appetite for implementing this feature, what we could have
 instead is documentation that explains to users how to use their own model
 if they want to, and keep our own models (including oneshot) internally as
 suggested here.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.1
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--

Comment (by robgjansen):

 The use case was to allow OnionPerf to measure traffic patterns other than
 the usual "file download" pattern (the model that OnionPerf generates for
 itself internally). So, for example, you could set up a tgen traffic model
 to act like a ping utility, sending a few bytes to the server side and
 back to the client to measure circuit round-trip times.

 My initial idea was not to make OnionPerf generate these models, but
 rather to create them externally and have OnionPerf just "pass them
 through" to tgen. That means whoever generated the models would need to
 correctly set the server addresses and SOCKS ports, etc.

 I'm not sure that Tor wants this feature for OnionPerf. An alternative
 could just be to wait until you have a specific model in mind that you've
 decided you want to start measuring, and then generate that model
 internally as we do now with the 5MiB downloads. In that case the pass-
 through feature would not be needed, and you wouldn't have to maintain
 something that you don't use.

 Do you think the pass-through feature is actually useful for Tor, or does
 generating models internally make more sense?

 (The tgen models in Shadow are generated with the correct addresses/ports
 during the phase when we generate the Shadow experiment configuration.
 This is currently done using the Shadow-Tor config generator
 [https://github.com/shadow/tornetgen here].)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.1
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--
Changes (by karsten):

 * actualpoints:   => 0.1


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID:  #33321 | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--
Changes (by karsten):

 * cc: robgjansen, jnewsome (added)


Comment:

 What is the use case here? Is this about providing TGen traffic models
 that are otherwise used in Shadow, but for more complex user models than
 bulk file downloads? OnionPerf users are not expected to generate these
 model files on their own, neither from scratch nor by editing existing
 model files, right?

 One technical problem I see is that TGen models generated by OnionPerf
 contain measurement details like peers (server addresses) or ports (SOCKS
 port of the local Tor client). Would the provided models contain
 placeholders for these parts that OnionPerf fills in before passing models
 to its TGen instances? How does Shadow solve this problem?

 Related to this ticket, we might want to implement #33243 by providing a
 traffic model file rather than by adding more command line parameters. In
 fact, we could take out the `--oneshot` parameter if we provide a traffic
 model file for it.

 Implementation note: OnionPerf already contains a `-m/--traffic-model`
 parameter that does not do anything right now and that we would implement
 here.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29370 [Metrics/Onionperf]: Measure mode with arbitrary tgen traffic models

[Tor Bug Tracker & Wiki]

#29370: Measure mode with arbitrary tgen traffic models
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  reopened
 Priority:  Low|  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:  Sponsor59
---+--
Changes (by gaba):

 * keywords:   => metrics-team-roadmap-2020
 * points:   => 1
 * sponsor:   => Sponsor59


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs