#StackBounty: #networking #wireless #security #vpn How can I block traffic over wifi before the VPN connects?

Bounty: 50

I’d like to use a VPN when on public wifi for security. In order to establish my OpenVPN tunnel I need a working network connection. When I connect to a public wifi access point there is a window of time after connecting but before my VPN client is launched, connects and updates the route table, during which traffic from my system travels unencrypted over public wifi.

How can I cause wifi to pass no traffic except traffic destined for my OpenVPN server during that window of time?

Extra credit : Is there a way to whitelist wifi networks as trusted (like my home or work wifi) such that all traffic is allowed as I won’t be using a VPN?


Get this bounty!!!

#StackBounty: #networking #wireless #bash #network-manager How to reset network manager without downtime?

Bounty: 50

I have an unstable WiFi connection, and the bandwidth frequently reaches 0 without actual disconnection (it is connected but without data transfer). Resetting the network manager by

sudo service network-manager restart

perfectly fixes the problem. However, I have two issues:

  1. How can I reset the network manager without a downtime? With the above command, any ongoing download will be interrupted. Is it possible to keep the current connection while resetting?
  2. How can I write a bash script to periodically check the network connection and reset it if there is no data transfer?

I use Ubuntu 20.04.


Get this bounty!!!

#StackBounty: #networking #wireless #20.04 #atheros #network-bridge Transparently bridge (not route) a wired connection to act as anoth…

Bounty: 100

My new, shiny, home NAS-computer, running Ubuntu 20.04, has a gigabit wired connection and an ath-9k chipset dual-band (2.5 / 5 GHz) wifi card. My current wireless AP only has a 2.5 GHz radio, and in my region 2.5 GHz is fairly congested. I would like to bridge from the lan to a new 5 GHz wireless network using the new computer, but using the same DHCP server / default gateway / DNS servers as the lan / Wifi at the moment. This is because I have a single-board computer as a default gateway, transparently ad-blocking (amongst other things). I’ve achieved this by just disabling the DHCP server on my ISP’s supplied router and using my own instead (which is also the gateway, routing packets to the router as the only device on it)

A brief ascii-art description of what I have is below:

+----+      +------------------+
| WAN+------+ISP Router        |
+----+      +------------------+         +--------------------+
            |1000-Base-T       +---------+LAN                 |
            |2.4 GHz (WPA2/PSK)+-------+ +--------------------+    +-----------------+
            +------------------+       | |SBC DHCPd / DNS / GW+----+Wired clients (*)|
                                       | +--------------------+    +-----------------+
                                       |
                                       | +-----------------------+
                                       +-+2.4GHz Wireless clients|
                                         +-----------------------+

I believe I’d like to configure the computer as a layer-2 bridge between its wired connection and wifi. I don’t want to use hostapd as I don’t want it to be doing NAT and routing — I might want to ssh from a wired device to a wireless one that may be associated with it. I’d also like devices to seamlessly switch between 2.4 & 5 GHz as appropriate — and I believe that doing that is as simple as having the same SSID, authentication method (i.e. WPA2/PSK) and key.

In short, I think that I’d like to change the above diagram to include a "5 GHz Wireless clients" at the node marked (*).

My card supports AP mode and quite a lot of other features: here’s the output of lshw and the (very long!) output of iw list:

     *-network
                          description: Wireless interface
                          product: AR93xx Wireless Network Adapter
                          vendor: Qualcomm Atheros
                          physical id: 0
                          bus info: pci@0000:03:00.0
                          logical name: wlp3s0
                          version: 01
                          serial: 14:cc:20:10:a6:fa
                          width: 64 bits
                          clock: 33MHz
                          capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless
                          configuration: broadcast=yes driver=ath9k driverversion=5.4.0-39-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11
                          resources: irq:101 memory:fc900000-fc91ffff memory:fc920000-fc92ffff
      ----
# iw list
Wiphy phy0
    max # scan SSIDs: 4
    max scan IEs length: 2257 bytes
    max # sched scan SSIDs: 0
    max # match sets: 0
    max # scan plans: 1
    max scan plan interval: -1
    max scan plan iterations: 0
    Retry short limit: 7
    Retry long limit: 4
    Coverage class: 0 (up to 0m)
    Device supports RSN-IBSS.
    Device supports AP-side u-APSD.
    Device supports T-DLS.
    Supported Ciphers:
        * WEP40 (00-0f-ac:1)
        * WEP104 (00-0f-ac:5)
        * TKIP (00-0f-ac:2)
        * CCMP-128 (00-0f-ac:4)
        * CCMP-256 (00-0f-ac:10)
        * GCMP-128 (00-0f-ac:8)
        * GCMP-256 (00-0f-ac:9)
        * CMAC (00-0f-ac:6)
        * CMAC-256 (00-0f-ac:13)
        * GMAC-128 (00-0f-ac:11)
        * GMAC-256 (00-0f-ac:12)
    Available Antennas: TX 0x7 RX 0x7
    Configured Antennas: TX 0x7 RX 0x7
    Supported interface modes:
         * IBSS
         * managed
         * AP
         * AP/VLAN
         * monitor
         * mesh point
         * P2P-client
         * P2P-GO
         * outside context of a BSS
    Band 1:
        Capabilities: 0x11ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 3839 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 8 usec (0x06)
        HT TX/RX MCS rate indexes supported: 0-23
        Bitrates (non-HT):
            * 1.0 Mbps
            * 2.0 Mbps (short preamble supported)
            * 5.5 Mbps (short preamble supported)
            * 11.0 Mbps (short preamble supported)
            * 6.0 Mbps
            * 9.0 Mbps
            * 12.0 Mbps
            * 18.0 Mbps
            * 24.0 Mbps
            * 36.0 Mbps
            * 48.0 Mbps
            * 54.0 Mbps
        Frequencies:
            * 2412 MHz [1] (20.0 dBm)
            * 2417 MHz [2] (20.0 dBm)
            * 2422 MHz [3] (20.0 dBm)
            * 2427 MHz [4] (20.0 dBm)
            * 2432 MHz [5] (20.0 dBm)
            * 2437 MHz [6] (20.0 dBm)
            * 2442 MHz [7] (20.0 dBm)
            * 2447 MHz [8] (20.0 dBm)
            * 2452 MHz [9] (20.0 dBm)
            * 2457 MHz [10] (20.0 dBm)
            * 2462 MHz [11] (20.0 dBm)
            * 2467 MHz [12] (20.0 dBm)
            * 2472 MHz [13] (20.0 dBm)
            * 2484 MHz [14] (disabled)
    Band 2:
        Capabilities: 0x11ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 3839 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 8 usec (0x06)
        HT TX/RX MCS rate indexes supported: 0-23
        Bitrates (non-HT):
            * 6.0 Mbps
            * 9.0 Mbps
            * 12.0 Mbps
            * 18.0 Mbps
            * 24.0 Mbps
            * 36.0 Mbps
            * 48.0 Mbps
            * 54.0 Mbps
        Frequencies:
            * 5180 MHz [36] (23.0 dBm)
            * 5200 MHz [40] (23.0 dBm)
            * 5220 MHz [44] (23.0 dBm)
            * 5240 MHz [48] (23.0 dBm)
            * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
            * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
            * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
            * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
            * 5500 MHz [100] (disabled)
            * 5520 MHz [104] (disabled)
            * 5540 MHz [108] (disabled)
            * 5560 MHz [112] (disabled)
            * 5580 MHz [116] (disabled)
            * 5600 MHz [120] (disabled)
            * 5620 MHz [124] (disabled)
            * 5640 MHz [128] (disabled)
            * 5660 MHz [132] (disabled)
            * 5680 MHz [136] (disabled)
            * 5700 MHz [140] (disabled)
            * 5745 MHz [149] (30.0 dBm)
            * 5765 MHz [153] (30.0 dBm)
            * 5785 MHz [157] (30.0 dBm)
            * 5805 MHz [161] (30.0 dBm)
            * 5825 MHz [165] (30.0 dBm)
    Supported commands:
         * new_interface
         * set_interface
         * new_key
         * start_ap
         * new_station
         * new_mpath
         * set_mesh_config
         * set_bss
         * authenticate
         * associate
         * deauthenticate
         * disassociate
         * join_ibss
         * join_mesh
         * remain_on_channel
         * set_tx_bitrate_mask
         * frame
         * frame_wait_cancel
         * set_wiphy_netns
         * set_channel
         * set_wds_peer
         * tdls_mgmt
         * tdls_oper
         * probe_client
         * set_noack_map
         * register_beacons
         * start_p2p_device
         * set_mcast_rate
         * connect
         * disconnect
         * channel_switch
         * set_qos_map
         * set_multicast_to_unicast
    Supported TX frame types:
         * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    Supported RX frame types:
         * IBSS: 0x40 0xb0 0xc0 0xd0
         * managed: 0x40 0xd0
         * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * mesh point: 0xb0 0xc0 0xd0
         * P2P-client: 0x40 0xd0
         * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * P2P-device: 0x40 0xd0
    software interface modes (can always be added):
         * AP/VLAN
         * monitor
    valid interface combinations:
         * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1,
           total <= 2048, #channels <= 1, STA/AP BI must match
    HT Capability overrides:
         * MCS: ff ff ff ff ff ff ff ff ff ff
         * maximum A-MSDU length
         * supported channel width
         * short GI for 40 MHz
         * max A-MPDU length exponent
         * min MPDU start spacing
    Device supports TX status socket option.
    Device supports HT-IBSS.
    Device supports SAE with AUTHENTICATE command
    Device supports low priority scan.
    Device supports scan flush.
    Device supports AP scan.
    Device supports per-vif TX power setting
    P2P GO supports CT window setting
    Driver supports full state transitions for AP/GO clients
    Driver supports a userspace MPM
    Device supports active monitor (which will ACK incoming frames)
    Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
    Device supports configuring vdev MAC-addr on create.
    Supported extended features:
        * [ RRM ]: RRM
        * [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
        * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
        * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
        * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
        * [ AIRTIME_FAIRNESS ]: airtime fairness scheduling

I’ve tried to do this with bridge-utils, i.e. by bridging the interfaces directly:

   $ brctl addbr br0
   $ brctl addif br0 enp4s0 wlp3s0

Unfortunately, this stopped all DNS resolution on the computer (!) and resulted in some ‘interesting’ routing errors I didn’t understand: e.g. I could ping 8.8.8.8 but not dig @8.8.8.8 google.com. Even doing

   $ brctl br0 down
   $ brctl delbr br0

still resulted in a restart of /etc/init.d/networking.

I don’t understand why this doesn’t work. I’ve also tried using Ubuntu’s network-manager gui, creating a new ‘shared’ AP — which just opens hostapd and also googled extensively, but can’t find a clear answer. I know that network topologies with multiple wireless bridges definitely exist — what’s the simplest way to configure it?


Get this bounty!!!

#StackBounty: #drivers #wireless #20.04 Ubuntu 20.04 wifi not working on Mac

Bounty: 50

I used ubuntu 16.04 and 18.04 and they were able to work with wifi after following below guides:

This time with Ubuntu 20.04, none of above works.

Output of command lspci -knn | grep Net -A3; rfkill list as below:

02:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM57765 Gigabit Ethernet PCIe [14e4:16b4] (rev 10)
    Subsystem: Broadcom Inc. and subsidiaries NetXtreme BCM57765 Gigabit Ethernet PCIe [14e4:16b4]
    Kernel driver in use: tg3
    Kernel modules: tg3
02:00.1 SD Host controller [0805]: Broadcom Inc. and subsidiaries BCM57765/57785 SDXC/MMC Card Reader [14e4:16bc] (rev 10)
0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

I wonder why Ubuntu does not fix this issue.


Get this bounty!!!

#StackBounty: #networking #drivers #wireless #lubuntu #20.04 Lubuntu 20.04 wifi intermittent problem

Bounty: 50

I have an issue with the wifi in a HP 15-db0598sa that I’ve installed lubuntu 20.04 on.

Pinging google.com gives typical output of the form:

64 bytes from lhr25s26-in-f14.1e100.net (172.217.169.14): icmp_seq=171 ttl=53 time=12.3 ms
64 bytes from lhr25s26-in-f14.1e100.net (172.217.169.14): icmp_seq=172 ttl=53 time=96.4 ms
64 bytes from lhr25s26-in-f14.1e100.net (172.217.169.14): icmp_seq=175 ttl=53 time=1026 ms
64 bytes from lhr25s26-in-f14.1e100.net (172.217.169.14): icmp_seq=176 ttl=53 time=11.2 ms
64 bytes from lhr25s26-in-f14.1e100.net (172.217.169.14): icmp_seq=177 ttl=53 time=11.4 ms
64 bytes from lhr25s26-in-f14.1e100.net (172.217.169.14): icmp_seq=178 ttl=53 time=10.3 ms
64 bytes from lhr25s26-in-f14.1e100.net (172.217.169.14): icmp_seq=179 ttl=53 time=10.5 ms
64 bytes from lhr25s26-in-f14.1e100.net (172.217.169.14): icmp_seq=181 ttl=53 time=1035 ms
64 bytes from lhr25s26-in-f14.1e100.net (172.217.169.14): icmp_seq=182 ttl=53 time=22.9 ms

where the ping varies from ~10ms (as on my other machines) up to > 1000 ms, with the odd ping (about 24% packet loss) dropped (such as between 172 and 175 and 179 and 181 above).

The output of lspci -knn | grep Net -A3 is as follows:

03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723]
        DeviceName: WLAN
        Subsystem: Hewlett-Packard Company RTL8723DE 802.11b/g/n PCIe Adapter [103c:8319]
        Kernel driver in use: rtw_pci

