You are not logged in.
There is absolutely no reason for blocking, this shouldn't happen! Can you post a traceroute or detail how access is denied?
To avoid censorship and blocks to the Internet the Devuan website is also accessible using Tor at the address http://devuanzuwu3xoqwp.onion
traceroute to 152.228.204.144 (152.228.204.144), 30 hops max, 48 byte packets
1 * * *
2 188.254.25.224 (188.254.25.224) 14.095 ms 14.161 ms 14.182 ms
3 87.226.146.100 (87.226.146.100) 14.197 ms 15.132 ms 14.830 ms
4 ae40.stkm-cr4.intl.ip.rostelecom.ru (217.107.67.31) 47.212 ms 188.128.126.81 (188.128.126.81) 43.109 ms 43.410 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 be105.gra-g1-nc5.fr.eu (213.186.32.212) 70.879 ms 74.580 ms 76.394 ms
10 * * *
11 be50-7.gra-3b-a9.fr.eu (37.187.231.92) 89.068 ms be50-5.gra-3b-a9.fr.eu (37.187.231.90) 94.988 ms be50-5.gra-3a-a9.fr.eu (37.187.231.86) 95.063 ms
12 nardoo.devuan.org (37.187.145.27)!!!!!!!!!!!! 80.985 ms 82.136 ms 82.182 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
There is no access to pkgmaster.devuan.org, dev1galaxy.org from the territory of the Russian Federation. Please provide access to these resources. Please explain the reason for blocking!
Ok, comrade!
I send my and your information to Debian bug report.
Thank you for your comment!
Hello, comrades!
I solve issue with use jitterentropy-rngd package after installation. Developers, Please add this code to script /etc/init.d/jitterentropy-rngd for solve current issue with this service:
if [ ! $(lsmod | grep jitterentropy_rng) ]; then
modprobe jitterentropy-rng
echo "Sucess load jitterentropy_rng module..."
if [ ! $(cat /etc/modules | grep jitterentropy_rng) ]; then
echo "jitterentropy_rng" >> /etc/modules
echo "Sucess add module jitterentropy_rng for autoload by start system..."
fi
fi
do_restart()
{
start-stop-daemon --stop --quiet --retry=TERM/2/KILL/5 --pidfile $PIDFILE --exec $DAEMON
start-stop-daemon --start --quiet --retry=TERM/2/KILL/5 --pidfile $PIDFILE --exec $DAEMON
}
do_start()
{
start-stop-daemon --start --quiet --retry=TERM/2/KILL/5 --pidfile $PIDFILE --exec $DAEMON
}
do_stop()
{
start-stop-daemon --stop --quiet --retry=TERM/2/KILL/5 --pidfile $PIDFILE --exec $DAEMON
}
Please repack installation package jitterentropy-rngd with this code!
$ dpkg -L netbase /. /etc /etc/protocols /etc/rpc /etc/services /usr /usr/share /usr/share/doc /usr/share/doc/netbase /usr/share/doc/netbase/changelog.gz /usr/share/doc/netbase/copyright $ apt-file search /etc/protocols netbase: /etc/protocols $
It's right there.
I know about package netbase.
I repeat FOR YOU again: after install netbase package file /etc/protocols not found!!!
I have installed netbase package without file /etc/protocols.
I try remove file /etc/protocols and reinstall netbase package, i have results: file /etc/protocols not found after reinstall netbase package.
Please fix this error with install netbase package!!!
I not use nftables, i use iptables & etc.
You not solve this problem!
Hello everybody!
The /etc/ directory does not contain the protocols file, which means that the ebtables utility cannot be used correctly. To fix this error, add this file (protocols) with the following content:
# Internet (IP) protocols
#
# Updated from http://www.iana.org/assignments/protocol-numbers and other
# sources.
# New protocols will be added on request if they have been officially
# assigned by IANA and are not historical.
# If you need a huge list of used numbers please install the nmap package.
ip 0 IP # internet protocol, pseudo protocol number
hopopt 0 HOPOPT # IPv6 Hop-by-Hop Option [RFC1883]
icmp 1 ICMP # internet control message protocol
igmp 2 IGMP # Internet Group Management
ggp 3 GGP # gateway-gateway protocol
ipencap 4 IP-ENCAP # IP encapsulated in IP (officially ``IP'')
st 5 ST # ST datagram mode
tcp 6 TCP # transmission control protocol
egp 8 EGP # exterior gateway protocol
igp 9 IGP # any private interior gateway (Cisco)
pup 12 PUP # PARC universal packet protocol
udp 17 UDP # user datagram protocol
hmp 20 HMP # host monitoring protocol
xns-idp 22 XNS-IDP # Xerox NS IDP
rdp 27 RDP # "reliable datagram" protocol
iso-tp4 29 ISO-TP4 # ISO Transport Protocol class 4 [RFC905]
dccp 33 DCCP # Datagram Congestion Control Prot. [RFC4340]
xtp 36 XTP # Xpress Transfer Protocol
ddp 37 DDP # Datagram Delivery Protocol
idpr-cmtp 38 IDPR-CMTP # IDPR Control Message Transport
ipv6 41 IPv6 # Internet Protocol, version 6
ipv6-route 43 IPv6-Route # Routing Header for IPv6
ipv6-frag 44 IPv6-Frag # Fragment Header for IPv6
idrp 45 IDRP # Inter-Domain Routing Protocol
rsvp 46 RSVP # Reservation Protocol
gre 47 GRE # General Routing Encapsulation
esp 50 IPSEC-ESP # Encap Security Payload [RFC2406]
ah 51 IPSEC-AH # Authentication Header [RFC2402]
skip 57 SKIP # SKIP
ipv6-icmp 58 IPv6-ICMP # ICMP for IPv6
ipv6-nonxt 59 IPv6-NoNxt # No Next Header for IPv6
ipv6-opts 60 IPv6-Opts # Destination Options for IPv6
rspf 73 RSPF CPHB # Radio Shortest Path First (officially CPHB)
vmtp 81 VMTP # Versatile Message Transport
eigrp 88 EIGRP # Enhanced Interior Routing Protocol (Cisco)
ospf 89 OSPFIGP # Open Shortest Path First IGP
ax.25 93 AX.25 # AX.25 frames
ipip 94 IPIP # IP-within-IP Encapsulation Protocol
etherip 97 ETHERIP # Ethernet-within-IP Encapsulation [RFC3378]
encap 98 ENCAP # Yet Another IP encapsulation [RFC1241]
# 99 # any private encryption scheme
pim 103 PIM # Protocol Independent Multicast
ipcomp 108 IPCOMP # IP Payload Compression Protocol
vrrp 112 VRRP # Virtual Router Redundancy Protocol [RFC5798]
l2tp 115 L2TP # Layer Two Tunneling Protocol [RFC2661]
isis 124 ISIS # IS-IS over IPv4
sctp 132 SCTP # Stream Control Transmission Protocol
fc 133 FC # Fibre Channel
mobility-header 135 Mobility-Header # Mobility Support for IPv6 [RFC3775]
udplite 136 UDPLite # UDP-Lite [RFC3828]
mpls-in-ip 137 MPLS-in-IP # MPLS-in-IP [RFC4023]
manet 138 # MANET Protocols [RFC5498]
hip 139 HIP # Host Identity Protocol
shim6 140 Shim6 # Shim6 Protocol [RFC5533]
wesp 141 WESP # Wrapped Encapsulating Security Payload
rohc 142 ROHC # Robust Header Compression
@Eaglet,
you might want to read man hwclock more carefullly, and then pay special attention to the documentation of the --show option, which clearly states, in so many words:The time shown is always in local time, even if you keep your Hardware Clock in UTC.
The options --utc and --localtime are for you to tell about time basis of your clock. The program then presents the clock reading in ISO 8601 format local time with respect to that basis.
1. UTC time should end at +00:00, not as it is now +xx:00. Local time should end at +/-xx:00.
2. I did not change the settings in the BIOS, hwclock itself set the time in UTC in the BIOS. This should not be the case, so that changes are made to the system without the user's participation.
3. See about ISO 8601 https://en.wikipedia.org/wiki/ISO_8601#Times
4. The above suggests that one of the developers of hwclock got stoned with marijuana.And you repeat the nonsense of a crazy developer hwclock.
Are you saying that iptables decrements the given option code by 1?
Or is it that you find it confusing that the --tcp-option parameter rejects code 0?
Rejecting option code 0 is of course consistent with the code table, since code 0 is an "end of options list" marker, and not an option code in itself.
1. What I wanted to say, I have already said here.
2. There are standards that are accepted as a standard and these standards should be followed, and not "break" user dependencies.
3. I'm not a girl to be embarrassed about.
4. The range of TCP options should be between 0 and 254, not as it is now from 1 to 255.
Do you know when and where this change took place? Was it in debian or upstream?
Where is '--tcp-option' from? It is not mentioned in man iptables.
Salute, comrade!
About --tcp-option please see this information from netfilter developers: https://www.netfilter.org/documentation … WTO-7.html or see man page iptables: https://linux.die.net/man/8/iptables
I don't know exactly where the change occurred, but it happened about 2 years ago. About 2 years ago, after the next update in iptables (this can be tracked by the history of updating fixes and updates for iptables in Debian b) in Debian 9, I started to show an error in the logs about the absence of --tcp-option 0. As it turned out in the future, this error was present in both Ubuntu and Devuan. I suspect that the developers of netfilter made this error, because it has become present in all derivatives based on Ubuntu and Debian.
rolfie, fsmithred!
You Trolls! Here, trolls, we're talking about hwclock, not ntp, ntpdate, ntpdate! Write on the topic, and do not clog the discussion with your wet dreams!
Hello, friends!
In Devuan 1, Devuan 2, Devuan 3 (and Debian, and Ubuntu) have next standard issue with iptables!
The current range of values for the --tcp-option iptables flag is 1-255 - this is not correct. The correct range of values should be 0-254. Please read the following information: https://www.iana.org/assignments/tcp-pa … rameters-1 This negative change in iptables was made approximately 2 years ago without making this change public. Please report this issue to the iptables developers so that they can set the range of --tcp-option values in accordance with the accepted standards for the TCP Protocol.
How is your Devuan box configured? Is it set to UTC or localtime? If you don't know then check the last line in /etc/adjtime
It is recommended to set GNU/Linux systems to UTC, even if dual-booting with Windows. For dual-boot systems you should instead force Windows to use UTC with the RealTimeIsUniversal registry key.
Use this to check your system timezone:
ls -l /etc/localtime
If it's wrong then use
# dpkg-reconfigure tzdata
Yes! My tzdata is configured. Issue only with hwclock util. I not use MS Windows systems over 10 years!!!
You are not careful! I repeat!
Must be:
hwclock --utc
2020-02-28 20:15:50.889268+00:00
hwclock --localtime
2020-02-28 23:16:54.311448+03:00
Hello, friends!
I have the following situation in Devuan 2 and Devuan 3:
hwclock --utc
2020-02-29 02:15:50.889268+03:00
hwclock --localtime
2020-02-28 23:16:54.311448+03:00
This is wrong!!!
Must be:
hwclock --utc
2020-02-28 20:15:50.889268+00:00
hwclock --localtime
2020-02-28 23:16:54.311448+03:00
After a reboot, the BIOS sets the time to UTC, which should be localtime.
Please report this issue to the hwclock developers.
Thanks!
It doesn't always happen in a few hours. Be patient. It's coming.
Problem is solved. Big thanks!
Done in 2.0.19+ds1-2+devuan4
Right now, it's still in ceres (unstable).
This error includes Devuan Beowulf 3!!! In testing the distribution!!!
Wow. It's fixed. New version should appear in repo within a few hours.
Thanks for reporting.
Thanks you!
Please fix another problem with package "dnscrypt-proxy". Please add the following lines to the start service script of the /etc/init.d/dnscrypt-proxy:
if [ ! -d /var/cache/dnscrypt-proxy/ ]; then
mkdir /var/cache/dnscrypt-proxy
fi
This is fix the problem with downloading source public-resolvers from https://download.dnscrypt.info
Developers, please add these changes to the "dnscrypt-proxy" installation package.
Hello, friends!
I resolve problem in installation package "dnscrypt-proxy". This package contains an incorrect command to start the /etc/init.d/dnscrypt-proxy service in the executable file:
cmd="/usr/sbin/dnscrypt-proxy -c /etc/dnscrypt-proxy/dnscrypt-proxy.toml"
The service launch command should be:
cmd="/usr/sbin/dnscrypt-proxy -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml"
========================================================
Developers, please fix this problem. Without fixing this problem in the "dnscrypt-proxy" installation package, this package is not installed using the "apt" package installer.
Hi
Try commenting the line "autospawn=no" on /etc/pulse/client.conf.d/00-disable-autospawn.conf file like the comments on that file suggest.
Ok! Thanks you! I try!
Developers Devuan can resolve this problem.
King regards.
Hi, my friends!
I have problem with autostart pulseaudio after login in KDE 5 Beowulf (Devuan 3), pulseaudio not autostart.
I resolve this problem only add this command in autostart in System Setting application: /usr/bin/pulseaudio --start --log-target=syslog
Friends, please, resolve this problem for all in next update Beowulf (Devuan 3).
King regards, thanks!
Sorry me please. I set up in fstab /run/shm ro (read only) and Skype GUI not work. I return /run/shm to rw and Skype GUI is work.
Please delete this my theme.
@Administrator Hi! I translate your files for FluxBB for Russian language and send result to you. Please see your mailbox. Please test my translate files.
@Administrator Please wait, i translate your send me files. Thanks you!