starred/zapret.installer
1
0
Fork 0
mirror of https://github.com/Snowy-Fluffy/zapret.installer.git synced 2026-07-16 06:03:47 +03:00
Code Issues 20 Packages Projects Releases Wiki Activity

Интернет не работает #81

New Issue
Closed
opened 2026-02-05 19:04:51 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-05 19:04:51 +03:00
Owner
Copy Link

Originally created by @TimeStop34 on GitHub (Jan 11, 2026).

Чзх? Я просто врубаю запрет, да даже с нулевым листом и с какой-либо стратегией - минус интернет.

Причем еще и сам скрипт не хочет с ним работать, просто:

  1. Я врубаю, илиzapret(zapret.installer) сам врубает его при выборе стратегии или т.д.
  2. Нахуй сноситься инет
  3. zapret(zapret.installer) не че не выводит
  4. Мне приходиться его вырубать через systemctl stop zapret
Originally created by @TimeStop34 on GitHub (Jan 11, 2026). Чзх? Я просто врубаю запрет, да даже с нулевым листом и с какой-либо стратегией - минус интернет. Причем еще и сам скрипт не хочет с ним работать, просто: 1. Я врубаю, или`zapret`(zapret.installer) сам врубает его при выборе стратегии или т.д. 2. Нахуй сноситься инет 3. `zapret`(zapret.installer) не че не выводит 4. Мне приходиться его вырубать через `systemctl stop zapret`
OVERLORD commented 2026-02-05 19:04:54 +03:00
Author
Owner
Copy Link

@n00zJS6tl0 commented on GitHub (Jan 11, 2026):

@TimeStop34 телепатия сломалась, скинь хотя бы на чем сидишь и лог:
hostnamectl && sudo journalctl --no-pager -S today -u zapret.service

@n00zJS6tl0 commented on GitHub (Jan 11, 2026): @TimeStop34 телепатия сломалась, скинь хотя бы на чем сидишь и лог: `hostnamectl && sudo journalctl --no-pager -S today -u zapret.service`
OVERLORD commented 2026-02-05 19:04:56 +03:00
Author
Owner
Copy Link

@TimeStop34 commented on GitHub (Jan 11, 2026):

Спасибо что хоть комманду скинул, а то так не ебу.
Вообще сижу на Arch kv6.18.4(kernel version) x86-64
А лог:

