[katzenpost] Issues with PANDA

[Lasse Wolter]

Hey,
this is Lasse Wolter, a Computer Science student at University of Edinburgh. At first I want to thank you for all the work you have put/are putting into this project and I'm enjoying working with it.
I'm currently doing an internship with the following title:
"Augmenting Anonymous Networks with Telemetry Feedback"

I'm trying to evaluate the mixnet traffic under different conditions and investigate if it would make sense to implement some kind of control algorithm for changing the mixnet parameters automatically. I'm trying to use katzenpost for this project.
I've set up a mixnet in a virtual machine consisting of:

  *
1 authority
  *
2 providers
     *
both running memspool as an external plugin
     *
one of them running PANDA as external plugin
  *
  *
6 mixes

Things seem to start up fine and the PKI document is generated.
Now, for the experiments itself I need to send messages. Hence, I'm trying to use the catshadow client to create users, add them as contacts of one another and send messages.
When I connect two catshadow sessions to your mixnet (provider: idefix), create users and add them as contacts, I can let them talk to one another. Looking at the catshadow logs, I see the debug message:
"PANDA exchange completed"

However, running the exact same setup - this time connected to my local mixnet - I receive the following message:
"Failure waiting for reply, timeout reached"

Now, I'm not sure if this is an issue with my mixnet or with PANDA. Could you provide any help with this/tell me how PANDA is setup on your mixnet?

I'm using:

  *
catshadow: release v0.0.1
  *
PANDA: release v0.0.3

Thanks a lot for your help and for all the work you are putting into this project.

Best wishes,

Lasse




 The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mixnetworks.org/pipermail/katzenpost/attachments/20190702/8e0ec9a0/attachment.html>