Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

running within docker container - packets out returned an error: Operation no permitted #80

Closed
centminmod opened this issue Sep 16, 2019 · 5 comments
Labels

Comments

@centminmod
Copy link

I built lsquic within a Ubuntu 19.04 docker container on CentOS 7 docker host, but when i try

 http_client -s www.google.com  -p /

it just hangs and doesn't return to prompt or output anything

if i run

 http_client -s www.google.com  -p / -L debug

I get 100s of lines with following message

23:16:32.478 [DEBUG] engine: send_packets_out: sent 0 packets
23:16:32.478 [DEBUG] on_write event fires
23:16:32.478 [DEBUG] engine: can send again
23:16:32.478 [DEBUG] event: can send again
23:16:32.478 [DEBUG] engine: batched packet 0 for connection 068A2F1FCD295F2F
23:16:32.478 [DEBUG] engine: batched all outgoing packets for full conn 068A2F1FCD295F2F
23:16:32.478 [INFO] sendto failed: Operation not permitted
23:16:32.478 [DEBUG] cannot send: register on_write event
23:16:32.478 [DEBUG] engine: cannot send packets
23:16:32.478 [DEBUG] event: cannot send packets
23:16:32.478 [DEBUG] engine: packets out returned an error: Operation not permitted
23:16:32.478 [DEBUG] [QUIC:068A2F1FCD295F2F] event: unsent packet 0, size 1200, frame types: PADDING CRYPTO
23:16:32.478 [DEBUG] [QUIC:068A2F1FCD295F2F] sendctl: packet 0 has been delayed
23:16:32.478 [DEBUG] engine: send_packets_out: sent 0 packets

so do I need additional steps for running within a docker container image ?

@centminmod centminmod changed the title running within docker container - packages out returned an error: Operation no permitted running within docker container - packets out returned an error: Operation no permitted Sep 16, 2019
@dtikhonov
Copy link
Contributor

The following works for me on Ubuntu 14:

docker run -it --rm lsquic http_client -s www.google.com -M HEAD -p / -o version=Q046

@centminmod
Copy link
Author

this works

http_client -s www.google.com -M HEAD -p / -o version=Q046
HTTP/1.1 200 OK
date: Wed, 18 Sep 2019 18:09:48 GMT
expires: -1
cache-control: private, max-age=0
content-type: text/html; charset=ISO-8859-1
p3p: CP="This is not a P3P policy! See g.co/p3phelp for more info."
server: gws
x-xss-protection: 0
x-frame-options: SAMEORIGIN
set-cookie: 1P_JAR=2019-09-18-18; expires=Fri, 18-Oct-2019 18:09:48 GMT; path=/; domain=.google.com; SameSite=none
set-cookie: NID=188=IaODhxOd3qVnNei0GPaklMcSc5Ww8cDKCmBWm4APgvg6xKZzIgbt0CLIhu0J9TmfAOUCXH440qB4wqW1E0zOSM9IZ2pUVdNSVRHCzxJdv2_JPHQCfDGO38whdjbSlPYMnH1FUyRe-LWuTZOtxVONbstvAsjBoLKUP9hLTwdk0Zw; expires=Thu, 19-Mar-2020 18:09:48 GMT; path=/; domain=.google.com; HttpOnly
alt-svc: quic=":443"; ma=2592000; v="46,43,39"
accept-ranges: none
vary: Accept-Encoding

this doesn't - incorrect syntax ? as it just hangs there without returning to command prompt

http_client -s www.google.com  -p /

@dtikhonov
Copy link
Contributor

By default, the client uses the highest QUIC version, which is ID-22 or ID-23, depending on the library version you have. www.google.com does not speak this version yet and there is no version negotiation between IETF and Google QUIC (at least it's not supported in the client). Using -o version=Q046 options, you select a version which the Google website does support.

@dtikhonov
Copy link
Contributor

The errors you reported earlier:

23:16:32.478 [INFO] sendto failed: Operation not permitted
23:16:32.478 [DEBUG] cannot send: register on_write event

are likely unrelated to the version problem.

@centminmod
Copy link
Author

thanks for the clarification :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants