Hello,


I am trying to bringup the wifi network with an ipv4 address on a Cubox-i automatically after boot.

Manually, it works:

root@outdoor:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug end0
iface end0 inet dhcp


auto wlan0
iface wlan0 inet dhcp
wpa-ssid DLAN
wpa-psk <secret>
root@outdoor:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d0:63:b4:00:2b:ac brd ff:ff:ff:ff:ff:ff
inet 192.168.7.25/24 brd 192.168.7.255 scope global dynamic end0
valid_lft 43121sec preferred_lft 43121sec
inet6 fe80::d263:b4ff:fe00:2bac/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:5a:f7:82:aa:c2 brd ff:ff:ff:ff:ff:ff
inet6 fd8d:5fab:96ee:0:ba5a:f7ff:fe82:aac2/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 fdea:6e1a:c5b2:0:ba5a:f7ff:fe82:aac2/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 fe80::ba5a:f7ff:fe82:aac2/64 scope link
valid_lft forever preferred_lft forever
root@outdoor:~# ifdown wlan0
Killed old client process
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on Socket/fallback
DHCPRELEASE of 192.168.2.202 on wlan0 to 192.168.2.1 port 67
ifroot@outdoor:~# ifup wlan0
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.2.202 from 192.168.2.1
DHCPREQUEST for 192.168.2.202 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.2.202 from 192.168.2.1
bound to 192.168.2.202 -- renewal in 16751 seconds.
root@outdoor:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d0:63:b4:00:2b:ac brd ff:ff:ff:ff:ff:ff
inet 192.168.7.25/24 brd 192.168.7.255 scope global dynamic end0
valid_lft 43062sec preferred_lft 43062sec
inet6 fe80::d263:b4ff:fe00:2bac/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:5a:f7:82:aa:c2 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.202/24 brd 192.168.2.255 scope global dynamic wlan0
valid_lft 43196sec preferred_lft 43196sec
inet6 fdea:6e1a:c5b2:0:ba5a:f7ff:fe82:aac2/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 fd8d:5fab:96ee:0:ba5a:f7ff:fe82:aac2/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 fe80::ba5a:f7ff:fe82:aac2/64 scope link
valid_lft forever preferred_lft forever
root@outdoor:~#

In the kernel messages I see:

[ 19.474457] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.bin (-2)
[ 19.493647] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.bin (-2)
[ 19.526434] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.txt (-2)
[ 19.552764] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.txt (-2)
[ 19.597617] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.clm_blob (-2)
[ 19.676688] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.clm_blob (-2)
[ 19.737380] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.clm_blob (-2)
[ 19.773626] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.clm_blob (-2)
[ 23.420532] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred
[ 23.427094] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev- wlan0 type 10 failed: err=-5

Any hint or advice is welcome.

Thanks
Rainer


--
Rainer Dorsch
http://bokomoko.de/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Looks like your firmware is not available. For broadcomm cards there is an extra installer, which downloads it seperately.

In Debian the firmware is not shipped in the repo, but an installer is
shipped.

Check for any broadcom related packages.

Hope this helps.

Best

Hans

In the kernel messages I see:

[ 19.474457] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.bin (-2)
[ 19.493647] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.bin (-2)
[ 19.526434] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.txt (-2)
[ 19.552764] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.txt (-2)
[ 19.597617] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.clm_blob (-2)
[ 19.676688] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.clm_blob (-2)
[ 19.737380] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.clm_blob (-2)
[ 19.773626] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.clm_blob (-2)
[ 23.420532] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout
occurred
[ 23.427094] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface
p2p-dev-
wlan0 type 10 failed: err=-5

Any hint or advice is welcome.

Thanks
Rainer

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Rainer,


Apologies I cannot help you. I have been hoping someone might who is
able to do so, would respond.


I searched the Internet and it would seem you are not alone with this
issue.


Is network manager installed in your system?


Is your system Debian 12 (Bookworm)?, I would presume so.


