Nikolay, I made more research on the issue. It turns out that I had two different problems: 1) "Connecting to nix.org (nix.org)|160.153.18.102|:80... failed:" - was the misconfigured http_proxy. Setting it correctly makes wget work. By nix.org I mean nixos.org. nix.org is a valid name too, site provides some content. 2) "FailedConnectionException2 "raw.githubusercontent.com" 443 True getProtocolByName: does not exist (no such protocol name: tcp)" message is actually produced by `stack` tool (Haskell package builder). This problem still exists. I think it is some corner case, related to gethostbyname() configuration.
I will try to contact Stack maintainers. Thanks for quick response! Sergey 2016-09-22 12:21 GMT+03:00 Nikolay Amiantov <[email protected]>: > Hi! > > This is a strange problem you have! I tested right now that at least in > `steam.env` networking works: > > nixpkgs git:(stable) ✗ TERM=xterm nix-shell -A steam.env > steam-chrootenv:ab@abbradarbook:~/nixpkgs$ > /run/current-system/sw/bin/curl nixos.org > <!DOCTYPE html> > > <html lang="en"> > > <head> > <title>NixOS Linux</title> > ... > > You seem to have tried "nix.org" instead of "nixos.org" which is indeed > unreachable for me -- just in case, try the latter instead. > > On 09/22/2016 12:04 PM, Sergey Mironov wrote: >> Hi! I tried to use buildFHSUserEnv to create chroot environment to >> build some tricky BuildRoot project. The function seems to do the >> Right Thing in general except for network behavior: calling wget from >> this environment returns following >> >> buildroot-env-chrootenv:smironov@ww2:~/proj/ks/kss-linux-demo$ >> LANG=C wget nix.org >> --2016-09-22 11:56:53-- http://nix.org/ >> Resolving nix.org (nix.org)... 160.153.18.102 >> Connecting to nix.org (nix.org)|160.153.18.102|:80... failed: >> Connection refused. >> >> Calling BuildRoot-powered Makefile (which requires access to the >> network) results in following error: >> >> FailedConnectionException2 "raw.githubusercontent.com" 443 True >> getProtocolByName: does not exist (no such protocol name: tcp) >> >> So I am guessing that the possible problem lies somewhere in the TCP >> stack setup. Is it a known issue? How can I turn the network on? >> >> Regards, >> Sergey >> _______________________________________________ >> nix-dev mailing list >> [email protected] >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> > > > -- > Nikolay. _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
