I have been evaluating chromoting webrtc with bandwidth throttling using the simple wondershaper tool.

It appears it works well with the old path of reporting captured frames, but things come to a halt when we use it on the current encoded path due to estimated bandwidth being completely off.

==
18/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9113
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9114
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9115
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9116
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9117
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9118
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9119
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9120
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9121
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9122
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9123
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9124
[0418/150926:WARNING:rtp_packet_history.cc(187)] No match for getting seqNum 9125
[0418/150926:ERROR:generic_encoder.cc(194)] Target bitrate (kbps) 171687
[0418/150926:ERROR:generic_encoder.cc(194)] Target bitrate (kbps) 186317
[0418/150927:ERROR:generic_encoder.cc(194)] Target bitrate (kbps) 180150
[0418/150927:ERROR:generic_encoder.cc(194)] Target bitrate (kbps) 180150
[0418/150927:ERROR:generic_encoder.cc(194)] Target bitrate (kbps) 159164
[0418/150927:ERROR:generic_encoder.cc(194)] Target bitrate (kbps) 100362
===