"Proceeding WITHOUT firewalling in effect!" warning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Won't Fix
|
Low
|
Unassigned |
Bug Description
Hello everyone,
I noticed a strange systemd warning in my kernel log about "Proceeding WITHOUT firewalling in effect!" There is an older Debian bug mention about this same issue and it is said there that it was fixed last year: https:/
Release: Ubuntu 19.10, fresh install, latest updates with updates-testing repository enabled
Systemd-package version: 242-7ubuntu3
Kernel: Linux 5.3.0-21-generic
Here is the relevant warning information via running sudo dmesg after boot:
[ 2.096064] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7
[ 2.101034] Lockdown: systemd: BPF is restricted; see man kernel_lockdown.7
[ 2.136885] systemd[1]: File /lib/systemd/
[ 2.142209] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[ 2.158190] systemd[1]: /lib/systemd/
[ 2.197029] systemd[1]: Listening on Journal Socket.
[ 2.203708] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[ 2.243900] bpfilter: Loaded bpfilter_umh pid 420
#Continues normally from here without anything that seems odd
The included attachment .txt has more information. From what I've read online from various bug trackers from other distributions this should be related to a missing kernel option (CONFIG_
# Output after running in commandline: grep BPF /boot/config-`uname -r`
# Kernel settings seem to be correct?
CONFIG_CGROUP_BPF=y
CONFIG_BPF=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_BPFILTER=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_BPF_JIT=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_BPF_EVENTS=y
CONFIG_
CONFIG_TEST_BPF=m
Also my friend just installed 19.10 on his machine and is seeing the same warning, but I haven't found anyone else mentioning this issue at least on the latest Ubuntu 19.10. The same warning message is appearing if I run Ubuntu 19.10 in live mode from the USB stick.
What I expected to happen: no such error (it doesn't appear on Fedora or openSUSE Tumbleweed that I've recently had installed on my other SSD)
What happened instead: error appears during every boot sequence
It's also worth stressing that the firewall is functioning just fine (using standard ufw) despite the error, so I'm guessing this is a harmless warning.
Changed in systemd (Ubuntu): | |
status: | New → In Progress |
Changed in systemd (Ubuntu): | |
assignee: | nobody → Dan Streetman (ddstreet) |
status: | In Progress → Fix Released |
Changed in systemd (Ubuntu Eoan): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu): | |
assignee: | Dan Streetman (ddstreet) → nobody |
Changed in systemd (Ubuntu Eoan): | |
importance: | Undecided → Low |
status: | New → In Progress |
Changed in systemd: | |
status: | Unknown → Fix Released |
Changed in systemd (Ubuntu Eoan): | |
assignee: | Dan Streetman (ddstreet) → nobody |
status: | In Progress → New |
can you test with the systemd from this ppa to see if it fixes the warning logs: /launchpad. net/~ddstreet/ +archive/ ubuntu/ systemd
https:/