195 reputation
17
bio website
location Chile
age
visits member for 2 years, 6 months
seen Jul 2 at 14:21

Jun
29
awarded  Benefactor
Jun
29
comment How does Chrome/webRTC select which TURN server to use if multiple options are given?
I did award the bounty, because it expires in four hours and your answer is the only one. :-) Though I'm not entirely sure if it is correct. We currently run two TURN servers for an application (US and EU hosted). Since the code for adding the turn servers is always the same, only one TURN server should be used. However, both see a similar amount of usage. (The app is Chrome only) ... There is definitely a selection process. The question is how it works.
Jun
26
awarded  Student
Jun
22
awarded  Promoter
May
5
awarded  Tumbleweed
Apr
28
asked How does Chrome/webRTC select which TURN server to use if multiple options are given?
Jun
28
awarded  Yearling
Feb
14
comment Hotmail Sender ID always fails with “temperror” regardless of SPF
Does this issue really still exist? I'm having exactly the same issue: ALL other ESPs and checks work flawlessly, but hotmail insists on temperrors both for DKIM and for SPF.
Mar
30
awarded  Supporter
Mar
6
revised Linux Slow Start: Changing ip route does not have any effect on initial window
deleted 192 characters in body
Mar
6
revised Linux Slow Start: Changing ip route does not have any effect on initial window
added 45 characters in body
Mar
6
revised Linux Slow Start: Changing ip route does not have any effect on initial window
added 269 characters in body
Mar
5
comment Linux Slow Start: Changing ip route does not have any effect on initial window
I don't know your setup. The original poster asked why despite increasing the initial window size on the server his test connection only has a window size of 5840 bytes. The answer is: Because the client he tested with does not allow a bigger window size. I can't comment on other setups or possibly other problems/bugs with the concept in general.
Mar
5
revised Linux Slow Start: Changing ip route does not have any effect on initial window
added 543 characters in body
Mar
5
comment Linux Slow Start: Changing ip route does not have any effect on initial window
Just to emphasize, I think you got this the wrong way around: The first sending machine is the client as it opens the connection, not your server. It is the client offering the 5840 byte window. The server cannot propose a larger window size, only a smaller one.
Mar
5
comment Linux Slow Start: Changing ip route does not have any effect on initial window
Uh, 17.255.209.0 is your server subnet, right? The packet you are seeing is FROM 21.101.151.198.45873 TO 17.255.209.19.http. I am no expert on tcpdump output, but to me this reads: Hello Server, I am your client, I like 5840 byte windows. :) The next packet would be the server responding with ACK, 5840 is great, cheers. :)
Mar
5
awarded  Editor
Mar
5
revised Linux Slow Start: Changing ip route does not have any effect on initial window
added 126 characters in body
Mar
5
comment Linux Slow Start: Changing ip route does not have any effect on initial window
I assume that's what Sam Saffron is referring to in his comment: Linux 3.0 has an RWIN of 10 MSS (14.600 bytes).
Mar
5
answered Linux Slow Start: Changing ip route does not have any effect on initial window