I have disabled IPv6 on the dhcp as in this answer: https://askubuntu.com/a/1180403/489692

In furtherance to DESGUA’s answer, I changed /etc/dhcp/dhclient.conf. More specifically, I deleted line 18:

dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,

I eventually disconnected wifi and reconnected.

and that ameliorated some issues, but the ping is still intermittently ~10ms and >1000ms.

Are there any other configuration settings I could use to improve the stability of the connection (besides using wired networking – this laptop will be in a different room to the router so this is possible, but I’d prefer to use the wireless).

To add: I’ve got an older machine using Ubuntu 18.04 in the same location, and the ping there is fine:

64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=4 ttl=53 time=12.8 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=5 ttl=53 time=11.6 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=6 ttl=53 time=12.1 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=7 ttl=53 time=11.0 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=8 ttl=53 time=11.0 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=9 ttl=53 time=21.8 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=10 ttl=53 time=11.3 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=11 ttl=53 time=11.5 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=12 ttl=53 time=12.3 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=13 ttl=53 time=13.2 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=14 ttl=53 time=11.6 ms
64 bytes from ams16s21-in-f14.1e100.net (216.58.212.206): icmp_seq=15 ttl=53 time=11.5 ms

EDIT: I have tried installing the driver here (for RTL8723DE) https://github.com/lwfinger/rtlwifi_new/tree/extended
and the output of lspci -knn | grep Net -A3 remains:

