[Bloat] Issue with negotiating ECN with Cloudflare hosts?

General list for discussing Bufferbloat
 help / color / mirror / Atom feed

* [Bloat] Issue with negotiating ECN with Cloudflare hosts?
@ 2019-09-19 17:50 Toke Høiland-Jørgensen
  2019-09-20  7:24 ` Jesper Dangaard Brouer
  0 siblings, 1 reply; 4+ messages in thread
From: Toke Høiland-Jørgensen @ 2019-09-19 17:50 UTC (permalink / raw)
  To: ecn-sane, bloat

Is anyone else experiencing problems negotiating ECN when connecting to
Cloudflare? I see this for most sites protected by Cloudflare (such as
bufferbloat.net), but only when using IPv4:

# sysctl -w net.ipv4.tcp_ecn=1
net.ipv4.tcp_ecn = 1
# curl -v 1.1.1.1
*   Trying 1.1.1.1:80...
* TCP_NODELAY set
* Connected to 1.1.1.1 (1.1.1.1) port 80 (#0)
> GET / HTTP/1.1
> Host: 1.1.1.1
> User-Agent: curl/7.66.0
> Accept: */*
> 
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer


# sysctl -w net.ipv4.tcp_ecn=0
net.ipv4.tcp_ecn = 0
# curl -v 1.1.1.1
*   Trying 1.1.1.1:80...
* TCP_NODELAY set
* Connected to 1.1.1.1 (1.1.1.1) port 80 (#0)
> GET / HTTP/1.1
> Host: 1.1.1.1
> User-Agent: curl/7.66.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Date: Thu, 19 Sep 2019 17:42:22 GMT
< Content-Type: text/html
< Transfer-Encoding: chunked
< Connection: keep-alive
< Location: https://1.1.1.1/
< Served-In-Seconds: 0.000
< CF-Cache-Status: HIT
< Age: 4442
< Expires: Thu, 19 Sep 2019 21:42:22 GMT
< Cache-Control: public, max-age=14400
< Server: cloudflare
< CF-RAY: 518d5b13fcfcd43f-HAM
< 
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>cloudflare-lb</center>
</body>
</html>
* Connection #0 to host 1.1.1.1 left intact


I've opened a support request with my ISP, but thought I'd ask if anyone
else was seeing this? (Is anyone else running with ECN enabled?)

-Toke

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bloat] Issue with negotiating ECN with Cloudflare hosts?
  2019-09-19 17:50 [Bloat] Issue with negotiating ECN with Cloudflare hosts? Toke Høiland-Jørgensen
@ 2019-09-20  7:24 ` Jesper Dangaard Brouer
       [not found]   ` <CAJPywT+Xa9pXpZ66eKR7NOpn8T-Tt_obU6HjShzw=zQCDeudfg@mail.gmail.com>
  2019-09-20  9:41   ` Toke Høiland-Jørgensen
  0 siblings, 2 replies; 4+ messages in thread
From: Jesper Dangaard Brouer @ 2019-09-20  7:24 UTC (permalink / raw)
  To: Toke Høiland-Jørgensen; +Cc: ecn-sane, bloat, brouer, Marek Majkowski