Here are a few links, though I did not see any fixes.


https://forums.raspberrypi.com/viewtopic.php?t=284735



https://linux.debian.kernel.narkive.com/WW9FRWvK/bug-797779-brcmfmac4330-sdio-txt-from-openelec-fixes-the-issue


https://community.infineon.com/t5/Wi-Fi-Bluetooth-for-Linux/cypress-fmac-v5-15-58-2023-0801-backport-issue/td-p/474900#.


https://bugs-devel.debian.org/cgi-bin/bugreport.cgi?bug=1041436 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053345


https://patchwork.kernel.org/project/linux-wireless/patch/5A55D325.60805@broadcom.com/


George.



On Monday, 03-02-2025 at 01:01 Rainer Dorsch wrote:


Hello,


I am trying to bringup the wifi network with an ipv4 address on a
Cubox-i
automatically after boot.

Manually, it works:

root@outdoor:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug end0
iface end0 inet dhcp


auto wlan0
iface wlan0 inet dhcp
   wpa-ssid DLAN
   wpa-psk
root@outdoor:~# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: end0:
mtu 1500 qdisc fq_codel state UP
group default qlen 1000
    link/ether d0:63:b4:00:2b:ac brd ff:ff:ff:ff:ff:ff
    inet 192.168.7.25/24 brd 192.168.7.255 scope global dynamic
end0
       valid_lft 43121sec preferred_lft 43121sec
    inet6 fe80::d263:b4ff:fe00:2bac/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0:
mtu 1500 qdisc fq_codel state UP
group default qlen 1000
    link/ether b8:5a:f7:82:aa:c2 brd ff:ff:ff:ff:ff:ff
    inet6 fd8d:5fab:96ee:0:ba5a:f7ff:fe82:aac2/64 scope global
dynamic
mngtmpaddr
       valid_lft forever preferred_lft forever
    inet6 fdea:6e1a:c5b2:0:ba5a:f7ff:fe82:aac2/64 scope global
dynamic
mngtmpaddr
       valid_lft forever preferred_lft forever
    inet6 fe80::ba5a:f7ff:fe82:aac2/64 scope link
       valid_lft forever preferred_lft forever
root@outdoor:~# ifdown wlan0
Killed old client process
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on   LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on   Socket/fallback
DHCPRELEASE of 192.168.2.202 on wlan0 to 192.168.2.1 port 67
ifroot@outdoor:~# ifup wlan0
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on   LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.2.202 from 192.168.2.1
DHCPREQUEST for 192.168.2.202 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.2.202 from 192.168.2.1
bound to 192.168.2.202 -- renewal in 16751 seconds.
root@outdoor:~# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: end0:
mtu 1500 qdisc fq_codel state UP
group default qlen 1000
    link/ether d0:63:b4:00:2b:ac brd ff:ff:ff:ff:ff:ff
    inet 192.168.7.25/24 brd 192.168.7.255 scope global dynamic
end0
       valid_lft 43062sec preferred_lft 43062sec
    inet6 fe80::d263:b4ff:fe00:2bac/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0:
mtu 1500 qdisc fq_codel state UP
group default qlen 1000
    link/ether b8:5a:f7:82:aa:c2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.202/24 brd 192.168.2.255 scope global dynamic
wlan0
       valid_lft 43196sec preferred_lft 43196sec
    inet6 fdea:6e1a:c5b2:0:ba5a:f7ff:fe82:aac2/64 scope global
dynamic
mngtmpaddr
       valid_lft forever preferred_lft forever
    inet6 fd8d:5fab:96ee:0:ba5a:f7ff:fe82:aac2/64 scope global
dynamic
mngtmpaddr
       valid_lft forever preferred_lft forever
    inet6 fe80::ba5a:f7ff:fe82:aac2/64 scope link
       valid_lft forever preferred_lft forever
root@outdoor:~#

In the kernel messages I see:

[   19.474457] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.bin (-2)
[   19.493647] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.bin (-2)
[   19.526434] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.txt (-2)
[   19.552764] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.txt (-2)
[   19.597617] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.clm_blob (-2)
[   19.676688] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.clm_blob (-2)
[   19.737380] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.clm_blob (-2)
[   19.773626] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.clm_blob (-2)
[   23.420532] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout
occurred
[   23.427094] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface
p2p-dev-
wlan0 type 10 failed: err=-5

Any hint or advice is welcome.

Thanks
Rainer


--
Rainer Dorsch
http://bokomoko.de/

<html>
<head>
<style type="text/css">
body,p,td,div,span{
font-size:13px; font-family:Arial, Helvetica, sans-serif;
};
body p{
margin:0px;
}
</style>
</head>
<body><div>Rainer,</div><div><br></div><div>Apologies I cannot help you. I have been hoping someone might who is able to do so, would respond.</div><div><br></div><div>I searched the Internet and it would seem you are not alone with this issue.</div><div>
<br></div><div>Is network manager installed in your system?</div><div><br></div><div>Is your system Debian 12 (Bookworm)?, I would presume so.</div><div><br></div><div>Here are a few links, though I did not see any fixes.</div><div><br></div><div>https://
forums.raspberrypi.com/viewtopic.php?t=284735<br></div><div><br></div><div>https://linux.debian.kernel.narkive.com/WW9FRWvK/bug-797779-brcmfmac4330-sdio-txt-from-openelec-fixes-the-issue</div><div><br></div><div>https://community.infineon.com/t5/Wi-Fi-
Bluetooth-for-Linux/cypress-fmac-v5-15-58-

On Sun, 02 Feb 2025 15:01:27 +0100
Rainer Dorsch <ml@bokomoko.de> wrote:

I am trying to bringup the wifi network with an ipv4 address on a
Cubox-i automatically after boot.

Manually, it works:
[...]
root@outdoor:~# ifdown wlan0
[...]
ifroot@outdoor:~# ifup wlan0
[...]
Any hint or advice is welcome.

You can create a script which makes things work and have it being
invoked after each reboot via /etc/rc.local - not the best way, but
maybe a workaround.
--
kind regards
Frank

-----BEGIN PGP SIGNATURE-----

iQGzBAEBCgAdFiEE86z15c6qwvuAkhy+zDIN/uu9BloFAmehEP4ACgkQzDIN/uu9 Blpyzwv6A/VpLXABCjT0X+RdWwvGcFMN4LdEAjrBC+89Emlfz7Gux8g435SvKFsQ 8RboimoPuWt0RGfCDLFLTWILMAqsRU3XelZoQ8KPw03KuGvd7LtM8UBe9MNuSpdI mA1q5mM0a6hazSUqFLFv10PWpQEWu7mfhf6weAuvjMiVB2FjqbumEjtGAnzdym2k 18TXA906otdIfiA3/ZZpNV9FwsoG3XI6SiGPC/xGhscJTZunApEK2v4wCpjYrcc6 y6sFBx1duBK3YkcEMhDxGOXxcFQ/4eMMy7UycTPsDXuRodV5+xLDd2ZdCC0SLlLY ZKtCMMGoBKu25N4rTnSfbN0is2/nkUMIZKYeY82C/fIaA3DlU4rTaAeZcx889aLO nOP05+cp6tLfjRCw7MwM1ZoKbfVE6U0yOGNyM8m7nhJwI74PbLg1zq0KB5QC3HzP A16niUh9Hqv+7AP+ExqC90XZUo9LBJWN3PqNEXwlGmOdLemugHscEKCl1+9ik2j0
3ZH6cZ88
=5mCS
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Rainer,

I believe others have responded.

Just for my curiosity, Is Network Manager installed? Would you be able to use nmclli to set a static IP address? Or maybe systemctl ?

I find Linux Networking confusing, so many different systems for managing networking, for example /etc/network/interfaces (which I like), Network Manager (which I reluctantly accept), systemctl (which I do not appreciate), etc. Similarly with Firewalls,
iptables (which I like), nftables (which I ask, Why?), and I am not sure what other methods are out there, but I guess there are more.

Sadly I am far from understanding networking, I learn what I need to [hopefully] make it work.

George.


On Monday, 03-02-2025 at 01:01 Rainer Dorsch wrote:

Hello,

I am trying to bringup the wifi network with an ipv4 address on a Cubox-i automatically after boot.

Manually, it works:

root@outdoor:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug end0
iface end0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-ssid DLAN
wpa-psk <secret>
root@outdoor:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d0:63:b4:00:2b:ac brd ff:ff:ff:ff:ff:ff
inet 192.168.7.25/24 brd 192.168.7.255 scope global dynamic end0
valid_lft 43121sec preferred_lft 43121sec
inet6 fe80::d263:b4ff:fe00:2bac/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 100

0

link/ether b8:5a:f7:82:aa:c2 brd ff:ff:ff:ff:ff:ff
inet6 fd8d:5fab:96ee:0:ba5a:f7ff:fe82:aac2/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 fdea:6e1a:c5b2:0:ba5a:f7ff:fe82:aac2/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 fe80::ba5a:f7ff:fe82:aac2/64 scope link
valid_lft forever preferred_lft forever
root@outdoor:~# ifdown wlan0
Killed old client process
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on Socket/fallback
DHCPRELEASE of 192.168.2.202 on wlan0 to 192.168.2.1 port 67 ifroot@outdoor:~# ifup wlan0
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on LPF/wlan0/b8:5a:f7:82:aa:c2
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.2.202 from 192.168.2.1
DHCPREQUEST for 192.168.2.202 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.2.202 from 192.168.2.1
bound to 192.168.2.202 -- renewal in 16751 seconds.
root@outdoor:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d0:63:b4:00:2b:ac brd ff:ff:ff:ff:ff:ff
inet 192.168.7.25/24 brd 192.168.7.255 scope global dynamic end0
valid_lft 43062sec preferred_lft 43062sec
inet6 fe80::d263:b4ff:fe00:2bac/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether b8:5a:f7:82:aa:c2 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.202/24 brd 192.168.2.255 scope global dynamic wlan0
valid_lft 43196sec preferred_lft 43196sec
inet6 fdea:6e1a:c5b2:0:ba5a:f7ff:fe82:aac2/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 fd8d:5fab:96ee:0:ba5a:f7ff:fe82:aac2/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 fe80::ba5a:f7ff:fe82:aac2/64 scope link
valid_lft forever preferred_lft forever
root@outdoor:~#

In the kernel messages I see:

[ 19.474457] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.bin (-2)
[ 19.493647] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.bin (-2)
[ 19.526434] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.txt (-2)
[ 19.552764] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.txt (-2)
[ 19.597617] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.clm_blob (-2)
[ 19.676688] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.solidrun,cubox-i-q.clm_blob (-2)
[ 19.737380] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.clm_blob (-2)
[ 19.773626] brcmfmac mmc0:0001:1: firmware: failed to load brcm/ brcmfmac4330-sdio.clm_blob (-2)
[ 23.420532] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred
[ 23.427094] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev- wlan0 type 10 failed: err=-5

Any hint or advice is welcome.

Thanks
Rainer

--
Rainer Dorsch
http://bokomoko.de/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

George at Clug <Clug@goproject.info> writes:

iptables (which I like), nftables (which I ask, Why?)

For a few years now, well, almost a decade, iptables has been a hollow
shell with nftables inside. Why nftables? Because it unifies firewall
for ipv4, ipv6 and bridges, so we don't need to have separate iptables, ip6tables and ebtables. I'm very happy with that and probably software maintainers are happy too, with less maintenance load.

I tend to think users should pick something a little higher level for
firewall management and stick with it. No idea if there's a
recommendation or default in Debian, the wiki entry seems rather old
school.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)