Opened 6 years ago

Closed 11 months ago

#8085 closed task (wontfix)

Develop a bad transparent proxy test

Reported by: vmon Owned by: zwol
Priority: High Milestone:
Component: Archived/Stegotorus Version:
Severity: Normal Keywords: chopper, ack, archived-closed-2018-07-04
Cc: zwol Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We need to develop a variant of the transparent proxy unit test in which, the proxy drops some of the chop blocks randomly based on pre-specified rate.

This is to reliably test and reproduce any bug in the chopper's acknowledgement protocol.

Child Tickets

Change History (3)

comment:1 Changed 6 years ago by vmon

The transparent tester_proxy now has the commandline option[--drop-rate DROPRATE] where DROPRATE is a decimal number between 0 and 1. Everytime, read_cb is called back by libevent to retrieve the information, the proxy reads the data off the socket and then generate random number between 0 and 1 and write it to the other socket, only if the number is greater than the DROPRATE.

Without re-transmit, this bring the communication to stall. It is not clear for me that Stegotorus, as it is, can survive this even with retransmission for high drop rates. But there are ways to fix that. For one thing, I don't know why Stegotorus does not follow HTTP 1.1 standard of all connections are persistant. Persistent connections can solve quite few of the current problems.

I have yet to write a formal python unit test running this with different rates but for now I'm using it to test the retransmission.

comment:2 Changed 18 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:3 Changed 11 months ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: newclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.