Your message dated Sat, 13 Feb 2021 18:30:26 -0600
with message-id <20210214003026.GC22409@iolanthe>
and subject line Re: Bug#978631: ufw does not work at all!
has caused the Debian Bug report #978631,
regarding ufw does not work at all!
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
978631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978631
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ufw
Version: 0.36-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I run these commands on ufw protected Debian 10:
$ sudo ufw status
[sudo] hasło użytkownika energokoder:
Status: active
To Action From
-- ------ ----
Samba ALLOW 192.168.0.0/16
80/tcp ALLOW 192.168.0.0/16
443/tcp ALLOW 192.168.0.0/16
22/tcp ALLOW 192.168.0.0/16
Anywhere on enp0s25 LIMIT Anywhere
Anywhere on wlx08beac034eef LIMIT Anywhere
7002/tcp ALLOW 192.168.0.0/16
Anywhere (v6) on enp0s25 LIMIT Anywhere (v6)
Anywhere (v6) on wlx08beac034eef LIMIT Anywhere (v6)
$ echo "Jakiś plik" > 1.txt
$ python3 -m http.server 1234
Serving HTTP on 0.0.0.0 port 1234 (http://0.0.0.0:1234/) ...
192.168.1.20 - - [29/Dec/2020 12:53:42] "GET /1.txt HTTP/1.1" 200 -
And on my Kubuntu 20.04 I run commands:
$ wget 192.168.1.40:1234/1.txt
$ cat 1.txt
Jakiś plik
and it download without any problem!
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 10.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-11-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ufw depends on:
ii debconf [debconf-2.0] 1.5.71
ii iptables 1.8.2-4
ii lsb-base 10.2019051400
ii python3 3.7.3-1
ii ucf 3.0038+nmu1
ufw recommends no packages.
Versions of packages ufw suggests:
ii rsyslog 8.1901.0-1
-- debconf information:
ufw/allow_known_ports:
ufw/enable: false
ufw/allow_custom_ports:
ufw/existing_configuration:
--- End Message ---
--- Begin Message ---
On Tue, 29 Dec 2020, Jamie Strandboge wrote:
> On Tue, 29 Dec 2020, Energo Koder wrote:
> > Anywhere on enp0s25 LIMIT Anywhere
> > Anywhere on wlx08beac034eef LIMIT Anywhere
>
> I suspect it is these two lines that are allowing the traffic. It is
> saying to allow (with rate limiting) anything coming in on the enp0s25
> and wlx08beac034eef interfaces. Is 192.168.1.40 associated with either
> of these interfaces?
Per the reporter, the traffic was matching one of the allowed rules so
this is not a bug.
Thanks for the report!
--
Email: [email protected]
IRC: jdstrand
--- End Message ---