On Thu, 19 Sep 2019 19:50:45 +0200 Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Is anyone else experiencing problems negotiating ECN when connecting to
> Cloudflare? I see this for most sites protected by Cloudflare (such as
> bufferbloat.net), but only when using IPv4:
> 
> # sysctl -w net.ipv4.tcp_ecn=1
> net.ipv4.tcp_ecn = 1
> # curl -v 1.1.1.1
> *   Trying 1.1.1.1:80...
> * TCP_NODELAY set
> * Connected to 1.1.1.1 (1.1.1.1) port 80 (#0)
> > GET / HTTP/1.1
> > Host: 1.1.1.1
> > User-Agent: curl/7.66.0
> > Accept: */*
> >   
> * Recv failure: Connection reset by peer
> * Closing connection 0
> curl: (56) Recv failure: Connection reset by peer

It works for me when repeating your experiment:

$ sysctl -w net.ipv4.tcp_ecn=1
net.ipv4.tcp_ecn = 1

$ curl -v 1.1.1.1
* Rebuilt URL to: 1.1.1.1/
*   Trying 1.1.1.1...
* TCP_NODELAY set
* Connected to 1.1.1.1 (1.1.1.1) port 80 (#0)
> GET / HTTP/1.1
> Host: 1.1.1.1
> User-Agent: curl/7.61.1
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Date: Fri, 20 Sep 2019 07:19:48 GMT
< Content-Type: text/html
< Transfer-Encoding: chunked
< Connection: keep-alive
< Location: https://1.1.1.1/
< Served-In-Seconds: 0.000
< CF-Cache-Status: HIT
< Age: 5944
< Expires: Fri, 20 Sep 2019 11:19:48 GMT
< Cache-Control: public, max-age=14400
< Server: cloudflare
< CF-RAY: 519208830aced891-CPH
[...]
 
 
> # sysctl -w net.ipv4.tcp_ecn=0
> net.ipv4.tcp_ecn = 0
> # curl -v 1.1.1.1
> *   Trying 1.1.1.1:80...
> * TCP_NODELAY set
> * Connected to 1.1.1.1 (1.1.1.1) port 80 (#0)
> > GET / HTTP/1.1
> > Host: 1.1.1.1
> > User-Agent: curl/7.66.0
> > Accept: */*
> >   
> * Mark bundle as not supporting multiuse
> < HTTP/1.1 301 Moved Permanently
> < Date: Thu, 19 Sep 2019 17:42:22 GMT
> < Content-Type: text/html
> < Transfer-Encoding: chunked
> < Connection: keep-alive
> < Location: https://1.1.1.1/
> < Served-In-Seconds: 0.000
> < CF-Cache-Status: HIT
> < Age: 4442
> < Expires: Thu, 19 Sep 2019 21:42:22 GMT
> < Cache-Control: public, max-age=14400
> < Server: cloudflare
> < CF-RAY: 518d5b13fcfcd43f-HAM
> < 
> <html>
> <head><title>301 Moved Permanently</title></head>
> <body bgcolor="white">
> <center><h1>301 Moved Permanently</h1></center>
> <hr><center>cloudflare-lb</center>
> </body>
> </html>
> * Connection #0 to host 1.1.1.1 left intact
> 
> 
> I've opened a support request with my ISP, but thought I'd ask if anyone
> else was seeing this? (Is anyone else running with ECN enabled?)

I'm not seeing it, so it might be your ISP?

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

^ permalink raw reply	[flat|nested] 4+ messages in thread

[parent not found: <CAJPywT+Xa9pXpZ66eKR7NOpn8T-Tt_obU6HjShzw=zQCDeudfg@mail.gmail.com>]

* Re: [Bloat] Issue with negotiating ECN with Cloudflare hosts?
       [not found]   ` <CAJPywT+Xa9pXpZ66eKR7NOpn8T-Tt_obU6HjShzw=zQCDeudfg@mail.gmail.com>
@ 2019-09-20  9:38     ` Toke Høiland-Jørgensen
  0 siblings, 0 replies; 4+ messages in thread
From: Toke Høiland-Jørgensen @ 2019-09-20  9:38 UTC (permalink / raw)
  To: Marek Majkowski, Jesper Dangaard Brouer; +Cc: ecn-sane, bloat

Marek Majkowski <marek@cloudflare.com> writes:

> We definitely don't do anything fancy about ECN on our side. It must
> be some middle-box or intermediate router.

Yeah, didn't figure you guys were, at least not on purpose... :)

> Could you share your source IP, traceroute, and ideally "traceroute
> -S" (tcp/SYN mode).

Sure, I'll send you that off-list.

-Toke

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bloat] Issue with negotiating ECN with Cloudflare hosts?
  2019-09-20  7:24 ` Jesper Dangaard Brouer
       [not found]   ` <CAJPywT+Xa9pXpZ66eKR7NOpn8T-Tt_obU6HjShzw=zQCDeudfg@mail.gmail.com>
