Bug#739251: iptables: Situation resolved
Package: iptables Version: 1.6.0+snapshot20161117-6 Followup-For: Bug #739251 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Using synaptic, I removed all debian-edu packages. Iptables immediately functioned as expected. Rules loading up at boot and maintained seamlessly throughout runtime. I would guess this bug is with the skole-linux, debian-edu package. Iptables working fine with simple xfce desktop. -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages iptables depends on: ii libc62.24-11+deb9u3 ii libip4tc01.6.0+snapshot20161117-6 ii libip6tc01.6.0+snapshot20161117-6 ii libiptc0 1.6.0+snapshot20161117-6 ii libnetfilter-conntrack3 1.0.6-2 ii libnfnetlink01.0.1-3 ii libxtables12 1.6.0+snapshot20161117-6 iptables recommends no packages. Versions of packages iptables suggests: ii kmod 23-2 -- no debconf information
Bug#892951: iptables rules loaded via iptables-restore ....rules.v4 are dropped every few minutes.
Package: iptables Version: 1.6.0+snapshot20161117-6 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I believe the problem existed after fresh netinstall of Debian Stretch with xfce destop but I am not sure exactly when I \ began to notice iptables problem. I added skolelinux desktop which took over boot but is still xfce so I didn't mind. Being \ rather security conscious I'm sure I would setup iptables with rules right away. * What exactly did you do (or not do) that was effective (or ineffective)? I made rules for iptables. I noticed I had problems loading the rules up at boot. Tried netfilter-persistent, \ tried a script in rc.local maybe a couple of other efforts (installed apf, uninstalled apf netfilter-persistent, reinstall \ iptables and netfilter-persistent...) most things I tried usually worked for a few boots but would then would\ randomly fail. The most dependable thing I have found is to be disconnected from the network by default and place a preprocessing iptables startup script \ in wicd which loads the rules before network is brought up. Eventually I discovered the loaded rules would disapper after a few minutes. This \ happens whether I am browsing the internet or not or in fact not doing anything. I just tried to gdebi the latest package iptables_1.6.1-2~bpo9+1_amd64.deb but that was uninstallable due to an incompatible library. Rquired outcome is of course to load the rules and depend on them to be stable. Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages iptables depends on: ii libc62.24-11+deb9u3 ii libip4tc01.6.0+snapshot20161117-6 ii libip6tc01.6.0+snapshot20161117-6 ii libiptc0 1.6.0+snapshot20161117-6 ii libnetfilter-conntrack3 1.0.6-2 ii libnfnetlink01.0.1-3 ii libxtables12 1.6.0+snapshot20161117-6 iptables recommends no packages. Versions of packages iptables suggests: ii kmod 23-2 -- no debconf information
Bug#892493: dnscrypt-proxy: Unable to initialize plugin - libdcplugin_example_logging.so
Package: dnscrypt-proxy Version: 1.9.4-1 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installed dnscrypt-proxy via synaptic. There were failed attemps to start the service and I concluded it needed the dnscrypt-proxy-plugins package so that's been installed as well. At this point, 4 of 5 plugins load but 'libdcplugin_example_logging.so' fails to initialize. * What exactly did you do (or not do) that was effective (or ineffective)? I marked both dnscrypt-proxy and dnscrypt-proxy-plugins for reinstallation in synaptic and reinstalled. I still get the same result. I have checked that the file exists and it does, located in the same directory and has the same permissions as the other plugins that load without error. * What was the outcome of this action? Installing the plugins got one step closer to getting it working but still fails with ' [ERROR] Unable to load plugins' message * What outcome did you expect instead? Hoped it would run and I could go on to adjust configuration options. System Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dnscrypt-proxy depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii libc62.24-11+deb9u1 ii libltdl7 2.4.6-2 ii libsodium18 1.0.11-2 ii libsystemd0 232-25+deb9u1 ii lsb-base 9.20161125 dnscrypt-proxy recommends no packages. Versions of packages dnscrypt-proxy suggests: ii resolvconf 1.79 -- Configuration Files: /etc/dnscrypt-proxy/dnscrypt-proxy.conf changed: ProviderName2.dnscrypt-cert.ns3.ca.luggs.co ProviderKey 1C19:7933:1BE8:23CC:CF08:9A79:0693:7E5C:3410:2A56:AC7F:6270:E046:25B2:EDDB:04E3 ResolverAddress 142.4.204.111:443 Daemonize no User _dnscrypt-proxy LocalAddress 127.0.0.1:53 LocalCache on EphemeralKeys off MaxActiveRequests 250 EDNSPayloadSize 1252 TCPOnly no QueryLogFile /tmp/dns-queries.log LogLevel 6 Syslog on SyslogPrefix dnscrypt BlockIPv6 yes -- no debconf information
