Arch Linux

diszkord

Member

Registered: 2014-04-17

Posts: 7

Difficulties while creating ad-hoc access point

Hello there!

Lately I've started using arch with xfce because of its speed and customization possiblilities. Everything would be great if not the fact that I'm experiencing a weird error while creating an ad-hoc access point through network-manager/hostapd/create_ap. My setup is:

Network card: Qualcomm Atheros AR9285
Kernel Version: 3.14.1
Kernel Driver in use: ath9k

enp2s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether dc:0e:a1:e2:9f:4b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 70  bytes 5236 (5.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 70  bytes 5236 (5.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.224.1.216  netmask 255.255.255.255  destination 10.64.64.64
        ppp  txqueuelen 3  (Point-to-Point Protocol)
        RX packets 59690  bytes 47382430 (45.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 53902  bytes 8325888 (7.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 44:6d:57:67:61:8c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

dmesg

[ 3778.791990] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 4010.957971] wlp3s0: Trigger new scan to find an IBSS to join
[ 4015.163857] wlp3s0: Trigger new scan to find an IBSS to join
[ 4020.152642] wlp3s0: Trigger new scan to find an IBSS to join
[ 4020.836610] wlp3s0: Creating new IBSS network, BSSID e6:6c:af:2d:ab:94
[ 4020.836753] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 4022.040681] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 4022.112391] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 4022.692279] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready

This error shows up when I try connect with iwconfig

SET failed on device wlp3s0 ; Operation not supported.

I've been digging unsuccessfully through the internet for many hours and I didn't any find solutions that would fix that problem. My only suspicion is that the nl80211 driver is possibly not loading up properly (I can't switch card to the master mode.). If someone has any idea how to fix that please share

Rexilion

Member

Registered: 2013-12-23

Posts: 784

Re: Difficulties while creating ad-hoc access point

Did it ever work with another distro? What kernel version did it use?

---

fs/super.c : "Self-destruct in 5 seconds.  Have a nice day...\n",

diszkord

Member

Registered: 2014-04-17

Posts: 7

Re: Difficulties while creating ad-hoc access point

Other distro's(ubuntu, debian, fedora) doesen't seem to have a problem when using this version of kernel(3.14.1) only arch pops up this error.

Rexilion

Member

Registered: 2013-12-23

Posts: 784

Re: Difficulties while creating ad-hoc access point

Differences in loaded firmware maybe?

---

fs/super.c : "Self-destruct in 5 seconds.  Have a nice day...\n",

diszkord

Member

Registered: 2014-04-17

Posts: 7

Re: Difficulties while creating ad-hoc access point

How can I check if there's any conflict between them?

[discord@hell ~]$ dmesg | grep firmware
[discord@hell ~]$ 

Rexilion

Member

Registered: 2013-12-23

Posts: 784

Re: Difficulties while creating ad-hoc access point

I was more specifically referring to the version of firmware installed (if external firmware is used by the device).

---

fs/super.c : "Self-destruct in 5 seconds.  Have a nice day...\n",

diszkord

Member

Registered: 2014-04-17

Posts: 7

Re: Difficulties while creating ad-hoc access point

usually i do not have to use an external firmware for this card

erm..
iw list

	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * WDS
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
	Band 1:

EDIT:
I'm an idiot, I forgot about dnsmasq..Solved!

Last edited by diszkord (2014-04-18 13:41:42)