03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723]
        DeviceName: WLAN
        Subsystem: Hewlett-Packard Company RTL8723DE 802.11b/g/n PCIe Adapter [103c:8319]
        Kernel driver in use: rtw_pci

so it looks like the new drive hasn’t installed. I’m at a complete loss now


Get this bounty!!!

#StackBounty: #networking #wireless #18.04 #atheros Weak Wifi Signal Ubuntu 18.04 Qualcomm Atheros QCA6174 802.11ac

Bounty: 50

I’ve been using Ubuntu 18.04 for a while, but a few days ago the wifi signal became weak to the point I can’t connect if I’m not really close to the router.
Other devices can connect in the same wireless from longer distances.
I already tried solutions from other posts, such as this one and this, nothing worked.
I suspect it started after an update.

lspci output:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 930M] (rev a2)
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 07)

lshw -class network output:

*-network                 
       description: Wireless interface
       product: QCA6174 802.11ac Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 32
       serial: 40:49:0f:fe:23:55
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath10k_pci driverversion=4.18.0-17-generic firmware=WLAN.RM.2.0-00180-QCARMSWPZ-1 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:127 memory:d5000000-d51fffff
  *-network
       description: Ethernet interface
       product: RTL810xE PCI Express Fast Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: enp3s0
       version: 07
       serial: f4:8e:38:e4:53:89
       size: 10Mbit/s
       capacity: 100Mbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
       resources: irq:17 ioport:d000(size=256) memory:d5204000-d5204fff memory:d5200000-d5203fff

