Bug#719810: shorewall-init: On ethernet module rmmod/modprobe shorewall-init fails to bring back firewall rules correctly

2017-11-20 Thread Roberto C . Sánchez
tags 719810 + unreproducible moreinfo
thanks

On Thu, Aug 15, 2013 at 10:37:38AM -0400, Daniel Dickinson wrote:
> Package: shorewall-init
> Version: 4.5.5.3-1
> Severity: minor
> 
> This is a bit of a corner case.  Due to a bug in the r8169 gige driver
> my network connection has issues that require the ethernet driver be
> rmmod'd then modprobe'd.  Shorewall-init doesn't seem to properly
> handl this case as shorewall's firewall rules are not put back in
> place on the modprobe (and consequent network manager reconnection to
> the router).
> 
Hi Daniel,

Apologies for the long delay, I sort of lost track of this bug report.

I have tried to reproduce this on a fresh Debian Stretch install (inside
of a Qemu VM guest).  I installed/configured shorewall and confirmed
that there were iptables rules that had been made active.  Then I did an
rmmod on virtio_net, checked and saw that the rules were still active,
then did a modprobe on virtio_net and again checked and found the rules
still active.

At this point I believe that the bug you encountered is either a result
of a specific bug in the r8169 driver, or some other kernel bug.  I
doubt that it is a Shorewall bug, as Shorewall is not an active service,
so it would not have a way to monitor the removal of the iptables rules.

This, along with the age of your original bug report causes me to think
that it should be closed.  However, before I do that I wanted to give
you the opportunity to comment or provide additional information that
might allow reproducing the bug.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com



Bug#719810: shorewall-init: On ethernet module rmmod/modprobe shorewall-init fails to bring back firewall rules correctly

2013-08-15 Thread Daniel Dickinson
Package: shorewall-init
Version: 4.5.5.3-1
Severity: minor

This is a bit of a corner case.  Due to a bug in the r8169 gige driver my 
network connection has issues that require the ethernet driver be rmmod'd then 
modprobe'd.  Shorewall-init doesn't seem to properly handl this case as 
shorewall's firewall rules are not put back in place on the modprobe (and 
consequent network manager reconnection to the router).

Regards,


Daniel

-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages shorewall-init depends on:
ii  shorewall   4.5.5.3-3
ii  shorewall6  4.5.5.3-2

shorewall-init recommends no packages.

shorewall-init suggests no packages.

-- Configuration Files:
/etc/default/shorewall-init changed:
PRODUCTS="shorewall shorewall6"
IFUPDOWN=1
SAVE_IPSETS=""
LOGFILE=/var/log/shorewall-ifupdown.log


-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org