Saita Proxy a Ubuntu da Debian, Mataki-mataki
Daga Tawagar Injiniyoyi ta ProxyV4 · Updated:
Saita proxy a Ubuntu a zahiri ƙananan saituttuka ne guda huɗu, domin Linux ba ta da maɓalli guda ɗaya na proxy. Shell ɗinka na karanta environment variables, APT na karanta babban fayil ɗin saitin kansa, ayyukan systemd na karanta unit drop-ins, kuma teburin GNOME na amfani da gsettings. Saita ɓangarorin da kake amfani da su kawai; misalan lambobin da ke ƙasa suna amfani da ProxyV4 HTTP(S) proxy tare da sunan mai amfani da kalmar sirri.
export http_proxy=http://user:pass@ip:port https_proxy=http://user:pass@ip:port- 1 IP$ 1.85
- 3+ IPs$ 1.70
- 10+ IPs$ 1.60
- 25+ IPs$ 1.50
- 50+ IPs$ 1.40
- 100+ IPs$ 1.30
- 200+ IPs$ 1.20
- 500+ IPs$ 1.10
- 1 IP$ 1.85
- 3+ IPs$ 1.70
- 10+ IPs$ 1.60
- 25+ IPs$ 1.50
- 50+ IPs$ 1.40
- 100+ IPs$ 1.30
- 200+ IPs$ 1.20
- 500+ IPs$ 1.10
Saitin proxy na APT tare da sunan mai amfani da kalmar sirri
Don sa apt ta yi amfani da proxy mai tantancewa, ƙirƙiri /etc/apt/apt.conf.d/80proxy tare da sunan mai amfani da kalmar sirri a cikin URL ɗin proxy. APT tana karanta wannan fayil a kowane gudu, tare da ko ba tare da sudo ba, kuma tana yin watsi da sauye-sauyen shell ɗinka:
sudo tee /etc/apt/apt.conf.d/80proxy > /dev/null << 'EOF'
Acquire::http::Proxy "http://USER:PASS@IP:PORT/";
Acquire::https::Proxy "http://USER:PASS@IP:PORT/";
EOF
sudo chmod 600 /etc/apt/apt.conf.d/80proxy
# duba abin da APT za ta yi amfani da shi, sannan gwada shi
apt-config dump | grep -i proxy
sudo apt updateDole ne kowane layi ya ƙare da semicolon, kuma kalmar sirri da ke ɗauke da @, : ko # dole ne a yi mata percent-encoding (@ yana zama %40). Idan apt update ta tsaya a 407 Proxy Authentication Required, bayanan shiga da ke cikin fayil ɗin ba daidai ba ne; duba shafin 407.
APT ta hanyar proxy na SOCKS5
Sabbin fitarwar APT (Ubuntu 18.04 da na gaba) suna karɓar URL na SOCKS5 a cikin maɓallan guda ɗaya, misali Acquire::http::Proxy "socks5h://USER:PASS@IP:PORT";. Dole ne odar ta kasance a yanayin SOCKS5 ko dual mode, wanda hakan ya cire IP na Vietnam (HTTP kawai). Idan sigar APT ɗinka ta ƙi karɓar tsarin, yi amfani da tsarin HTTP da ke sama.
Proxy don umarni ɗaya kawai
Don yin gwaji ba tare da taɓa saitin ba, shigar da zaɓin a layin umarni: sudo apt -o Acquire::http::Proxy="http://USER:PASS@IP:PORT/" update. Ba a adana komai ba.
Wanne fayil ne ke sarrafa wane shiri
Yawancin rahotannin "an yi watsi da proxy dina" a Linux suna faruwa ne sakamakon saka ƙima mai daidai a wurin da ba daidai ba. Dokoki biyu ne ke bayyana kusan duka: ta asali sudo tana watsar da muhallin mai amfani, kuma ayyukan systemd ba sa taɓa karanta ~/.bashrc.
| Mataki | Inda ake saita shi | Wanda ke karanta shi | Tsawon lokaci |
|---|---|---|---|
| Login shells | ~/.bashrc ko /etc/profile.d/proxy.sh | curl, wget, python, git, node | Kowane sabon login shell |
| Zaman PAM | /etc/environment | Duk zaman masu amfani | Har bayan sake kunnawa |
| APT | /etc/apt/apt.conf.d/80proxy | apt update, apt install | Na dindindin, don APT |
| Rukunonin systemd | /etc/systemd/system/<svc>.service.d/proxy.conf | Docker daemon, ayyukan kanku | Bayan daemon-reload da sake kunnawa |
Sauye-sauyen shell don curl, wget da scripts
Bayyana sauye-sauyen a cikin ƙananan baƙaƙe da manyan baƙaƙe: curl da wget suna duba http_proxy, yayin da sauran runtimes ke duba HTTP_PROXY kawai. Jerin no_proxy yana cire loopback da adiresoshin sirri daga proxy.
# /etc/profile.d/proxy.sh - shells da kayan aikin CLI
sudo tee /etc/profile.d/proxy.sh > /dev/null << 'EOF'
export http_proxy="http://USER:PASS@IP:PORT"
export https_proxy="http://USER:PASS@IP:PORT"
export HTTP_PROXY="http://USER:PASS@IP:PORT"
export HTTPS_PROXY="http://USER:PASS@IP:PORT"
export no_proxy="localhost,127.0.0.1,::1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16"
export NO_PROXY="$no_proxy"
EOF
source /etc/profile.d/proxy.shYi amfani da percent-encode don haruffa na musamman a cikin kalmar sirri a nan ma. APT tana da nata fayil ɗin, wanda aka bayyana a sama.
Ayyukan da systemd ke sarrafawa
Daemon ɗin da systemd ta fara yana ganin sauye-sauyen da aka ayyana a cikin unit ɗinsa kawai. Saka su a cikin drop-in, sake lodi, sannan sake kunna sabis ɗin. Jagoran Docker ya yi cikakken bayani kan Docker daemon da kwantena.
# /etc/systemd/system/<svc>.service.d/proxy.conf
[Service]
Environment="HTTP_PROXY=http://USER:PASS@IP:PORT"
Environment="HTTPS_PROXY=http://USER:PASS@IP:PORT"
Environment="NO_PROXY=localhost,127.0.0.1"
sudo systemctl daemon-reload
sudo systemctl restart <svc>sudo, sabobin da aka raba da kwamfutar tebur
- sudo: gudanar da
sudo -E curl ...don riƙe sauye-sauyen da ka fitar, ko sanya shi ya zama na dindindin tare daDefaults env_keep += "http_proxy https_proxy HTTP_PROXY HTTPS_PROXY no_proxy NO_PROXY"da aka ƙara ta hanyarsudo visudo. - Bayanan shiga a na'urori masu amfani da yawa: waɗannan fayiloli suna ɗauke da kalmar sirri ta proxy a sarari ba tare da ɓoyewa ba. Kulle su, misali
sudo chmod 600 /etc/apt/apt.conf.d/80proxy. - GNOME desktop: Settings → Network → Network Proxy → Manual, ko
gsettings set org.gnome.system.proxy mode 'manual'tare da maɓallan host da port a ƙarƙashinorg.gnome.system.proxy.http.
Gwaji da magance matsala
Bayan shigar da bayanan martaba, curl -s https://api.ipify.org ya kamata ya nuna IP na proxy maimakon adireshin sabar da kanta. Don samun cikakken rahoto kan ƙasa da mai shi, liƙa IP ɗin a cikin binciken IP. Jagororin curl da Python requests suna nuna wasu hanyoyin daban ga kowane umarni idan ba ka son sanya proxy ga duk shell ɗin.
- `407 Proxy Authentication Required`: bayanan shiga ba daidai ba ne ko kuma akwai harafi na musamman da ba a yi masa encoding ba a cikin kalmar sirri; duba shafin 407.
- apt tana aiki ne kawai tare da sudo -E: fayil ɗin 80proxy ya ɓace ko yana da kuskuren rubutu (kowane layi yana ƙarewa da semicolon).
- Haɗin yana tsayawa: firewall na sabar na iya toshe damar fita zuwa mashigar proxy; duba dalilan firewall.
Mataki bayan mataki
- 1
Ba wa APT nata fayil ɗin proxy
Saboda sudo apt update tana yin watsi da sauye-sauyen shell ɗinka, ƙirƙiri /etc/apt/apt.conf.d/80proxy tare da Acquire::http::Proxy da Acquire::https::Proxy, sannan duba shi da apt-config dump.
- 2
Rubuta /etc/profile.d/proxy.sh
Fitar da http_proxy, https_proxy da no_proxy a cikin ƙananan baƙaƙe da kuma HTTP_PROXY, HTTPS_PROXY da NO_PROXY a cikin manyan baƙaƙe domin kowane kayan aikin CLI ya same su.
- 3
Ƙara systemd drop-ins inda ake buƙata
Ga kowane daemon da dole ne ya yi amfani da proxy, ƙirƙiri drop-in na proxy.conf tare da layukan Environment, sannan ka gudanar da daemon-reload kuma ka sake kunna shi.
- 4
Tabbatar da IP ɗin fita
Gudanar da
source /etc/profile.d/proxy.shsannancurl -s https://api.ipify.org; sakamakon da zai fito ya zama IP ɗin proxy ɗinka.
Tambayoyi da aka fi yi
Shin da gaske ina buƙatar duka http_proxy da HTTP_PROXY?
Ee. Wasu kayan aiki kamar curl da wget suna duba sunan da ke da ƙananan haruffa, wasu kuma manyan haruffa kawai. Saita duka biyun yana hana rashin daidaiton aiki.
Me ya sa sudo apt update ba ya amfani da proxy na?
sudo yana sake saita muhalli sai dai idan ka saka -E. Fayil a cikin /etc/apt/apt.conf.d/ yana sa APT ya yi amfani da proxy ko ta yaya.
Ta yaya zan saita proxy a cikin tsarin tebur na Ubuntu GUI?
Bude Settings → Network → Network Proxy sannan ka zaɓi Manual, ko saita shi da gsettings a ƙarƙashin org.gnome.system.proxy.
Shin static proxy yana da amfani a kan uwar garken Linux?
Ee, lokacin da wani API na nesa ko abokin tarayya ya sanya IP ɗinka a cikin allowlist. Keɓaɓɓen IPv4 yana riƙe adireshi ɗaya muddin kana sabunta shi, don haka bayanin allowlist ɗin yana ci gaba da aiki.
Tushe
Kafaffen-IP proxies don sabobin da rubutun aiki
HTTP(S) tare da sunan mai amfani da kalmar sirri, bandwidth mara iyaka akan keɓaɓɓen IPv4, da kuma adireshi ɗaya a kowane sabuntawa.
Kwatanta farashi