Thanks in advance


Get this bounty!!!

#StackBounty: #wireless #network-manager #20.04 #airmon-ng Ubuntu 20.04 crashing while trying to set wifi interface to monitor mode

Bounty: 50

I am working on Ubuntu 20.04 and just installed Aircrack-ng 1.6 - (C) 2006-2020 Thomas d'Otreppe when i try to run sudo airmon-ng start wlp3s0 ubuntu crashed and restart automatically i tried multiple times but no luck

bhupesh@Laptop:~$ sudo airmon-ng check
[sudo] password for bhupesh: 
Found 4 processes that could cause trouble.
Kill them using 'airmon-ng check kill' before putting
the card in monitor mode, they will interfere by changing channels
and sometimes putting the interface back in managed mode

    PID Name
    814 avahi-daemon
    821 NetworkManager
    862 wpa_supplicant
    867 avahi-daemon

tried airmon-ng check kill

WIFI Drivers:

bhupesh@Laptop:~$ sudo lshw -C network
  *-network                 
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: enp2s0
       version: 15
       serial: 48:ba:4e:29:9f:6b
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII
       resources: irq:31 ioport:3000(size=256) memory:f0304000-f0304fff memory:f0300000-f0303fff
  *-network
       description: Wireless interface
       product: RTL8723DE 802.11b/g/n PCIe Adapter
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: wlp3s0
       version: 00
       serial: d4:6a:6a:12:c6:f1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rtw_pci driverversion=5.4.0-28-generic firmware=N/A ip=192.168.43.113 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:36 ioport:2000(size=256) memory:f1000000-f100ffff

by referring this anwser

tried reinstalling Aircrack-ng

and have dependencies installed : libnl-3-dev libssl-dev sqlite3 libsqlite3-dev libnl-genl-3-dev


Get this bounty!!!

#StackBounty: #networking #wireless #network-manager #raspberrypi #realtek-wireless Ubuntu server 20.04 ad-hoc network usb dongle

Bounty: 100

I’m trying to setup an ad-hoc (mesh) network on Raspberry Pi 4s running Ubuntu Server 20.04 LTS – through USB dongles. The network does not need to connect to the internet (this is just to form an intranet). From a fresh install, I just add sudo apt-get install xubuntu-desktop and start my setup.

  1. Install rtl88x2bu drivers for the dongles from this repo (as per README, also seen here and here).
sudo apt-get install dkms bc git
git clone https://github.com/cilynx/rtl88x2bu
cd rtl88x2bu
VER=$(sed -n 's/PACKAGE_VERSION="(.*)"/1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
  1. Plug in dongle and setup the wlan1 interface as per the WifiDocs.
Set ip=192.168.1.1, netmask=255.255.255.0, blank gateway.

Note: I tried with and without ignoring ipv6 as per this answer.

Note: the netmask is indicated as 24 if I close and reopen the nm-connection-editor.

My config:

conn_config_wifi

conn_config_ipv4

conn_config_ipv6

  1. (I tried with and without this step) I bring down the other interfaces (eth0 and wlan0) with sudo ip link set [interface] down – as the WifiDocs mention

If you have more than one interface with link-local addresses there can be some routing confusion

I also tried doing all these steps by making a NetworkManager yaml, but I get the same results.

I can see the network being broadcast, but running a ping command fails – no error message, it just hangs until I ctrl+c and then indicates 100% packet loss.

I’d be happy with any solution that gets two Pis talking to each other via ad-hoc through the dongles, but especially a NetworkManager GUI (as seen) or a netplan because I’ve looked at them. However, any solution works.

If it turns out the dongles (which use rtl88x2bu drivers) are incompatible with this project, a confirmation that the setup was done correctly would be great so I can track down an rt2x00 dongle as per the wiki.

Logs:

logs_lsusb_ping

logs_dmesg


Get this bounty!!!