@ 2019-09-20  9:41   ` Toke Høiland-Jørgensen
  1 sibling, 0 replies; 4+ messages in thread
From: Toke Høiland-Jørgensen @ 2019-09-20  9:41 UTC (permalink / raw)
  To: Jesper Dangaard Brouer; +Cc: ecn-sane, bloat, brouer, Marek Majkowski

Jesper Dangaard Brouer <brouer@redhat.com> writes:

> On Thu, 19 Sep 2019 19:50:45 +0200 Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>> Is anyone else experiencing problems negotiating ECN when connecting to
>> Cloudflare? I see this for most sites protected by Cloudflare (such as
>> bufferbloat.net), but only when using IPv4:
>> 
>> # sysctl -w net.ipv4.tcp_ecn=1
>> net.ipv4.tcp_ecn = 1
>> # curl -v 1.1.1.1
>> *   Trying 1.1.1.1:80...
>> * TCP_NODELAY set
>> * Connected to 1.1.1.1 (1.1.1.1) port 80 (#0)
>> > GET / HTTP/1.1
>> > Host: 1.1.1.1
>> > User-Agent: curl/7.66.0
>> > Accept: */*
>> >   
>> * Recv failure: Connection reset by peer
>> * Closing connection 0
>> curl: (56) Recv failure: Connection reset by peer
>
> It works for me when repeating your experiment:
>
> $ sysctl -w net.ipv4.tcp_ecn=1
> net.ipv4.tcp_ecn = 1
>
> $ curl -v 1.1.1.1
> * Rebuilt URL to: 1.1.1.1/
> *   Trying 1.1.1.1...
> * TCP_NODELAY set
> * Connected to 1.1.1.1 (1.1.1.1) port 80 (#0)
>> GET / HTTP/1.1
>> Host: 1.1.1.1
>> User-Agent: curl/7.61.1
>> Accept: */*
>> 
> < HTTP/1.1 301 Moved Permanently
> < Date: Fri, 20 Sep 2019 07:19:48 GMT
> < Content-Type: text/html
> < Transfer-Encoding: chunked
> < Connection: keep-alive
> < Location: https://1.1.1.1/
> < Served-In-Seconds: 0.000
> < CF-Cache-Status: HIT
> < Age: 5944
> < Expires: Fri, 20 Sep 2019 11:19:48 GMT
> < Cache-Control: public, max-age=14400
> < Server: cloudflare
> < CF-RAY: 519208830aced891-CPH
> [...]
>  
>  
>> # sysctl -w net.ipv4.tcp_ecn=0
>> net.ipv4.tcp_ecn = 0
>> # curl -v 1.1.1.1
>> *   Trying 1.1.1.1:80...
>> * TCP_NODELAY set
>> * Connected to 1.1.1.1 (1.1.1.1) port 80 (#0)
>> > GET / HTTP/1.1
>> > Host: 1.1.1.1
>> > User-Agent: curl/7.66.0
>> > Accept: */*
>> >   
>> * Mark bundle as not supporting multiuse
>> < HTTP/1.1 301 Moved Permanently
>> < Date: Thu, 19 Sep 2019 17:42:22 GMT
>> < Content-Type: text/html
>> < Transfer-Encoding: chunked
>> < Connection: keep-alive
>> < Location: https://1.1.1.1/
>> < Served-In-Seconds: 0.000
>> < CF-Cache-Status: HIT
>> < Age: 4442
>> < Expires: Thu, 19 Sep 2019 21:42:22 GMT
>> < Cache-Control: public, max-age=14400
>> < Server: cloudflare
>> < CF-RAY: 518d5b13fcfcd43f-HAM
>> < 
>> <html>
>> <head><title>301 Moved Permanently</title></head>
>> <body bgcolor="white">
>> <center><h1>301 Moved Permanently</h1></center>
>> <hr><center>cloudflare-lb</center>
>> </body>
>> </html>
>> * Connection #0 to host 1.1.1.1 left intact
>> 
>> 
>> I've opened a support request with my ISP, but thought I'd ask if anyone
>> else was seeing this? (Is anyone else running with ECN enabled?)
>
> I'm not seeing it, so it might be your ISP?

Yeah, guess I'll get to see if my ISP support knows what ECN is...
Should be fun :P

-Toke

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-09-20  9:41 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-19 17:50 [Bloat] Issue with negotiating ECN with Cloudflare hosts? Toke Høiland-Jørgensen
2019-09-20  7:24 ` Jesper Dangaard Brouer
     [not found]   ` <CAJPywT+Xa9pXpZ66eKR7NOpn8T-Tt_obU6HjShzw=zQCDeudfg@mail.gmail.com>
2019-09-20  9:38     ` Toke Høiland-Jørgensen
2019-09-20  9:41   ` Toke Høiland-Jørgensen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox