~$ lspci -nn 00:00.0 Host bridge : Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) 00:02.0 VGA compatible controller : Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) 00:16.0 Communication controller : Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) 00:16.3 Serial controller : Intel Corporation 6 Series/C200 Series Chipset Family KT Controller [8086:1c3d] (rev 04) 00:19.0 Ethernet controller : Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) 00:1b.0 Audio device : Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04) 00:1c.0 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4) 00:1c.1 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b4) 00:1c.3 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4) 00:1c.4 PCI bridge : Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b4) 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04) 00:1f.0 ISA bridge : Intel Corporation QM67 Express Chipset Family LPC Controller [8086:1c4f] (rev 04) 00:1f.2 SATA controller : Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 04) 03:00.0 Network controller : Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34) 0d:00.0 System peripheral : Ricoh Co Ltd PCIe SDXC/MMC Host Controller [1180:e823] (rev 07) As [he was saying](https://unix.stackexchange.com/questions/645901/having-issue-with-debian-installation#comment1210259_645901) . I was following [the Wiki](https://wiki.debian.org/iwlwifi) . root@debian:/home/istiak# apt update && apt install firmware-iwlwifi Hit:1 http://security.debian.org/debian-security buster/updates InRelease Hit:2 http://deb.debian.org/debian buster InRelease Hit:3 http://deb.debian.org/debian buster-updates InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package firmware-iwlwifi root@debian:/home/istiak# modprobe -r iwlwifi ; modprobe iwlwifi bash: modprobe: command not found bash: modprobe: command not found When I try to run iwconfig or ifconfig I get that command not found. How can I install wifi driver? I have installed(iwlwifi-6000g2a-ucode-18.168.6.1.tgz) from [here](https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html) . When I extracted I got it(iwlwifi-6000g2a-6.ucode). What I have to do with it? Output of /usr/sbin/modprobe --version : kmod version 26 +XZ -ZLIB +OPENSSL -EXPERIMENTAL iwconfig : root@debian:~# /sbin/iwconfig enp0s25 no wireless extensions. wwp0s29u1u4 no wireless extensions. wlp3s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off lo no wireless extensions. lspci -knn | grep -i net -A3 : istiak@debian:~$ lspci -knn | grep -i net -A3 00:19.0 Ethernet controller : Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) Subsystem: Lenovo 82579LM Gigabit Network Connection (Lewisville) (ThinkPad T520) [17aa:21ce] Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) -- 03:00.0 Network controller : Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN [8086:1311] Kernel driver in use: iwlwifi Kernel modules: iwlwifi

I’m trying to manage my wireless LAN interface using wpa_supplicant on my i.MX8 running Yocto Scarthgap. I can scan for available networks and connect successfully using the wpa_cli utility. However, when I try to save the current network configuration to the .conf file to persist it, wpa_supplicant fails to start on reboot due to an incorrect file format. Steps I followed before reboot to connect to an AP

> add_network
0
CTRL-EVENT-NETWORK-ADDED 0

> > set_network 0 ssid "MyNetwork"
OK
> set_network 0 psk "MyPassPhrase"
OK
> enable_network 0
OK
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
Trying to associate with SSID 'MyNetwork'
.....
CTRL-EVENT-CONNECTED - Connection to xxxxxx completed [id=0 id_str=]

> > save_config
OK
> quit

This is what my .conf file in /etc/wpa_supplicant/wpa_supplicant-wlan0.conf looks like after I run save_config .

ctrl_interface=/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1
filter_ssids=1
ignore_old_scan_res=1

network={
	ssid="MyNetwork"
	psk=*
}

On reboot systemd failed to start wpa_supplicant service

root@imx8qxp:~# journalctl -xe -u wpa_supplicant@wlan0.service 
Jul 09 16:03:46 imx8qxp systemd: Started WPA supplicant daemon (interface-specific version). 
-- Subject: A start job for unit wpa_supplicant@wlan0.service has finished successfully 
-- Defined-By: systemd 
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel  
--  
-- A start job for unit wpa_supplicant@wlan0.service has finished successfully. 
--  
-- The job identifier is 100. 
Jul 09 16:03:46 imx8qxp systemd: wpa_supplicant@wlan0.service: Main process exited, code=exited, status=255/EXCEPTION 
-- Subject: Unit process exited 
-- Defined-By: systemd 
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel  
--  
-- An ExecStart= process belonging to unit wpa_supplicant@wlan0.service has exited. --  -- The process' exit code is 'exited' and its exit status is 255. 
Jul 09 16:03:46 imx8qxp systemd: wpa_supplicant@wlan0.service: Failed with result 'exit-code'. -- Subject: Unit failed 
-- Defined-By: systemd 
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel  
--  
-- The unit wpa_supplicant@wlan0.service has entered the 'failed' state with result 'exit-code'.

On further investigation by trying to start wpa_supplicant manually

root@imx8qxp:~# wpa_supplicant -B -dd -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
Line 9: Invalid PSK '*'.
Line 9: failed to parse psk '*'.
Line 10: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant-wlan0.conf'.

I did try to manually generate the passphrase using the command wpa_passphrase SSID PASSWORD > /etc/wpa_supplicant/wpa_supplicant-wlan0.conf and there were no issues with it after reboot. I get this error only when trying to save network config from wpa_cli. I also tried recreating it on an ubuntu 24 machine but could not successfully reproduce the issue. While the obvious solution is to use wpa_passphrase directly, I'm interested in understanding why this issue occurs in the first place. Despite searching online, I haven’t come across anyone experiencing this exact problem. Could it be that I’m missing a step when saving the network configuration using wpa_cli? What causes this behaviour, and is there a correct way to persist network settings without manually trying to write to the file? I don't prefer using the wpa_passphrase command because I ultimately want to use wpa_ctrl C APIs and would not prefer messing with the .conf files in the application layer.

I am trying to set up 2 wireless access points from linux device (Debian Jessy). Both AP's should work simultaneously & share Internet connection (as shown below).

    _____       ___________ 
    |   | eth0 |           | wlan0(AccessPoint 2.5G) 
    |box|-----WLAN0_Stick WLAN1_Stick 
My initial config (hostapd & dnsmasq) for single wlan0 (AccessPoint 2.5G) 

**/etc/hostapd.conf**
    # Define interface
    interface=wlan0
    # Select driver
    driver=nl80211
    # Set access point name
    ssid=AP-wifi-2G
    # Set access point harware mode to 802.11g
    hw_mode=g
    # Set WIFI channel (can be easily changed)
    channel=6
    # Enable WPA2 only (1 for WPA, 2 for WPA2, 3 for WPA + WPA2)
    wpa=2
    wpa_passphrase=wifi123456

**/etc/dnsmasq.conf**
    # Bind to only one interface
    bind-interfaces
    # Choose interface for binding
    interface=wlan0
    # Specify range of IP addresses for DHCP leasses
    dhcp-range=192.168.150.2,192.168.150.10

In order to initialize AP1 I use following bash-script

**start.sh**
    !/bin/bash
    # Start
    # Configure IP address for WLAN
    sudo ifconfig wlan0 192.168.150.1
    # Start DHCP/DNS server
    sudo service dnsmasq restart
    # Enable routing
    sudo sysctl net.ipv4.ip_forward=1
    # Enable NAT
    sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
    # Run access point daemon
    sudo hostapd /etc/hostapd.conf
    # Stop
    # Disable NAT
    sudo iptables -D POSTROUTING -t nat -o eth0 -j MASQUERADE
    # Disable routing
    sudo sysctl net.ipv4.ip_forward=0
    # Disable DHCP/DNS server
    sudo service dnsmasq stop


This config works fine for single AP (wlan0, AccessPoint 2.5G)
I added the 2nd config /etc/hostapd_5G.conf for wlan1 similar as /etc/hostapd.conf & changed dnsmasq.conf & start.sh (wlan0->wlan1 for testing) - it also worked good in 5G.

But I need to run wlan0 AP & wlan1 AP simultaneously. I think I need to modify dnsmasq.conf for second interface. But I don't know how to do this.

Anyone please help with simultaneous configuration (wlan0 AP & wlan1 AP).
                                

I have 2 Wlan Routers with the same SSID. One on the channel 6 and one on the channel 11. By default I am connected to the one on the channel 6. How can I connect to the one on channel 11? (Of course I could just connect via LAN or power off the router with channel 6, but I'm searching for a solution where i connect to a specific endpoint) Thanks in advance!

whenever I try to connect to connect to wlan0 it says it is down but whenever I try to put it up by using the command ifconfig wlan0 up then I try ip addressbut it still doesn't come up 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 valid_lft forever preferred_lft forever 2: ens33: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:0c:29:f4:91:46 brd ff:ff:ff:ff:ff:ff altname enp2s1 inet 192.168.217.138/24 brd 192.168.217.255 scope global dynamic noprefixroute ens33 valid_lft 1754sec preferred_lft 1754sec inet6 fe80::3043:70ae:f66b:b70a/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlx00c0ca993e3b: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 00:c0:ca:99:3e:3b brd ff:ff:ff:ff:ff:ff how do i fix this this is kali vm kali is the only Linux flavour that does this this is a alfa adaptor called Alfa Network AWUS036NHA – USB WIFI Adapter, 150 Mbps, 802.11b/g/n, RP-SMA, AR9271L Atheros Chipset

I have a rtl8821ae-based 5GHz WiFi card on my desktop PC (It is pci-e TP-Link Archer T4E) I would like to install and use Linux to this desktop. I try different popular distros (Ubuntu, Fedora, Manjaro etc) and for all of them there is the same problem: slow wi-fi speed. I googled and tried to build some drivers from GitHub, but the ones I found are for rtl8821a**U** (USB-version), while mine card is PCI-e. I almost gave up, but tried Linux Mint Cinnamon and finally Wi-Fi worked as expected at full speed! Then I assumed Linux Mint uses some special driver. I decided that I need to figure out which one is used by Linux Mint to have a freedom to choose distro. I found the answer here: [How to find out which Wi-Fi driver is installed?](https://unix.stackexchange.com/a/7818/85258) Below is my output of Ubuntu (which has terribly slow Wi-Fi):

user@ubnt:~$ sudo lshw -class network
[sudo] password for user: 
  *-network                 
       description: Wireless interface
       product: RTL8812AE 802.11ac PCIe Wireless Network Adapter
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 01
       serial: xx:xx:xx:xx:xx:xx
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rtl8821ae driverversion=5.8.0-48-generic firmware=N/A ip=xx.xx.xx.xx latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:158 ioport:e000(size=256) memory:df400000-df403fff

user@ubnt:~$ lsmod | grep rtl8821ae
rtl8821ae             233472  0
btcoexist             155648  1 rtl8821ae
rtl_pci                28672  1 rtl8821ae
rtlwifi                94208  3 rtl_pci,rtl8821ae,btcoexist
mac80211              905216  3 rtl_pci,rtl8821ae,rtlwifi

user@ubnt:~$ modinfo rtl8821ae
filename:       /lib/modules/5.8.0-49-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae/rtl8821ae.ko
firmware:       rtlwifi/rtl8821aefw_29.bin
firmware:       rtlwifi/rtl8821aefw.bin
description:    Realtek 8821ae 802.11ac PCI wireless
license:        GPL
author:         Realtek WlanFAE    
srcversion:     64BDAFD5093CE917B32291C
alias:          pci:v000010ECd00008821sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008812sv*sd*bc*sc*i*
depends:        rtlwifi,rtl_pci,btcoexist,mac80211
retpoline:      Y
intree:         Y
name:           rtl8821ae
vermagic:       5.8.0-49-generic SMP mod_unload modversions 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        1A:D5:E6:56:CF:B6:5E:AF:60:74:90:89:34:8C:97:0F:89:36:10:FB
sig_hashalgo:   sha512
signature:      2C:62:21:33:F2:14:BA:C9:6D:A9:71:6F:92:6D:DE:4C:F5:B7:57:C5:
        BE:A2:F1:61:99:31:DE:15:3B:E2:42:41:FA:15:1D:2D:24:6F:6F:C6:
        B8:4B:2F:92:21:F8:D5:B6:E2:6E:9B:42:86:F1:43:CE:FC:DF:87:F8:
        8D:DC:BB:65:A3:5E:7C:42:2C:46:CA:EB:48:59:44:A7:83:36:91:6A:
        C8:21:AC:F7:CD:71:7C:E4:59:FF:11:E4:4A:2B:C5:AF:FD:88:EE:F7:
        8E:B8:FA:A6:B8:A9:35:5F:76:A4:8A:D7:63:E0:37:74:BE:91:34:F1:
        E6:F8:DB:6F:D5:AF:3D:C6:29:26:51:95:8F:3C:4F:65:A5:05:0B:19:
        20:ED:1D:D2:F0:FF:F1:F1:06:C3:51:06:20:2F:40:11:E6:12:C4:96:
        1F:C1:C5:58:7D:09:10:C3:17:DE:31:51:2E:14:DE:92:20:40:62:D2:
        0A:D6:52:73:37:10:28:30:EA:47:28:53:51:2D:5C:C2:F7:10:E2:44:
        58:67:83:6B:F1:5D:01:A4:A6:B2:EC:B7:FD:CC:A4:A9:DD:71:13:91:
        52:E0:77:A6:E6:1A:4A:27:B0:0A:59:EF:EF:28:D4:E3:CE:A9:8F:DD:
        F5:A0:FF:91:02:E6:E4:2E:D9:08:90:F0:AB:E2:67:AA:B1:54:A2:7E:
        8A:77:97:FB:93:1C:85:CC:E5:18:CE:F9:AC:47:9E:8D:D3:2F:9C:11:
        16:38:E6:DC:BA:D6:8C:C7:EA:B9:38:EE:27:00:AE:66:FE:CB:79:E0:
        43:66:2D:5C:88:AE:BD:07:49:08:F2:4E:4D:BF:FE:48:3E:6D:14:3A:
        CC:DE:7D:02:8A:6E:E6:72:69:FB:65:30:36:35:DD:5B:FA:DD:1B:F4:
        B5:F2:56:05:A6:58:C0:31:0A:93:BB:05:F1:B4:5D:0A:32:4A:38:46:
        1B:9F:F9:27:8B:A0:56:CE:14:8B:84:C8:56:7D:24:FD:50:0F:6E:E8:
        E8:5F:9E:7C:C1:6B:50:AB:68:BE:23:3F:27:84:82:B1:64:6C:DF:C5:
        CC:6B:33:7C:B4:5E:1A:8D:61:E1:D9:58:EA:3F:19:DD:C9:92:ED:18:
        FC:A4:96:94:EF:F4:C1:9F:63:E8:E9:83:2B:CF:DC:28:38:F6:86:C4:
        20:7C:C6:8E:F7:64:CE:D9:B0:F1:19:D8:E2:1F:EB:77:3D:24:C3:93:
        23:FC:69:16:DA:27:64:6F:92:88:91:EA:25:FF:BB:F1:30:19:0F:74:
        68:C1:EB:C1:F0:A5:2C:F7:F4:03:30:72:50:28:EB:54:F0:84:F6:17:
        60:27:3F:54:89:E1:25:A8:07:12:AC:0B
parm:           swenc:Set to 1 for software crypto (default 0)
 (bool)
parm:           ips:Set to 0 to not use link power save (default 1)
 (bool)
parm:           swlps:Set to 1 to use SW control power save (default 0)
 (bool)
parm:           fwlps:Set to 1 to use FW control power save (default 1)
 (bool)
parm:           msi:Set to 1 to use MSI interrupts mode (default 1)
 (bool)
parm:           aspm:Set to 1 to enable ASPM (default 1)
 (int)
parm:           debug_level:Set debug level (0-5) (default 0) (int)
parm:           debug_mask:Set debug mask (default 0) (ullong)
parm:           disable_watchdog:Set to 1 to disable the watchdog (default 0)
 (bool)
parm:           int_clear:Set to 0 to disable interrupt clear before set (default 1)
 (bool)

Now the output of well behaving Linux Mint:

mint@mint:~/Desktop$ sudo lshw -class network
  *-network                 
       description: Wireless interface
       product: RTL8812AE 802.11ac PCIe Wireless Network Adapter
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 01
       serial: xx:xx:xx:xx:xx:xx
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rtl8821ae driverversion=5.4.0-58-generic firmware=N/A ip=xx.xx.xx.xx latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:159 ioport:e000(size=256) memory:df400000-df403fff

mint@mint:~/Desktop$ lsmod | grep rtl8821ae
rtl8821ae             233472  0
btcoexist             155648  1 rtl8821ae
rtl_pci                28672  1 rtl8821ae
rtlwifi                90112  3 rtl_pci,rtl8821ae,btcoexist
mac80211              843776  3 rtl_pci,rtl8821ae,rtlwifi

mint@mint:~$ modinfo rtl8821ae
filename:       /lib/modules/5.4.0-58-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae/rtl8821ae.ko
firmware:       rtlwifi/rtl8821aefw_29.bin
firmware:       rtlwifi/rtl8821aefw.bin
description:    Realtek 8821ae 802.11ac PCI wireless
license:        GPL
author:         Realtek WlanFAE    
srcversion:     A8B43BD1DD5C4F8EC9C4F6A
alias:          pci:v000010ECd00008821sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008812sv*sd*bc*sc*i*
depends:        rtlwifi,rtl_pci,btcoexist,mac80211
retpoline:      Y
intree:         Y
name:           rtl8821ae
vermagic:       5.4.0-58-generic SMP mod_unload 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        4F:99:95:CB:A3:36:65:3E:1E:5A:30:73:58:12:C3:10:81:02:EA:FF
sig_hashalgo:   sha512
signature:      04:58:B3:93:74:BB:47:4C:44:EC:B9:B4:BF:41:D8:2F:78:10:5E:74:
        CD:E2:93:42:71:D7:48:C7:ED:DA:9C:80:00:BB:DF:99:2A:44:0C:CB:
        BF:79:2E:05:FD:61:CA:E7:3F:5A:C0:5D:1B:78:31:41:88:44:A4:6A:
        82:A8:51:64:AA:12:6F:1A:F2:09:E8:C1:5E:CF:BA:52:2F:8E:1D:DF:
        D9:93:8E:51:EF:4D:7E:8E:2E:D6:B1:DE:3E:05:0C:57:05:3E:3B:70:
        62:F6:01:87:A0:16:41:90:AF:CA:B9:7B:98:C8:DF:E0:2A:74:C1:97:
        DD:9B:23:93:C5:32:28:07:C0:72:52:C6:62:89:90:6C:A3:B2:80:E5:
        DE:E5:78:C5:FF:75:C9:3F:42:53:35:E4:9A:D7:A3:82:0B:BE:B8:90:
        0D:AD:0C:6D:48:A6:40:32:2E:2E:11:9D:55:C5:2A:4D:4F:40:EF:36:
        B2:F7:E5:C0:2E:56:C5:8C:13:27:86:C2:F1:0E:27:0F:9A:64:EE:CA:
        29:B7:A8:56:4D:7B:71:A2:B4:01:FA:1E:DC:7C:3A:B5:32:07:29:EF:
        86:41:94:61:64:17:6B:DD:B8:6D:9B:7C:2D:56:9D:5E:69:7B:A1:A8:
        C5:62:A5:F7:43:2D:49:D7:6A:43:3C:1B:DC:28:74:BF:0E:7E:BD:47:
        41:DF:0C:9E:E0:D3:5E:A9:9C:3C:6A:67:05:57:A7:9A:00:54:07:46:
        AE:53:5B:8F:8F:1C:76:AA:7E:41:FA:23:70:00:4F:BA:59:92:91:A9:
        F7:7B:16:B2:0B:DB:1A:43:A4:00:EF:3A:A7:5D:D0:E9:D0:80:CF:C6:
        77:0F:E7:75:99:C7:80:66:7D:94:E4:88:F1:22:26:69:D5:1E:F1:79:
        C4:14:E8:B9:20:66:9C:72:DD:02:85:EA:A3:51:02:03:97:C5:65:60:
        3E:E7:94:AD:A5:DA:ED:EC:34:BC:2E:41:48:BF:1C:B8:C0:3B:95:39:
        A8:A8:AC:57:3C:95:91:BA:E5:38:A3:82:34:BD:85:CA:71:3D:45:4A:
        4D:D7:13:54:57:9B:7B:BD:67:B2:DE:77:05:60:5D:B9:71:0E:B7:D4:
        45:88:2D:F8:0C:FD:20:EF:A8:AE:51:B0:25:5F:E6:85:36:24:C0:10:
        A9:49:EA:05:BD:27:C6:01:1D:83:48:03:F5:B1:08:DA:86:0F:F8:68:
        BB:7E:6D:01:76:36:D1:EE:B2:F2:72:D2:9F:E6:12:E4:77:DF:5A:1C:
        E4:9F:3E:14:62:DF:8F:D5:2A:A6:04:88:39:07:6E:BB:78:5A:74:2B:
        F5:D3:70:56:2F:D1:09:2C:B7:48:88:FF
parm:           swenc:Set to 1 for software crypto (default 0)
 (bool)
parm:           ips:Set to 0 to not use link power save (default 1)
 (bool)
parm:           swlps:Set to 1 to use SW control power save (default 0)
 (bool)
parm:           fwlps:Set to 1 to use FW control power save (default 1)
 (bool)
parm:           msi:Set to 1 to use MSI interrupts mode (default 1)
 (bool)
parm:           aspm:Set to 1 to enable ASPM (default 1)
 (int)
parm:           debug_level:Set debug level (0-5) (default 0) (int)
parm:           debug_mask:Set debug mask (default 0) (ullong)
parm:           disable_watchdog:Set to 1 to disable the watchdog (default 0)
 (bool)
parm:           int_clear:Set to 0 to disable interrupt clear before set (default 1)
 (bool)

Looks like driver name matches. And driver version gives me a clue that it is a driver from the kernel. While driver module size (according to lsmod) is equal and the driver version is greater for Ubuntu, how comes it is so slow on any distro but Mint? What else can I check to figure out the difference and how can I enable fast Wi-Fi on any other distro? With Linux Mint now I know for sure that it is possible. UPD: added modinfo output. The srcversion differs (as expected). The Linux Mint kernel/driver version is older. If it is a regression in newer Realtek driver/kernel, what is the best place to submit a bug report? UPD2: If I update linux Kernel from 5.4 to 5.8, wifi becomes slow. Looks like I need to submit a kernel bug. But before it I would like to check if the latest stable kernel (5.11) have the problem.

I am attempting to communicate with devices on my LAN via the internet. I have purchased a static IP for my router. When I log in to my router, the IP address displayed on the router GUI matches the IP address displayed if I search for my IP on the Internet, for example, by going to a "what is my IP" website. My problem is that the connection times out when I attempt to access my router over the Internet. I have tried: 1. When I enter my router's IP, as described above, into my browser, the connection hangs. Note: My browser was not on the same network as my router when I tried this. 2. When I ping my router's IP address using ping my.ip.address.here. This also hangs, reporting 100% packet failure. The result of (2) above inclines me to think something is going awry. Initially, I believed I was behind a CGNAT, such that any incoming request to my IP wouldn't know which of the many routers was mine. After purchasing a static IP, I believed the mapping should be 1-1, and any incoming request should know how to access my router. Can anyone advise what could be preventing connection to my router? ### Additional Info On my router's GUI, under the heading "Traffic Status", there is a subheading "Disabled Interface: WWAN". I cannot seem to find any option on the GUI to alter this, if this is indeed the cause. Following the "help" link to Zyxel's webpage , there are a number of differences between my GUI and what is implied in the instructions. Under "Web Interface Tutorials" is a section "Remote Access from WAN". This section advises navigating to "Maintenance > Remote Management > MGMT Services" within the GUI. However, the "Maintenance" section in my GUI does not contain a "Remote Management" subheading. Is there a means to disable this option and re-enable it? Is it possible for my make and model not to contain this feature, full stop? Any guidance is greatly appreciated. ### Attempt to enable PING Under the "Firewall" section of my router GUI, I have found a "Protocol" and "Access Control" menu. Within the "Protocol" section, I have added a "Protocol Entry":

Service name: Ping
Protocol: ICMP
ICMPtype: 0 /Echo-reply

Then, within the "Access Control" menu, I add a "New Access Control List Rule":

Source IP Address: Any/32
Destination IP Address: Any/32
Service: Ping
Action: ACCEPT

Unfortunately, when I PING my router's IP address, the connection hangs. ### LAN Setup In case it is relevant, my LAN information is listed as:

IP Address: 192.168.1.1
Subnet Mask: 255.255.255.0

Also, I note that my WAN IP is quoted as having a subnet mask of:

255.255.255.248

### Issue setting subnet mask to 0 Within the ACL Rule section of the router GUI, when attempting to allow ping access from the internet to my LAN device, I assume: 1. "Source IP Address" will be the IP address of the device, on the internet initiating the ping request. 2. "Destination IP Address" will be the IP address of the device on my LAN I wish to allow the ping request to be received. If I try to input a "Destination IP" of [LAN.Device.IP.Address]/0, the GUI displays the error message The maximum of prefix length is 32. ### Device details Router model: Zyxel EX3301-T0

I bought an Alfa AWUS1900 WLAN device for education purpose with Aircrack, because it has Linux support and some posts/reviews confirms that. Sadly I can't get the driver working in monitor mode, especially on the new 5er Kernel. ## My setup The notebook runs Ubunu 18.04.3 LTS with VirtualBox where I created a VM with the [latest Kali Linux](https://www.kali.org/downloads/) , which is 2019.3 at the time of writing. VirtualBox has the extension pack installed for USB 2 support. It runs as root for USB forwarding: ## My chipset Since I read reviews about users getting different chipsets for the same device type, I plugged the device in and verified to have the RTL8814AU chipset: root@kali:~# lsusb | grep -E "Realtek*" Bus 001 Device 002: ID 0bda:8813 Realtek Semiconductor Corp. RTL8814AU 802.11a/b/g/n/ac Wireless Adapter ## Not working drivers A snapshot was created before any driver was installed and after each non-working driver, I went back to the vanilla snapshot to have a clean system and make sure that no older driver influence the current one. ### zebulon2/rtl8814au [This driver](https://askubuntu.com/questions/981638/alfa-awus1900-driver-support/983834#983834) worked partially when using the Kali Linux snapshot image directly without upgrading packages (there are many updates avaliable). The device got detected and the network manager shows me avaliable APs as well as using nmcli dev wifi command. But the device is in managed mode: root@kali:~/rtl8814au# iw dev | grep type type managed I can't switch to monitor mode: root@kali:~/rtl8814au# airmon-ng check kill Killing these processes: PID Name 831 wpa_supplicant root@kali:~/rtl8814au# airmon-ng start wlan0 PHY Interface Driver Chipset phy0 wlan0 rtl8814au Realtek Semiconductor Corp. RTL8814AU 802.11a/b/g/n/ac ERROR adding monitor mode interface: command failed: Operation not supported (-95) Even not with ifconfig: root@kali:~/rtl8814au# ifconfig wlan0 down root@kali:~/rtl8814au# iwconfig wlan0 mode monitor Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Operation not permitted. dmesg lot entry when putting in monitor mode: [ 940.905187] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00 [ 940.905191] RTL871X: nolinked power save leave Some posts mentioned a bug in airmon-ng but say it should work with ifconfig. ### realtek-rtl88xxau-dkms According to [this thread in the kali forum](https://forums.kali.org/showthread.php?36296-EXTREME-WIFI-SUPPORT-Alfa-Networks-AWUS1900-WORKING) , there is a package called realtek-rtl88xxau-dkms in the repos that should contain all required drivers. So I installed his dependencies [like described here](https://forums.kali.org/showthread.php?36296-EXTREME-WIFI-SUPPORT-Alfa-Networks-AWUS1900-WORKING&p=79079#post79079) apt install dkms && apt-get install bc && apt-get install build-essential && apt-get install linux-headers-$(uname -r) then the driver package using apt-get install realtek-rtl88xxau-dkms and plugged in my usb wifi device. I'm wondering that I get some error about missing module or filename, but it's not clear for me what exactly is missing and if it's required (since it says installation completed): 88XXau.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.2.0-kali3-amd64/updates/ depmod.... DKMS: install completed. dmesg detects the new device, but after a few seconds it got disconnected: [ 1080.147957] usb 1-1: new high-speed USB device number 4 using ehci-pci [ 1080.595125] usb 1-1: New USB device found, idVendor=0bda, idProduct=8813, bcdDevice= 0.00 [ 1080.595131] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1080.595135] usb 1-1: Product: 802.11ac NIC [ 1080.595136] usb 1-1: Manufacturer: Realtek [ 1080.595137] usb 1-1: SerialNumber: 123456 [ 1087.695407] usb 1-1: USB disconnect, device number 4 On the first run, this was all I got. But the second approach shows also this VirtualBox error: ### aircrack-ng/rtl8812au I'm not sure if [aircrack-ng/rtl8812au](https://github.com/aircrack-ng/rtl8812au) is the same driver as the realtek-rtl88xxau-dkms apt-package, so I tried ./dkms-install.sh there but also no luck, just similar issues. Altough the snapshot of Kali Linux is outdated for several months (over 800 package updates for a vanilla installation), there seems no kernel update. The following kernel version is the same before and after updating all packages: Linux kali 5.2.0-kali2-amd64 #1 SMP Debian 5.2.9-2kali1 (2019-08-22) x86_64 GNU/Linux

Today I have installed VirtualBox on Debian 12 and using wifi bridge work, I can ping the vm using the same ip class of wlan0 wifi (88x2bu driver), but ip addr and ip link sh don't report interface 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp3s0: mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether ******** brd ****** 3: wlan0: mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ************ brd ********** permaddr ******* , where is the bridge? With other applications like kvm/qemu libvirt I ever failed to set any bridge with wlan (with ethernet is ok), how is possible that VirtualBox can use bridge and libvirt not? For libvirt I ever use the virbr solution: create a virbr interface that "point" to wlan something like this wifibr *** Trying a bridge fail brctl addif br0 wlan0 can't add wlan0 to bridge br0: Operation not supported Question: how virtualbox bridge work? Is possible to make something similar with libvirt? I prefer to use my wlan0 ip class

I have a tftp server on lan 192.168.0.0/24 I want a qemu vm reach it, with ethernet is simple a) First create br0 MAC1="52:54:$(dd if=/dev/urandom count=1 2>/dev/null | md5sum | sed 's/^\(..\)\(..\)\(..\)\(..\).*$/\1:\2:\3:\4/')"; nmcli con add ifname br0 type bridge con-name br0 bridge.mac-address $MAC1 b) then add eth0 as slave, then you can add vnet* or tap* interfaces with qemu or libvirt With wlan is impossible brctl addif br0 wlan1 can't add wlan1 to bridge br0: Operation not supported nmcli fail also with timeout So I have two solutions, create a "virbr" with libvirt and the use iptables rules for natting it, but the virbr must have a different lan address (192.168.1.0/24 or 10.2.1.0/24 or whatever you want but not an address of ip range used by wlan because exit with errors) or create an empty br0 with network-manager and then assign a ip address to it and with iptables route to wlan0 iptables -A FORWARD -i br0 -o wlan1 -j ACCEPT iptables -A FORWARD -i wlan1 -o br0 -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT iptables -t nat -A POSTROUTING -o wlan1 -j MASQUERADE but when I try to get a dhcp address from 192.168.0.0/24 lan it fail. Any advice to use 192.168.0.0/24 ip for wlan "bridge"? Thanks Edit: the iw command to "enable" the wlan0 as slave fail iw dev wlan1 set 4addr on command failed: Operation not supported (-95) Another thing: today I have installed VirtualBox on Debian 12 and using wifi bridge work, I can ping the vm using the same ip class of wlan0 wifi (88x2bu driver), but ip addr and ip link sh don't report interface, where is the bridge?

I have a computer, C, a router, R, and a Raspberry Pi, P.  They are connected: Internet R P C Now I want C to be able to access the internet. The P has wlan0 and eth0, so my first thought was to bridge eth0 and wlan0, but that is not possible due to the nature of Wi-Fi, I've learned. The next approach is to add a DHCP server to P and let C lease an IP number.  It works fine; ip route on C gives: `10.254.239.0/27 dev eth0 src 10.254.239.13 default via 10.254.239.10 dev eth0 ` and ifconfig on P gives

eth0      Link encap:Ethernet  HWaddr b8:27:eb:44:bb:71  
          inet addr:10.254.239.10  Bcast:10.254.239.31  Mask:255.255.255.224
          inet6 addr: fe80::3206:e7e:fb7e:23d5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:569 errors:0 dropped:0 overruns:0 frame:0
          TX packets:235 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:142936 (139.5 KiB)  TX bytes:50384 (49.2 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:1444 (1.4 KiB)  TX bytes:1444 (1.4 KiB)

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:11:ee:24  
          inet addr:192.168.0.106  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::2501:6a8:8bcf:4a40/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5415 errors:0 dropped:4989 overruns:0 frame:0
          TX packets:454 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:815495 (796.3 KiB)  TX bytes:49230 (48.0 KiB)

C can ping P but not R, leaving me to believe that P has some routing error. How can I configure P to pass traffic between R and C? ip route on P gives:

default via 192.168.0.1 dev wlan0  metric 303 
10.254.239.0/27 dev eth0  proto kernel  scope link  src 10.254.239.10 
192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.106  metric 303 

Also on P:

$ cat /proc/sys/net/ipv4/ip_forward
1

I downloaded Kali Linux WSL 2 Terminal to my Windows 10. However, it is not showing wlan0 even though I'm connected to the internet. Is there a way to solve this, or is my Wi-Fi adapter not compatible?

Error: airmon-ng did not find any wireless interfaces

wifi      = none (no device)

I'm running Gentoo. I have a HP laptop with the touch screen. I put the default GNOME on it. Problem was that Wayland didn't like touch screens. So I did the update and put X on it. Everything worked fine, until I saw that GNOME upgrade brought NetworkManager. And so I tried to switch to using it. Unfortunately that didn't work. My wlan0 interface failed to load. Looking into dmrsg I saw Ieee80211 phy0: Failed to add default virtual face There is no debug output in the dmesg. Next thing - I tried to switch back to using dhcpcd. But the same thing happened - I got exactly the same error. Unfortunately, even after I tried to turn on the debugging printouts nothing printed. I'm on the 6.6.21 kernel version right now. I can provide more info if asked, just don't know what. Does anybody know what could be the issue? And how to find the cause of the problem? The laptop doesn't have a wired network jack so I can't get online. Thank you. EDIT: dhcpcd is definitely running: ps aux | grep dhcp root 1455 0.0 0.0 3100 2324 ? S Jul 04 0.00 dhcpcd [manager] [ip4] [ip6] So it is definitely running. The output of ifconfig is as follows: lo: flags=73 mcu 65536 inet: 127.0.0.1 netmask 255.0.0.0 inet6: ::1 prefixlen 128 scopeId 0x18 loop: txqueuelen 1800 (local loopback) RX packet 0 bytes 0 (0.0.8) TX packets 0 bytes 0 (0.0.8) TIA!! EDIT: WaylandGnome /etc/init.d # lspci -v 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex Flags: bus master, fast devsel, latency 0 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) I/O Memory Management Unit Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) I/O Memory Management Unit Flags: bus master, fast devsel, latency 0, IRQ 24 Capabilities: Secure device Capabilities: MSI: Enable+ Count=1/4 Maskable- 64bit+ Capabilities: HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev c8) (prog-if 00 [VGA controller]) DeviceName: ATI EG BROADWAY Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] Flags: bus master, fast devsel, latency 0, IRQ 39, IOMMU group 0 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0000000 (64-bit, prefetchable) [size=8M] I/O ports at 2000 [size=256] Memory at f0c00000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: Vendor Specific Information: Len=08 Capabilities: Power Management version 3 Capabilities: Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: Secondary PCI Express Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Kernel driver in use: amdgpu Kernel modules: amdgpu 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio Subsystem: Hewlett-Packard Company Kabini HDMI/DP Audio Flags: bus master, fast devsel, latency 0, IRQ 35, IOMMU group 0 Memory at f0c60000 (64-bit, non-prefetchable) [size=16K] Capabilities: Vendor Specific Information: Len=08 Capabilities: Power Management version 3 Capabilities: Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: Vendor Specific Information: ID=0001 Rev=1 Len=010 Kernel driver in use: snd_hda_intel 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge Flags: fast devsel, IOMMU group 1 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port Flags: bus master, fast devsel, latency 0, IRQ 26, IOMMU group 1 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: f0b00000-f0bfffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: Power Management version 3 Capabilities: Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: Secondary PCI Express Kernel driver in use: pcieport 00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port Flags: bus master, fast devsel, latency 0, IRQ 27, IOMMU group 1 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: f0a00000-f0afffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: Power Management version 3 Capabilities: Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: Secondary PCI Express Kernel driver in use: pcieport 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge Flags: fast devsel, IOMMU group 2 00:08.0 Encryption controller: Advanced Micro Devices, Inc. [AMD] Carrizo Platform Security Processor Subsystem: Hewlett-Packard Company Carrizo Platform Security Processor Flags: bus master, fast devsel, latency 0, IRQ 3, IOMMU group 3 Memory at f0c40000 (64-bit, prefetchable) [size=128K] Memory at f0900000 (32-bit, non-prefetchable) [size=1M] Memory at f0c6f000 (32-bit, non-prefetchable) [size=4K] Memory at f0c6a000 (32-bit, non-prefetchable) [size=8K] Capabilities: MSI-X: Enable- Count=2 Masked- Capabilities: [5c] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: Power Management version 3 Capabilities: [a4] PCI Advanced Features 00:09.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Carrizo Audio Dummy Host Bridge Flags: fast devsel, IOMMU group 4 00:09.2 Audio device: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Audio Controller Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 34, IOMMU group 4 Memory at f0c64000 (32-bit, non-prefetchable) [size=16K] Capabilities: Power Management version 3 Capabilities: [a4] PCI Advanced Features Kernel driver in use: snd_hda_intel 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 20) (prog-if 30 [XHCI]) Subsystem: Hewlett-Packard Company FCH USB XHCI Controller Flags: bus master, fast devsel, latency 0, IRQ 18, IOMMU group 5 Memory at f0c68000 (64-bit, non-prefetchable) [size=8K] Capabilities: Power Management version 3 Capabilities: MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: MSI-X: Enable+ Count=8 Masked- Capabilities: [a0] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: Latency Tolerance Reporting Kernel driver in use: xhci_hcd 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 49) (prog-if 01 [AHCI 1.0]) Subsystem: Hewlett-Packard Company FCH SATA Controller [AHCI mode] Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19, IOMMU group 6 I/O ports at 2118 [size=8] I/O ports at 2124 [size=4] I/O ports at 2110 [size=8] I/O ports at 2120 [size=4] I/O ports at 2100 [size=16] Memory at f0c6c000 (32-bit, non-prefetchable) [size=1K] Capabilities: Power Management version 3 Capabilities: SATA HBA v1.0 Kernel driver in use: ahci 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 49) (prog-if 20 [EHCI]) Subsystem: Hewlett-Packard Company FCH USB EHCI Controller Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18, IOMMU group 7 Memory at f0c6d000 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci-pci 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 4a) Subsystem: Hewlett-Packard Company FCH SMBus Controller Flags: 66MHz, medium devsel, IOMMU group 8 Kernel driver in use: piix4_smbus 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11) Subsystem: Hewlett-Packard Company FCH LPC Bridge Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 8 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 0 Flags: fast devsel, IOMMU group 9 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 1 Flags: fast devsel, IOMMU group 9 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 2 Flags: fast devsel, IOMMU group 9 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 3 Flags: fast devsel, IOMMU group 9 Capabilities: [f0] Secure device 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 4 Flags: fast devsel, IOMMU group 9 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 5 Flags: fast devsel, IOMMU group 9 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) Subsystem: Hewlett-Packard Company RTS5229 PCI Express Card Reader Flags: fast devsel, IRQ 5, IOMMU group 1 Memory at f0b00000 (32-bit, non-prefetchable) [size=4K] Capabilities: Power Management version 3 Capabilities: MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: Express Endpoint, MSI 00 Capabilities: Advanced Error Reporting Capabilities: Device Serial Number 00-00-00-01-00-4c-e0-00 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 61) DeviceName: Intel WLAN Intel 7265NGWG.NVW Stone Peak 2 D0 ac 2x2 + BT 4 LE PCIe+USB NGFF 2230 WW non-vPro Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [Stone Peak 2 AC] Flags: bus master, fast devsel, latency 0, IRQ 37, IOMMU group 1 Memory at f0a00000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: Express Endpoint, MSI 00 Capabilities: Advanced Error Reporting Capabilities: Device Serial Number a4-02-b9-ff-ff-4a-8b-57 Capabilities: [14c] Latency Tolerance Reporting Capabilities: L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi WaylandGnome /etc/init.d # rc-update binfmt | boot bootmisc | boot cgroups | sysinit devfs | sysinit dhcpcd | default display-manager | default dmesg | sysinit elogind | boot fsck | boot hostname | boot hwclock | boot keymaps | boot killprocs | shutdown kmod-static-nodes | sysinit local | default nonetwork localmount | boot loopback | boot modules | boot mount-ro | shutdown mtab | boot net.wlan0 | default netmount | default ntp-client | default procfs | boot root | boot save-keymaps | boot save-termencoding | boot savecache | shutdown seedrng | boot swap | boot sysctl | boot sysfs | sysinit sysklogd | default systemd-tmpfiles-setup | boot systemd-tmpfiles-setup-dev | sysinit termencoding | boot udev | sysinit udev-trigger | sysinit WaylandGnome /etc/init.d # cat /etc/conf.d/net config_wlan0="dhcp" WaylandGnome /etc/init.d # lsmod Module Size Used by amdgpu 9805824 16 i2c_algo_bit 12288 1 amdgpu drm_ttm_helper 12288 1 amdgpu ttm 81920 2 amdgpu,drm_ttm_helper drm_exec 12288 1 amdgpu drm_suballoc_helper 12288 1 amdgpu amdxcp 12288 1 amdgpu drm_buddy 16384 1 amdgpu gpu_sched 49152 1 amdgpu drm_display_helper 159744 1 amdgpu wmi_bmof 12288 0 video 61440 1 amdgpu wmi 28672 2 video,wmi_bmof iwlmvm 548864 0 vboxnetflt 32768 0 vboxnetadp 24576 0 mac80211 1089536 1 iwlmvm vboxdrv 520192 2 vboxnetadp,vboxnetflt libarc4 12288 1 mac80211 iwlwifi 458752 1 iwlmvm cfg80211 1032192 3 iwlmvm,iwlwifi,mac80211 efivarfs 24576 1 WaylandGnome /etc/init.d # uname -a Linux WaylandGnome 6.6.21-gentoo #1 SMP PREEMPT_DYNAMIC Wed Apr 3 15:27:22 CDT 2024 x86_64 AMD FX-9800P RADEON R7, 12 COMPUTE CORES 4C+8G AuthenticAMD GNU/Linux

Is it possible to run two different network interfaces (e.g. being connected to two different wlan-networks) on one card in parallel on linux? If yes, how? If no, why not (I would be glad about a bit technical background). Update: I read a bit, and found out that it is possible to have several ip addresses assigned to the same network card (http://www.tecmint.com/create-multiple-ip-addresses-to-one-single-network-interface/) , but my problem is that I want to be connected to several wlan-networks (one ad-hoc-network and one usual network) in parallel. Is that possible? Due to a lack of a running unix os I am not able to check that. After request: My current network card is Intel Centrino Advanced-N 6230, but my final target is to do that on android, too (I thought that should be possible after android is a modified linux.... But my first approach would be on a usual pc, specs as above)

It seems that the kernel (?) puts the interface down and then up when wlan interface connected to some AP reconnect from one BSSID to another. Is it possible to prevent kernel from doing it? So interface stays up during this process?

I have multiple devices (A, B, C). Device A is a sensor that captures data and shares it with device C (Android) over a local Wi-Fi network. The problem is that the application to receive data only works on Android, and Android does not support being connected to two networks simultaneously, so when C connects to the Wi-Fi that A emits, it can correctly receive the data captured by A, but loses internet connection. I would like to know if a third device B (Ubuntu 23.10) with internet thanks to a 4G modem, can connect to the Wi-Fi network that A broadcasts and share internet through that Wi-Fi network so that C has internet when it connects to A's Wi-Fi. A is not configurable, it is a purchased device and I cannot modify anything. A emits a Wi-Fi signal and to receive data it is necessary to connect an Android device (C) to A's Wi-Fi network in order to receive data from its application. If A could connect to a hotspot issued by C there would be no problem since A and C would be connected and C would maintain an internet connection. However, A's app does not support that functionality and the only way to receive the data captured by A is to connect C to the Wi-Fi created by A. I would like to know if I can add another device (B), with an OS that does support simultaneous connection of network interfaces (for example Ubuntu) and share the internet through the Wi-Fi created by A. I have searched many similar questions about it, but none that solve my problem. In most of the questions asked, the internet is shared through a network cable or by creating a hotspot, however, I need to share the internet through the Wi-Fi network that A creates and not create a new one. On the other hand, I have found a lot of information about bridges and bonding, but I have not achieved favorable results either.

Following these instructions , I found that phy0 on my desktop should support wake on wlan and turned it on.

[root@Arch alex]# iw phy0 wowlan show
WoWLAN is enabled:
 * wake up on magic packet

However, when I suspend the system and try to wake it up from a distance, it doesn't work:

[alex@Archlaptop tmp]$ wol 44:E5:17:ED:9E:D2r
Waking up 44:E5:17:ED:9E:D2r...

And nothing happens. Furhermore, if I follow the Arch wiki , I don't get wake-on-wlan:

[root@Arch alex]# ethtool wlo1
Settings for wlo1:
        Link detected: yes

What is going on?

I have two network interfaces on a client PC, one wired, one wireless. The wired is connected directly to a server PC running DHCP, which gives the client PC a 10.0... address. The client PC also connects to a wireless router, which gives it a 192.168... address. This was all set up and detected automatically by NetworkManager. I am able to ping the server PC and wireless router. The problem is I want to use the wired connection as a LAN only, and the wireless for WAN access to the wider Internet. But NetworkManager thinks the opposite, and tries to use the LAN to go to the outside Internet. If I unplug the cable it correctly uses wireless. But I'd like to have them both connected at the same time. I'm running Debian unstable if that matters. Is there some way to configure this?

I have a Compaq CQ58 laptop with fresh Debian 12. I would like to fix one problem, namely the non-working WLAN on/off button. Constantly lights up yellow (it should be either yellow or blue) and does not respond to pressing. xev does not catch its pressing.

With the following configuration on Devuan Chimaera Linux: /etc/network/interfaces auto wlan0 iface wlan0 inet dhcp pre-up /sbin/wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf post-down /usr/bin/killall -q wpa_supplicant /etc/wpa_supplicant/wpa_supplicant.conf network={ ssid="MySSID" psk="redacted" } ctrl_interface=/run/wpa_supplicant update_config=1 dhclient only runs when the interface first comes up. If I use ifconfig wlan0 down, the IP address is retained while down and ifconfig wlan0 up brings the interface back up without running dhclient. Unfortunately I have a custom /etc/dhcp/dhclient-exit-hooks.d/wlan0-routes which adds custom routes, calculated from the default route provided by dhclient. When I bring wlan0 down, the custom routes are lost, as expected. When I bring wlan0 up, dhclient does not run and so the custom routes are not re-added. --- Update: There seems to be a difference in the behaviour of ifconfig wlan0 down (which caused this) and ifdown wlan0. root@demo:~# ifconfig wlan0 down root@demo:~# ip addr show wlan0 9: wlan0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 00:0e:8e:4c:f6:a3 brd ff:ff:ff:ff:ff:ff inet 192.168.98.196/24 brd 192.168.98.255 scope global dynamic wlan0 valid_lft 7130sec preferred_lft 7130sec root@demo5:~# ifconfig wlan0 up ... root@demo5:~# ifdown wlan0 root@demo5:~# ip addr show wlan0 9: wlan0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 00:0e:8e:4c:f6:a3 brd ff:ff:ff:ff:ff:ff When I use ifdown wlan0 instead of ifconfig wlan0 down dhclient is called when I bring the interface up, and everything works as it ought. What is the difference between ifconfig wlan0 down and ifdown wlan0?