mjhjmtu

First time post so sorry if I do anything wrong!

I'm trying to create a wireless ad-hoc network using two RT5370 wireless adapters and two Ubuntu laptops. I've followed several tutorials, none of which have worked. In addition, I have completely reinstalled Ubuntu on one computer, and tried to make a mesh network on two Debian computers (Raspberry Pis, newly flashed with Raspbian Stretch Lite). The commands I have tried are:

sudo ip link set down wlx00f0003212b5

sudo iwconfig wlx00f0003212b5 mode ad-hoc essid my-mesh-network ap 02:de:ad:be:ef:00 channel 1

sudo ip link set up wlx00f0003212b5

sudo ip addr add dev wlx00f0003212b5 192.168.1.1/24

(I have predictable network interface names turned on, which causes the interface names starting with wlx).

I ran this command on both nodes, the only differences were that the network interface had a different name and I assigned a different IP address (192.168.1.2) to the second node.

The nodes are unable to ping each other. They are able to ping themselves using the IP addresses I assigned, which makes me think that this is an issue in layer 2. I have done similar ad-hoc connections over an Ethernet cable without any issues.

I have confirmed (using iw list as well as by reading other comments online) that these network adapters support IBSS (ad-hoc) networking. The ESSID of the network is visible to other devices within range.

I have tried manually adding the MAC address of the other node to the ARP table, which causes pings to not reach their destination.

I have also tried using the "Edit Connections" dialog in the Ubuntu GUI to make the connection, which also did not work.

Output of iwconfig: (I have removed other network interfaces)

wlx00f0003212b5 IEEE 802.11 ESSID:off/any
 Mode:Ad-Hoc Frequency:2.412 GHz Cell: 02:DE:AD:BE:EF:00
 Tx-Power=20 dBm
 Retry short long limit:2 RTS thr:off Fragment thr:off
 Power Management:off

Output of ip link:

8: wlx00f0003212b5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1532 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether 00:f0:00:32:12:b5 brd ff:ff:ff:ff:ff:ff

Output of ip addr:

8: wlx00f0003212b5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1532 qdisc mq state DOWN group default qlen 1000
link/ether 00:f0:00:32:12:b5 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global wlx00f0003212b5
 valid_lft forever preferred_lft forever
inet6 fe80::2f0:ff:fe32:12b5/64 scope link 
 valid_lft forever preferred_lft forever

Output of ip route:

192.168.1.0/24 dev wlx00f0003212b5 proto kernel scope link src 192.168.1.1 metric 600 linkdown

Output of iw wlx00f0003212b5 info:

Interface wlx00f0003212b5
 ifindex 8
 wdev 0x400000001
 addr 00:f0:00:32:12:b5
 type IBSS
 wiphy 4

Output of iw list:

Wiphy phy7
 max # scan SSIDs: 4
 max scan IEs length: 2257 bytes
 Retry short long limit: 2
 Coverage class: 0 (up to 0m)
 Device supports RSN-IBSS.
 Supported Ciphers:
 * WEP40 (00-0f-ac:1)
 * WEP104 (00-0f-ac:5)
 * TKIP (00-0f-ac:2)
 * CCMP (00-0f-ac:4)
 * 00-0f-ac:10
 * GCMP (00-0f-ac:8)
 * 00-0f-ac:9
 Available Antennas: TX 0 RX 0
 Supported interface modes:
 * IBSS
 * managed
 * AP
 * AP/VLAN
 * monitor
 * mesh point
 Band 1:
 Capabilities: 0x17e
 HT20/HT40
 SM Power Save disabled
 RX Greenfield
 RX HT20 SGI
 RX HT40 SGI
 RX STBC 1-stream
 Max AMSDU length: 3839 bytes
 No DSSS/CCK HT40
 Maximum RX AMPDU length 32767 bytes (exponent: 0x002)
 Minimum RX AMPDU time spacing: 2 usec (0x04)
 HT TX/RX MCS rate indexes supported: 0-7, 32
 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) (no IR)
 * 2472 MHz [13] (20.0 dBm) (no IR)
 * 2484 MHz [14] (20.0 dBm) (no IR)
 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
 * set_tx_bitrate_mask
 * frame
 * frame_wait_cancel
 * set_wiphy_netns
 * set_channel
 * set_wds_peer
 * probe_client
 * set_noack_map
 * register_beacons
 * start_p2p_device
 * set_mcast_rate
 * connect
 * disconnect
 * Unknown command (104)
 * Unknown command (121)
 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:
 * # AP, mesh point <= 8,
 total <= 8, #channels <= 1
 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
 Driver supports full state transitions for AP/GO clients
 Driver supports a userspace MPM

(These were run on the first node; the second node has identical outputs except for the IP address and WiFi interface name. I would be happy to post more logs if that information is needed.)

I have not installed any firewalls or other software that could be blocking the pings.

What could be the cause of this issue?