Using my laptop with Ubuntu 24.04 I'd like to simulate a device (a mobile camera) which normally broadcasts a Wi-Fi network and runs a REST server on port 8099 (by sending REST messages to that server it is possible to control the camera). The workflow with the actual camera looks like this: 1. Turn on the camera. 1. Connect the PC to camera's Wi-Fi network. 1. Check gateway address of the network (e.g., 192.168.1.10). 1. Manipulate the camera using its REST API (e.g., to take a photo, send HTTP GET message to http://192.168.1.10:8099/api/takePhoto ). The "simulated" Wi-Fi network broadcasted by the laptop should use IPv4 addressing and should have gateway address – as the real camera device is controlled by sending REST messages to gateway address. No connection to the Internet is needed. I've tried to setup a hotspot and than use nm-connection-editor to change its parameters: * "Wi-Fi" tab * Mode: Ad-hoc * "IPv4 Settings" tab * Method: Manual * Address #1 * Address: 192.168.1.100 * Netmask: 24 * Gateway: 192.168.1.1 * Require IPv4 addressing for this connection to complete: ON * "IPv6 Settings" tab * Method: Disabled but the results are not satisfactory – when I connect to that Wi-Fi network on my Windows 10 machine, I see only IPv6 address and no gateway address. When I try to obtain gateway IP address of this network, I get 0.0.0.0. Is it at all possible to setup the network I desire on Ubuntu 24.04? Is so, what should I do to achieve intended results? PS I have almost no experience with networking.

I have 4 raspberry PI connected through an ad-hoc network. They have the following addresses: **169.254.1.1 169.254.1.2 169.254.1.3 169.254.1.4** I need to fix the route as follow: **169.254.1.1** --> **169.254.1.2** --> **169.254.1.3** --> **169.254.1.4** Currently, I'm using B.A.T.M.A.N. protocol for mesh ad-hoc networks. I tried the **ip route add** command but it doesn't work. ---------- **EDIT** I tried to use ebtables to filter traffic from **MAC addresses** using

$ebtables -A INPUT -s [*mac address*] -j DROP

The rule is added correctly but it doesn't work, maybe I did something wrong with the syntax...

### I ran into trouble extending my existing Batman Mesh with several new Wifi devices. * The existing configuration worked fine for years on the existing devices. * All relevant systems (now) run up2date 5.x kernels (Debian10.X+bpo, OpenWRT master). ### Wifi connection stup specifics: * WPA3/SAE CCMP is currently showing as "negotiated" for the existing IBSS mesh partners. * Currently participating Wifi chipsets: * QCA9880 (ath10k, Archer C7s/OpenWRT) - Work great, Sub-MS latency, ~600-1100 MBit negotiated. * IPQ4028 (ath10k, B1300/OpenWRT) - connects reliably, but has higher latency than ^ (+~1.5ms). ### Things I'm aware of: * The wanted connection type, IBSS (f.k.a. Adhoc), limits me to 7 per "cell"/frequency. * The other "mesh" type, 802.11s (my first choice), is supported even less well by devices/drivers. Here's the working configuration for wpa-supplicant for the existing 4 devices:

ap_scan=2
country=LU
passive_scan=1
network={
        scan_ssid=0
        ssid="MYSSID"
        key_mgmt=WPA-PSK WPA-PSK-SHA256 SAE
        mode=1
        fixed_freq=1
        frequency=5200
        ht40=1
        vht=1
        max_oper_chwidth=1
        psk="The correct passphrase"
        proto=RSN
        ieee80211w=1
        bssid=aa:Sa:me:For:Al:ll
        beacon_int=5000
}

(I know, the target systems have all prerequsites, because I can make this config work with an old USB stick on both) ### The problematic new devices/combinations are: * Amd Jaguar with miniPCI QCA9377 (ath10k) - fails to connect to IBSS * Intel i5 with miniPCI 3160 Wifi (iwlwifi) - fails to connect to IBSS * Both of the above with Various USB Adapters: * Mediatek mt76x2u, 0e8d:7612, ASIC:76120044, ROM: 20141115060606a, FW:201507311614 * connects __fine__, __very__ low latency, **crashes host hard** soon. * Ralink MT7610U (Archer T2U) mt76x0u, 148f:761a, ASIC 76100002, EEPROM ver:02 fae:01 * connects __fine__, __very__ low latency, **crashes host hard** soon. * Realtek RTL88x2bu AC1200 Techkey, [88x2bu(dkms)](https://github.com/morrownr/88x2bu) 0bda:b812 * fails to connect to IBSS Originally I started with the QCA9377 in the AMD rig, and this is the main reason for this Question, but while testing/diagnosing I got the above results with the other cards/systems, and would like to now also know, how to get them to join a VHT RSN-IBSS network. Notes: * I can post more details, and will edit in requested command output. * Mesh Conf is fairly standard for a batman L2 mesh using several wired/wireless link( type)s. * The links are backhaul links, they transport BATMAN ethertype encapsulating several L2 VLANs. * To transport MTU1500 w/o fragmentation, the phy links __must__ run at MTU 1560+ * The current Mesh participants run at MTU 2304, the WIFI maximum. (Ready to compromise on that) * All of the above wifi adapters list IBSS with RSN in the iw phy output

I need to create a open Ad hoc network on Ubuntu 18.04 , the nm-connection-editor throws up an error when i try to create a new network: Cannot save connection due to error: Invalid setting Wi-Fi: 802-11-wireless.ssid: property is missing What could I be doing wrong here?

I am currently working on setting up a wireless mesh network using babeld as the routing algorithm. The documentation is very sparse, and most of the configuration guides I've seen online are using the deprecated ifconfig command. I could obviously just install ifconfig and run the commands as-is. But, if possible, I would prefer to not create an unnecessary dependency on ifconfig, and just use the built-in iproute2-based commands instead. So I have been converting ifconfig commands I'm coming across into their corresponding ip versions (e.g. ifconfig eth0 up --> ip link set eth0 up) However, today I came across the following babeld configuration script : ifconfig wlan0 down iwconfig wlan0 mode ad-hoc essid reseaulibre.ca ap 02:CA:FF:EE:BA:BE channel 9 ifconfig wlan0 up avahi-autoipd wlan0 ifconfig wlan0:avahi netmask 255.255.255.255 babeld -D wlan0:avahi wlan0 ... and I don't understand how to convert the following line into a corresponding ip command: ifconfig wlan0:avahi netmask 255.255.255.255 **What is an equivalent command using ip, that would work in the context of the above configuration script?**

I've been trying to get my machine to work with Wi-Fi Direct and also ad-hoc mode. I have two dongles, one for each mode. I'm following this tutorial on how to set up wifi ad-hoc: WiFi Ad-hoc Network *edit* I followed the following steps: I modified the /etc/network/interfaces document to be the following: auto wlan0 iface wlan0 inet static address 192.168.2.30 netmask 255.255.255.0 wireless-channel 1 wireless-essid IBSSNetwork wireless-mode ad-hoc wlan0 was my adapter for IBSS mode and wlan1 is my adapter for Wi-Fi direct. I also enabled Wi-Fi direct in the wpa_supplicant configuration. My other computer that I'm trying to communicate with using ad-hoc had the following in the /etc/network/interfaces document: auto wlan0 iface wlan0 inet static address 192.168.2.31 netmask 255.255.255.0 wireless-channel 1 wireless-essid IBSSNetwork wireless-mode ad-hoc From this configuration, I can ping each computer but I cannot create a Wi-Fi direct network. Now I change the /etc/network/interfaces document to be auto wlan0 iface wlan0 inet static address 192.168.2.30 netmask 255.255.255.0 wireless-channel 7 wireless-essid IBSSNetwork wireless-mode ad-hoc and auto wlan0 iface wlan0 inet static address 192.168.2.31 netmask 255.255.255.0 wireless-channel 7 wireless-essid IBSSNetwork wireless-mode ad-hoc and after rebooting the computer, I can no longer communicate via ad-hoc between computers, but I can create a Wi-Fi direct network on my first computer. *end edit* And I'm able to get the Wi-Fi direct and Wi-Fi ad hoc to work independently but not simultaneously. Here's my problem: When I follow the guide and set the wireless channel to 1 and I use wpa_cli - the p2p-dev-wlan1 interface does not show up. When I change the wireless channel in the /etc/network/interfaces document, I can't ping the other computer on the Ad-hoc network. **So my question is, what is blocking me from using both interfaces simultaneously and why can't I set the Wi-Fi ad hoc network to another channel and still communicate with other devices?** Thanks!

I'm trying to get WiFi Direct running on my Arch linux machine to connect to an Android Smartphone. But when trying to find WiFi Direct peers, the message FAIL is returned with no other error message. How can I find out what's the problem? Following the [P2P README of wpa_supplicant](http://svn.dd-wrt.com/browser/src/router/hostapd-wps/wpa_supplicant/README-P2P?rev=16495) and [this blog post](https://thangamaniarun.wordpress.com/2013/03/03/how-to-use-wi-fi-direct-on-androidubuntu-part1/) , I compiled wpa_supplicant from git (repo git://w1.fi/srv/git/hostap.git, commit 2d18ab40826ecaec26bfd82d42dcb08f2715e362, master as of May 31th, 2017, build config see below). I started wpa_supplicant and used wpa_cli to issue the command p2p_find, however, this returns the message FAIL, with no other information neither in the wpa_cli output, nor in the wpa_supplicant output or the syslog (journalctl -f) How can I get wpa_supplicant to show a helpful error message? --------------------------------- Building and running wpa_supplicant ======================= git clone git://w1.fi/srv/git/hostap.git cd hostapd/wpa_supplicant cp defconf .config # Edit .config to uncomment: # * CONFIG_AP=y # * CONFIG_P2P=y # * CONFIG_wps=y # * (CONFIG_DRIVER_NL80211=y) enabled by default # * (CONFIG_CTRL_IFACE=y) enabled by default # # * CONFIG_LIBNL32=y (Arch Linux uses libnl 3.2) # make # Run wpa_supplicant. See below for config files sudo ./wpa_supplicant -c/etc/wpa_supplicant/p2p.conf -iwlan0 -dd -Dnl80211 wpa_supplicant Peer-To-Peer configuration ========================================== /etc/wpa_supplicant/p2p.conf: ctrl_interface=DIR=/var/run/wpa_supplicant update_config=1 device_name=My Arch Machine device_type=1-0050F204-1 driver_param=use_p2p_group_interface=1 Log files ========== wpa_cli session (user input after >) > wpa_cli wpa_cli v2.6 [...] Selected interface 'wlan0' Interactive mode > p2p_find FAIL wpa_supplicant standard output. The point where p2p_find was invoked from within wpa_cli is marked with # /etc/wpa_supplicant/p2p.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant/p2p.conf' -> '/etc/wpa_supplicant/p2p.conf' Reading configuration file '/etc/wpa_supplicant/p2p.conf' ctrl_interface='DIR=/var/run/wpa_supplicant' update_config=1 device_name='My Arch Machine' driver_param='use_p2p_group_interface=1' nl80211: Supported cipher 00-0f-ac:1 nl80211: Supported cipher 00-0f-ac:5 nl80211: Supported cipher 00-0f-ac:2 nl80211: Supported cipher 00-0f-ac:4 nl80211: Supported cipher 00-0f-ac:10 nl80211: Supported cipher 00-0f-ac:8 nl80211: Supported cipher 00-0f-ac:9 nl80211: Using driver-based off-channel TX nl80211: Driver-advertised extended capabilities (default) - hexdump(len=8): 00 00 00 00 00 00 00 40 nl80211: Driver-advertised extended capabilities mask (default) - hexdump(len=8): 00 00 00 00 00 00 00 40 nl80211: interface wlan0 in phy phy0 nl80211: Set mode ifindex 3 iftype 2 (STATION) nl80211: Subscribe to mgmt frames with non-AP handle 0xa6c350 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=040a nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=040b nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=040c nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=040d nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=090a nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=090b nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=090c nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=090d nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=0409506f9a09 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=7f506f9a09 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=06 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=0a07 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=0a11 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=1101 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=1102 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=0505 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xa6c350 match=0500 rfkill: initial event: idx=1 type=1 op=0 soft=0 hard=0 netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT) nl80211: driver param='use_p2p_group_interface=1' nl80211: Use separate P2P group interface Add interface wlan0 to a new radio phy0 nl80211: Regulatory information - country=00 nl80211: 2402-2472 @ 40 MHz 20 mBm nl80211: 2457-2482 @ 20 MHz 20 mBm (no IR) nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR) nl80211: 5170-5250 @ 80 MHz 20 mBm (no IR) nl80211: 5250-5330 @ 80 MHz 20 mBm (DFS) (no IR) nl80211: 5490-5730 @ 160 MHz 20 mBm (DFS) (no IR) nl80211: 5735-5835 @ 80 MHz 20 mBm (no IR) nl80211: 57240-63720 @ 2160 MHz 0 mBm nl80211: Added 802.11b mode based on 802.11g information wlan0: Own MAC address: 00:26:82:b0:3a:0a wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0 wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0 wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0 wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0 wlan0: RSN: flushing PMKID list in the driver nl80211: Flush PMKIDs wlan0: State: DISCONNECTED -> INACTIVE wlan0: WPS: UUID based on MAC address: cfafece3-a583-5946-bcde-95bd75350713 ENGINE: Loading dynamic engine ENGINE: Loading dynamic engine EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: Supplicant port status: Unauthorized nl80211: Skip set_supp_port(unauthorized) while not associated EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED wlan0: Added interface wlan0 wlan0: State: INACTIVE -> DISCONNECTED nl80211: Set wlan0 operstate 0->0 (DORMANT) netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT) random: Got 20/20 bytes from /dev/random RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1003 ([UP]) RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1003 ([UP]) EAPOL: disable timer tick CTRL_IFACE monitor attached /tmp/wpa_ctrl_14358-125\x00 CTRL-DEBUG: ctrl_sock-sendto: sock=12 sndbuf=212992 outq=0 send_len=3 # wlan0: Control interface command 'P2P_FIND' CTRL-DEBUG: ctrl_sock-sendto: sock=12 sndbuf=212992 outq=0 send_len=5 ^Cwlan0: Removing interface wlan0 wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 state=DISCONNECTED wlan0: State: DISCONNECTED -> DISCONNECTED nl80211: Set wlan0 operstate 0->0 (DORMANT) netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT) EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 wlan0: WPA: Clear old PMK and PTK wlan0: Cancelling scan request wlan0: Cancelling authentication timeout Off-channel: Clear pending Action frame TX (pending_action_tx=(nil) Remove interface wlan0 from radio phy0 Remove radio phy0 nl80211: deinit ifname=wlan0 disabled_11b_rates=0 nl80211: Remove monitor interface: refcount=0 netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP) nl80211: Set mode ifindex 3 iftype 2 (STATION) nl80211: Unsubscribe mgmt frames handle 0x88888888882e4bd9 (mode change) wlan0: CTRL-EVENT-TERMINATING CTRL-DEBUG: ctrl_sock-sendmsg: sock=12 sndbuf=212992 outq=0 send_len=23 CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_14358-125\x00 CTRL_IFACE wait for attached monitors to receive messages journalctl -f: Mai 31 09:40:17 arch sudo: user : TTY=pts/3 ; PWD=/home/user/Computer/Network/wifi-direct/hostap/wpa_supplicant ; USER=root ; COMMAND=./wpa_supplicant -c/etc/wpa_supplicant/p2p.conf -iwlan0 -dd -Dnl80211 Mai 31 09:40:17 arch sudo: pam_unix(sudo:session): session opened for user root by user(uid=0) Mai 31 09:40:17 arch kernel: brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) Mai 31 09:40:17 arch kernel: brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) Mai 31 09:40:17 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready # Mai 31 09:40:35 arch sudo: pam_unix(sudo:session): session closed for user root System information ================== uname -a ## Linux arch 4.11.2-1-ARCH #1 SMP PREEMPT Mon May 22 06:53:49 CEST 2017 x86_64 GNU/Linux lspci -k ## 05:00.0 Network controller: Broadcom Limited BCM43225 802.11b/g/n (rev 01) ## Subsystem: Broadcom Limited Device 04da ## Kernel driver in use: bcma-pci-bridge ## Kernel modules: bcma WLAN card capabilities ====================== **iw list** output: capabilities P2P-client, P2P-GO and P2P-device are there. 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. 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) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP * AP/VLAN * monitor Band 1: Capabilities: 0x7c HT20 SM Power Save disabled RX Greenfield RX HT20 SGI RX HT40 SGI No RX STBC Max AMSDU length: 3839 bytes No DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 8 usec (0x06) HT Max RX data rate: 500 Mbps HT TX/RX MCS rate indexes supported: 0-15 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 (19.0 dBm) * 2417 MHz (19.0 dBm) * 2422 MHz (19.0 dBm) * 2427 MHz (19.0 dBm) * 2432 MHz (19.0 dBm) * 2437 MHz (19.0 dBm) * 2442 MHz (19.0 dBm) * 2447 MHz (19.0 dBm) * 2452 MHz (19.0 dBm) * 2457 MHz (19.0 dBm) * 2462 MHz (19.0 dBm) * 2467 MHz (19.0 dBm) * 2472 MHz (19.0 dBm) * 2484 MHz (disabled) 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 * set_qos_map * 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 interface combinations are not supported 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 Device supports configuring vdev MAC-addr on create.

I have network-manager and nm-applet installed on arch linux. I'm using Gnome desktop. When I try to set-up hotspot using GUI I get an error stating "Activation of network failed". This is what I have in my /etc/NetworkManager/system-connection/Hotspot [connection] id=Hotspot uuid=00b96273-0d3d-4430-bacc-280f2cd0c19d type=wifi autoconnect=false permissions= secondaries= [wifi] hidden=false mac-address=AC:B5:7A:85:D2:DA mac-address-blacklist= mac-address-randomization=0 mode=ap seen-bssids= ssid=name [wifi-security] group=ccmp; key-mgmt=wpa-psk pairwise=ccmp; proto=rsn; psk=password [ipv4] dns-search= method=shared [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto I tried connecting using nmcli con up id Hotspot but it gave me the same error. I made sure the extra services like network.service or net-auto-wireless.service are disabled (They were already disabled). Can anyone help me setting up a hotspot with network-manager. Thanks in advance.

nmcli proposes a connection type olpc-mesh. **How does it differ from ad hoc networking and in which situation is this connection type used?** From man nmcli: type olpc-mesh ssid SSID [channel 1-13] [dhcp-anycast MAC] ssid SSID. channel channel to use for the network. dhcp-anycast anycast DHCP MAC address used when requesting an IP address via DHCP.

Why are the channels supported for an Ad hoc network ( **12 channels** ) different from those that my interface support ( **35 channels)** ------------------------- * To find the 35 channels, I ran iwlist wlan0 channel * to find those accepted for my ad hoc network cat channel_list | while read i do echo -n "$i: " iwconfig wlan0 channel $i done I have the following error for channels greated than 12: Error for wireless request "Set Frequency" (8B04) : SET failed on device wlp3s0 ; Invalid argument.

I have 3 devices. On one tetwork one device can see another, yet they both can not see the third one. They are in same wi-fi ad-hoc network. 2 of them see each other and one does not see no one. Devices are in cl.ose proximity (10cm). How to figure out why? For one That does not play with others: ==== Here is ifconfig: root@edison:~# ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr 78:4b:87:a9:87:53 inet addr:192.168.2.50 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::7a4b:87ff:fea9:8753/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1528 Metric:1 RX packets:1342297 errors:0 dropped:852312 overruns:0 frame:0 TX packets:158162 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:80024954 (76.3 MiB) TX bytes:10973582 (10.4 MiB) Here is iwconfig: root@edison:~# iwconfig wlan0 wlan0 IEEE 802.11abgn ESSID:"pi-ad-hoc" Mode:Ad-Hoc Frequency:2.427 GHz Cell: 3A:41:3D:F5:20:A2 Tx-Power=31 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Here is iwlist scan (strangly it shows **more then one network** with same name): Cell 01 - Address: 3A:41:3D:F5:20:A2 Channel:4 Frequency:2.427 GHz (Channel 4) Quality=70/70 Signal level=-4 dBm Encryption key:off ESSID:"pi-ad-hoc" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Ad-Hoc Extra:tsf=0000002153a8a359 Extra: Last beacon: 90ms ago IE: Unknown: 000970692D61642D686F63 IE: Unknown: 010882848B962430486C IE: Unknown: 030104 ... Cell 06 - Address: 2E:5D:62:E8:17:46 Channel:4 Frequency:2.427 GHz (Channel 4) Quality=70/70 Signal level=0 dBm Encryption key:off ESSID:"pi-ad-hoc" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Ad-Hoc Extra:tsf=00000021521e98ce Extra: Last beacon: 25920ms ago IE: Unknown: 000970692D61642D686F63 IE: Unknown: 010882848B962430486C IE: Unknown: 030104 ... Cell 08 - Address: 0A:27:49:3D:49:E9 Channel:4 Frequency:2.427 GHz (Channel 4) Quality=70/70 Signal level=0 dBm Encryption key:off ESSID:"pi-ad-hoc" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Ad-Hoc Extra:tsf=0000002153313756 Extra: Last beacon: 7920ms ago IE: Unknown: 000970692D61642D686F63 IE: Unknown: 010882848B962430486C IE: Unknown: 030104 ... Cell 09 - Address: E2:32:E6:6A:CC:A9 Channel:4 Frequency:2.427 GHz (Channel 4) Quality=70/70 Signal level=0 dBm Encryption key:off ESSID:"pi-ad-hoc" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Ad-Hoc Extra:tsf=0000002153a96297 Extra: Last beacon: 40ms ago IE: Unknown: 000970692D61642D686F63 Here is ping: root@edison:~# ping 192.168.2.2 PING 192.168.2.2 (192.168.2.2): 56 data bytes ^C --- 192.168.2.2 ping statistics --- 8 packets transmitted, 0 packets received, 100% packet loss root@edison:~# ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1): 56 data bytes ^C --- 192.168.2.1 ping statistics --- 7 packets transmitted, 0 packets received, 100% packet loss root@edison:~# And here for the one of that do work: ==== ping: pi@pi3-2:~ $ ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=8.13 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=6.99 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=7.80 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=7.39 ms ^C --- 192.168.2.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 6.998/7.584/8.138/0.441 ms pi@pi3-2:~ $ ping 192.168.2.50 PING 192.168.2.50 (192.168.2.50) 56(84) bytes of data. ^C --- 192.168.2.50 ping statistics --- 9 packets transmitted, 0 received, 100% packet loss, time 7999ms ifconfig: pi@pi3-2:~ $ ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr b8:27:eb:67:07:fc inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::ac7f:b393:aac1:78bf/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1528 Metric:1 RX packets:1287637 errors:0 dropped:158601 overruns:0 frame:0 TX packets:487835 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:91775299 (87.5 MiB) TX bytes:46478896 (44.3 MiB) iwconfig pi@pi3-2:~ $ iwconfig wlan0 IEEE 802.11bgn ESSID:"pi-ad-hoc" Mode:Ad-Hoc Frequency:2.427 GHz Cell: 3A:41:3D:F5:20:A2 Tx-Power=31 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on iwlist wlan0 scan pi@pi3-2:~ $ iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 3A:41:3D:F5:20:A2 Channel:4 Frequency:2.427 GHz (Channel 4) Quality=70/70 Signal level=-35 dBm Encryption key:off ESSID:"pi-ad-hoc" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Ad-Hoc Extra:tsf=0000000000000000 Extra: Last beacon: 154751220ms ago IE: Unknown: 000970692D61642D686F63 IE: Unknown: 010882848B960C121824 IE: Unknown: 030104 IE: Unknown: 06020000 IE: Unknown: 32043048606C IE: Unknown: DD070050F202000100 IE: Unknown: 010882848B962430486C IE: Unknown: 2A0100 IE: Unknown: 32040C121860 IE: Unknown: 2D1A21001FFF00000000000000000000000000000000000000000000 IE: Unknown: 3D1604001300000000000000000000000000000000000000 IE: Unknown: DD09001018020010000000

In a wireless Ad-Hoc network, I have two computers which communicates in UDP together from 192.168.1.3 to 192.168.1.5 I have a third computer (192.168.1.6) which wants to listen to the packets which are not addressed to it. I can see the packets with tcpdump (which sets the wireless card in promiscuous mode). To redirect the packets, I am using : iptables -t nat -I PREROUTING -s 192.168.1.3 -j DNAT --to-destination 192.168.1.5 Is it the only rule I need to use? Why isn't it working? Did I miss other requirements?

I have 3 computers: 192.168.2.1, 192.168.2.2, 192.168.2.4 connected into an wireless ad-hoc network. I want all the traffic from 192.168.2.1 to go through 192.168.2.2 when it talks to 192.168.2.3. Basically 192.168.2.1 192.168.2.2 192.168.2.3 How do I alter the routing tables? I tried: pi@192.168.2.1: sudo ip route add 192.168.2.3 via 192.168.2.2 dev wlan0 pi@192.168.2.3: sudo ip route add 192.168.2.1 via 192.168.2.2 dev wlan0 I enabled forwading on 192.168.2.2 and it works. But when I do traceroute from 192.168.2.1, it looks like it goes directly to 192.168.2.3. Now, I added few more nodes (see the route table of 192.168.2.1 below) and I still get one hop when I do traceroute. But if I log into 192.192.2.2 and I traceroute 192.168.2.5, it gives me the correct number of hops. **ROUTE TABLE OF 192.168.2.1** Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 202 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 303 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 192.168.2.3 192.168.2.2 255.255.255.255 UGH 0 0 0 wlan0 192.168.2.4 192.168.2.2 255.255.255.255 UGH 0 0 0 wlan0 192.168.2.5 192.168.2.2 255.255.255.255 UGH 0 0 0 wlan0 **ROUTE TABLE OF 192.168.2.2** Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 0.0.0.0 255.255.0.0 U 303 0 0 wlan0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 192.168.2.4 192.168.2.3 255.255.255.255 UGH 0 0 0 wlan0 192.168.2.5 192.168.2.3 255.255.255.255 UGH 0 0 0 wlan0 Is it possible that the nodes do some caching? **EDIT;** I have 10 nodes in total now, and this is the output from my traceroute traceroute -4 192.168.2.10 traceroute to 192.168.2.10 (192.168.2.10), 30 hops max, 60 byte packets 1 192.168.2.2 (192.168.2.2) 10.140 ms 10.324 ms 10.398 ms 2 192.168.2.3 (192.168.2.3) 17.292 ms 17.483 ms 17.564 ms 3 192.168.2.4 (192.168.2.4) 25.646 ms 25.708 ms 26.110 ms 4 192.168.2.5 (192.168.2.5) 34.156 ms 34.416 ms 34.501 ms 5 192.168.2.6 (192.168.2.6) 44.131 ms 44.479 ms 44.560 ms 6 192.168.2.7 (192.168.2.7) 51.382 ms 43.074 ms 46.144 ms 7 192.168.2.8 (192.168.2.8) 46.129 ms 43.374 ms 53.956 ms 8 192.168.2.9 (192.168.2.9) 58.156 ms 83.625 ms 83.642 ms 9 192.168.2.10 (192.168.2.10) 83.565 ms 84.008 ms 89.355 ms