янв 11 11:19:38 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:19:38 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:22:00 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:22:00 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:22:00 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:22:00 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:22:01 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:22:01 timestop34home systemd[1]: Starting zapret.service...
янв 11 11:22:01 timestop34home zapret[80979]: WARNING !!! --ipset parameter is present
янв 11 11:22:01 timestop34home zapret[80979]: It's OK if you only specialize already redirected traffic and also process the rest.
янв 11 11:22:01 timestop34home zapret[80979]: If you redirect port X to process several IPs from the list and do nothing with the rest - IT'S VERY INEFFECTIVE !
янв 11 11:22:01 timestop34home zapret[80979]: Kernel ipsets should be used instead. Write custom scripts and filter IPs in kernel.
янв 11 11:22:01 timestop34home zapret[80979]: Starting daemon 3: /opt/zapret/nfq/nfqws --user=tpws --dpi-desync-fwmark=0x40000000 --qnum=200
янв 11 11:22:01 timestop34home zapret[80979]: --filter-udp=443 --hostlist=/opt/zapret/ipset/zapret-hosts-user.txt --dpi-desync=fake --dpi-desync-repeats=6 --dpi-desync-fake-quic=/opt/zapret/files/fake/quic_initial_www_google_com.bin --new ^
янв 11 11:22:01 timestop34home zapret[80979]: --filter-udp=19294-19344,50000-50100 --filter-l7=discord,stun --dpi-desync=fake --dpi-desync-fake-discord=/opt/zapret/files/fake/quic_initial_www_google_com.bin --dpi-desync-fake-stun=/opt/zapret/files/fake/quic_initial_www_google_com.bin --dpi-desync-repeats=6 --new ^
янв 11 11:22:01 timestop34home zapret[80979]: --filter-tcp=2053,2083,2087,2096,8443 --hostlist-domains=discord.media --dpi-desync=multisplit --dpi-desync-split-seqovl=652 --dpi-desync-split-pos=2 --dpi-desync-split-seqovl-pattern=/opt/zapret/files/fake/tls_clienthello_www_google_com.bin --new ^
янв 11 11:22:01 timestop34home zapret[80979]: --filter-tcp=443 --hostlist=/opt/zapret/ipset/zapret-hosts-user.txt --ip-id=zero --dpi-desync=multisplit --dpi-desync-split-seqovl=652 --dpi-desync-split-pos=2 --dpi-desync-split-seqovl-pattern=/opt/zapret/files/fake/tls_clienthello_www_google_com.bin --new ^
янв 11 11:22:01 timestop34home zapret[80979]: --filter-tcp=80,443 --hostlist=/opt/zapret/ipset/zapret-hosts-user.txt --dpi-desync=multisplit --dpi-desync-split-seqovl=652 --dpi-desync-split-pos=2 --dpi-desync-split-seqovl-pattern=/opt/zapret/files/fake/tls_clienthello_www_google_com.bin --new ^
янв 11 11:22:01 timestop34home zapret[80979]: --filter-udp=443 --dpi-desync=fake --dpi-desync-repeats=6 --dpi-desync-fake-quic=/opt/zapret/files/fake/quic_initial_www_google_com.bin --new ^
янв 11 11:22:01 timestop34home zapret[80979]: --filter-tcp=80,443,1024-65535 --ipset=/opt/zapret/ipset/ipset-game.txt  --dpi-desync=multisplit --dpi-desync-split-seqovl=652 --dpi-desync-split-pos=2 --dpi-desync-split-seqovl-pattern=/opt/zapret/files/fake/tls_clienthello_www_google_com.bin --new ^
янв 11 11:22:01 timestop34home zapret[80979]: --filter-udp=1024-65535 --ipset=/opt/zapret/ipset/ipset-game.txt  --dpi-desync=fake --dpi-desync-autottl=2 --dpi-desync-repeats=12 --dpi-desync-any-protocol=1 --dpi-desync-fake-unknown-udp=/opt/zapret/files/fake/quic_initial_www_google_com.bin --dpi-desync-cutoff=n2
янв 11 11:22:01 timestop34home zapret[80979]: Applying iptables
янв 11 11:22:01 timestop34home zapret[80979]: Creating ip list table (firewall type iptables)
янв 11 11:22:01 timestop34home zapret[81021]: setting high oom kill priority
янв 11 11:22:01 timestop34home zapret[81021]: reloading ipset backend (no-update)
янв 11 11:22:01 timestop34home zapret[80979]: Inserting iptables rule for nfqws postrouting (qnum 200) : -p tcp -m multiport --dports 80,443,2053,2083,2087,2096,8443,1024:65535 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:9
янв 11 11:22:01 timestop34home zapret[80979]: Inserting iptables rule for nfqws input+forward (qnum 200) : -p tcp -m multiport --sports 80,443,2053,2083,2087,2096,8443,1024:65535  -m connbytes --connbytes-dir=reply --connbytes-mode=packets --connbytes 1:3
янв 11 11:22:01 timestop34home zapret[80979]: Inserting iptables rule for nfqws postrouting (qnum 200) : -p udp -m multiport --dports 443,19294:19344,50000:50100,1024:65535 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:9
янв 11 11:22:01 timestop34home zapret[81075]: net.netfilter.nf_conntrack_tcp_be_liberal = 1
янв 11 11:22:01 timestop34home systemd[1]: Started zapret.service.
янв 11 11:22:50 timestop34home systemd[1]: Stopping zapret.service...
янв 11 11:22:50 timestop34home zapret[81466]: Stopping daemon 3: /opt/zapret/nfq/nfqws
янв 11 11:22:50 timestop34home zapret[81466]: Clearing iptables
янв 11 11:22:50 timestop34home zapret[81466]: Deleting iptables rule for nfqws postrouting (qnum 200) : -p tcp -m multiport --dports 80,443,2053,2083,2087,2096,8443,1024:65535 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:9
янв 11 11:22:50 timestop34home zapret[81466]: Deleting iptables rule for nfqws input+forward (qnum 200) : -p tcp -m multiport --sports 80,443,2053,2083,2087,2096,8443,1024:65535  -m connbytes --connbytes-dir=reply --connbytes-mode=packets --connbytes 1:3
янв 11 11:22:51 timestop34home zapret[81466]: Deleting iptables rule for nfqws postrouting (qnum 200) : -p udp -m multiport --dports 443,19294:19344,50000:50100,1024:65535 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:9
янв 11 11:22:51 timestop34home zapret[81538]: net.netfilter.nf_conntrack_tcp_be_liberal = 0
янв 11 11:22:51 timestop34home systemd[1]: zapret.service: Deactivated successfully.
янв 11 11:22:51 timestop34home systemd[1]: Stopped zapret.service.
янв 11 11:22:51 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:22:51 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:22:51 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:22:51 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:23:21 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:23:21 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:23:25 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:23:25 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:37:19 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
янв 11 11:37:19 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
@TimeStop34 commented on GitHub (Jan 11, 2026): Спасибо что хоть комманду скинул, а то так не ебу. Вообще сижу на Arch kv6.18.4(kernel version) x86-64 А лог: ``` янв 11 11:19:38 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:19:38 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:22:00 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:22:00 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:22:00 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:22:00 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:22:01 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:22:01 timestop34home systemd[1]: Starting zapret.service... янв 11 11:22:01 timestop34home zapret[80979]: WARNING !!! --ipset parameter is present янв 11 11:22:01 timestop34home zapret[80979]: It's OK if you only specialize already redirected traffic and also process the rest. янв 11 11:22:01 timestop34home zapret[80979]: If you redirect port X to process several IPs from the list and do nothing with the rest - IT'S VERY INEFFECTIVE ! янв 11 11:22:01 timestop34home zapret[80979]: Kernel ipsets should be used instead. Write custom scripts and filter IPs in kernel. янв 11 11:22:01 timestop34home zapret[80979]: Starting daemon 3: /opt/zapret/nfq/nfqws --user=tpws --dpi-desync-fwmark=0x40000000 --qnum=200 янв 11 11:22:01 timestop34home zapret[80979]: --filter-udp=443 --hostlist=/opt/zapret/ipset/zapret-hosts-user.txt --dpi-desync=fake --dpi-desync-repeats=6 --dpi-desync-fake-quic=/opt/zapret/files/fake/quic_initial_www_google_com.bin --new ^ янв 11 11:22:01 timestop34home zapret[80979]: --filter-udp=19294-19344,50000-50100 --filter-l7=discord,stun --dpi-desync=fake --dpi-desync-fake-discord=/opt/zapret/files/fake/quic_initial_www_google_com.bin --dpi-desync-fake-stun=/opt/zapret/files/fake/quic_initial_www_google_com.bin --dpi-desync-repeats=6 --new ^ янв 11 11:22:01 timestop34home zapret[80979]: --filter-tcp=2053,2083,2087,2096,8443 --hostlist-domains=discord.media --dpi-desync=multisplit --dpi-desync-split-seqovl=652 --dpi-desync-split-pos=2 --dpi-desync-split-seqovl-pattern=/opt/zapret/files/fake/tls_clienthello_www_google_com.bin --new ^ янв 11 11:22:01 timestop34home zapret[80979]: --filter-tcp=443 --hostlist=/opt/zapret/ipset/zapret-hosts-user.txt --ip-id=zero --dpi-desync=multisplit --dpi-desync-split-seqovl=652 --dpi-desync-split-pos=2 --dpi-desync-split-seqovl-pattern=/opt/zapret/files/fake/tls_clienthello_www_google_com.bin --new ^ янв 11 11:22:01 timestop34home zapret[80979]: --filter-tcp=80,443 --hostlist=/opt/zapret/ipset/zapret-hosts-user.txt --dpi-desync=multisplit --dpi-desync-split-seqovl=652 --dpi-desync-split-pos=2 --dpi-desync-split-seqovl-pattern=/opt/zapret/files/fake/tls_clienthello_www_google_com.bin --new ^ янв 11 11:22:01 timestop34home zapret[80979]: --filter-udp=443 --dpi-desync=fake --dpi-desync-repeats=6 --dpi-desync-fake-quic=/opt/zapret/files/fake/quic_initial_www_google_com.bin --new ^ янв 11 11:22:01 timestop34home zapret[80979]: --filter-tcp=80,443,1024-65535 --ipset=/opt/zapret/ipset/ipset-game.txt --dpi-desync=multisplit --dpi-desync-split-seqovl=652 --dpi-desync-split-pos=2 --dpi-desync-split-seqovl-pattern=/opt/zapret/files/fake/tls_clienthello_www_google_com.bin --new ^ янв 11 11:22:01 timestop34home zapret[80979]: --filter-udp=1024-65535 --ipset=/opt/zapret/ipset/ipset-game.txt --dpi-desync=fake --dpi-desync-autottl=2 --dpi-desync-repeats=12 --dpi-desync-any-protocol=1 --dpi-desync-fake-unknown-udp=/opt/zapret/files/fake/quic_initial_www_google_com.bin --dpi-desync-cutoff=n2 янв 11 11:22:01 timestop34home zapret[80979]: Applying iptables янв 11 11:22:01 timestop34home zapret[80979]: Creating ip list table (firewall type iptables) янв 11 11:22:01 timestop34home zapret[81021]: setting high oom kill priority янв 11 11:22:01 timestop34home zapret[81021]: reloading ipset backend (no-update) янв 11 11:22:01 timestop34home zapret[80979]: Inserting iptables rule for nfqws postrouting (qnum 200) : -p tcp -m multiport --dports 80,443,2053,2083,2087,2096,8443,1024:65535 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:9 янв 11 11:22:01 timestop34home zapret[80979]: Inserting iptables rule for nfqws input+forward (qnum 200) : -p tcp -m multiport --sports 80,443,2053,2083,2087,2096,8443,1024:65535 -m connbytes --connbytes-dir=reply --connbytes-mode=packets --connbytes 1:3 янв 11 11:22:01 timestop34home zapret[80979]: Inserting iptables rule for nfqws postrouting (qnum 200) : -p udp -m multiport --dports 443,19294:19344,50000:50100,1024:65535 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:9 янв 11 11:22:01 timestop34home zapret[81075]: net.netfilter.nf_conntrack_tcp_be_liberal = 1 янв 11 11:22:01 timestop34home systemd[1]: Started zapret.service. янв 11 11:22:50 timestop34home systemd[1]: Stopping zapret.service... янв 11 11:22:50 timestop34home zapret[81466]: Stopping daemon 3: /opt/zapret/nfq/nfqws янв 11 11:22:50 timestop34home zapret[81466]: Clearing iptables янв 11 11:22:50 timestop34home zapret[81466]: Deleting iptables rule for nfqws postrouting (qnum 200) : -p tcp -m multiport --dports 80,443,2053,2083,2087,2096,8443,1024:65535 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:9 янв 11 11:22:50 timestop34home zapret[81466]: Deleting iptables rule for nfqws input+forward (qnum 200) : -p tcp -m multiport --sports 80,443,2053,2083,2087,2096,8443,1024:65535 -m connbytes --connbytes-dir=reply --connbytes-mode=packets --connbytes 1:3 янв 11 11:22:51 timestop34home zapret[81466]: Deleting iptables rule for nfqws postrouting (qnum 200) : -p udp -m multiport --dports 443,19294:19344,50000:50100,1024:65535 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:9 янв 11 11:22:51 timestop34home zapret[81538]: net.netfilter.nf_conntrack_tcp_be_liberal = 0 янв 11 11:22:51 timestop34home systemd[1]: zapret.service: Deactivated successfully. янв 11 11:22:51 timestop34home systemd[1]: Stopped zapret.service. янв 11 11:22:51 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:22:51 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:22:51 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:22:51 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:23:21 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:23:21 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:23:25 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:23:25 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:37:19 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. янв 11 11:37:19 timestop34home systemd[1]: /usr/lib/systemd/system/zapret.service:10: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. ```
OVERLORD commented 2026-02-05 19:04:57 +03:00
Author
Owner
Copy Link

@n00zJS6tl0 commented on GitHub (Jan 11, 2026):

@TimeStop34 попробуй поставить пакет iptables-nft
Если не прокатит, то удали прошлый и попробуй установить iptables

@n00zJS6tl0 commented on GitHub (Jan 11, 2026): @TimeStop34 попробуй поставить пакет `iptables-nft` Если не прокатит, то удали прошлый и попробуй установить `iptables`
OVERLORD commented 2026-02-05 19:04:57 +03:00
Author
Owner
Copy Link

@TimeStop34 commented on GitHub (Jan 12, 2026):

@TimeStop34 попробуй поставить пакет iptables-nft

Вроде как помогло - теперь весь инет не падает, скорее всего теперь если что-то не грузиться - проблема стратегии.
Спасибо

@TimeStop34 commented on GitHub (Jan 12, 2026): > @TimeStop34 попробуй поставить пакет `iptables-nft` Вроде как помогло - теперь весь инет не падает, скорее всего теперь если что-то не грузиться - проблема стратегии. Спасибо
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
invalid
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/zapret.installer#81
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?