On 4/25/2020 8:32 AM, Dave Taht wrote:
It would be a useful test for an intrepid windows administrator to actually enable ecn fully and see what breaks in their vpn, smb, and rdp implementations, and across their remote workforce, and observe any difference in QoE. I have long tried to get one drunk enough to deploy ecn across their windows infrastructure without any success.
I can easily do it for myself, now that I know where that setting hides. Is there reason to make others do it or is it sufficient that I be the only guinea pig here?
since (I think?) the proposed vpn traffic is client -> server (?) not, clients -> router -> server, each individual using this link over the vpn will tend to get their own queue, and a big upload or download through their openvpn will tend to "do them in", because openvpn has lousy queue management internally... and (when last I looked), windows itself had not a lot of backpressure when dealing with that device.
I'm using openvpn to avoid exposing raw RDP servers to the Internet. I still don't trust MS enough to allow a Windows box directly connected to the Internet. So it's Win10(@home) -> openvpn(client on Win10 @home) ->openvpn(Linux router @office)->Win10(@office). I think another user may use RDP's file transfer capabilities, but I personally use a separate ssh (scp) connection for that. I have no problem with command lines.
_______________________________________________ Bloat mailing list [email protected] https://lists.bufferbloat.net/listinfo/bloat
