#[End...OS] Can't get AP sharing on same wifi interface

75 messages · Page 1 of 1 (latest)

jovial wasp
#

Hello people, I'm struggling with the above. I can't get my Intel AX201 (does support AP modes) to share it's WIFI connection with my own hotspot AP. I've used iw to create an interface, made it go up using ifconfig, and somehow tried mashing this mess together with my NetworkManager to make it turn. Unfortunately, the nm reports that every interface but the one it selects is "device not ready". Due to this I reverted my changes and tried using nm to generate a hotspot (something I found out I can do only after making an interface), and that sort of works, I can't connect to my AP using any of my devices, and the AP seems to replace the WIFI connection I want to share.

#

Sorry for the edit! Hopefully I can find some help here :)

delicate stirrup
#

Most network interfaces can’t act as both a client and an AP at the same time.

#

It’s simply not possible on your hardware as far as I’m aware

#

... solved

carmine heathBOT
#

#9742 📣 If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.

  • You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
  • You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".

Your title should be like so: https://cdn.discordapp.com/attachments/503224329191030787/1039841700417384498/image.png
Thank you

jovial wasp
#

That’s pretty odd as far as standard goes

#

Unfortunate I can’t get a client and AP running simultaneously though

cursive quarry
#

you can see if your wifi adapter supports being an AP and client at the same time with
$ iw list | grep -A3 'valid interface combinations'
for example, mine does:

        valid interface combinations:
                 * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
                   total <= 3, #channels <= 2
jovial wasp
#

Hmmm

#

P2P is not the same thing though right

cursive quarry
#

no it's different

cursive quarry
#

yours is exactly the same?

jovial wasp
#

Yeah

#

I’ve been trying this for hours now lol

cursive quarry
#

then it can be an AP and a client (managed) at the same time

jovial wasp
#

Managed and AP?

#

Are you sure you’re reading that list right? It looks like it can only be managed and then nothing else

cursive quarry
#

total number of managed not more than one, and total number of AP, ... not more than one, total number of P2P not more than one
total number of active modes at one time not more than 3, across no more than 2 channels

jovial wasp
#

Hmmm

#

Okay this is very promising but network manager has refused to follow this completely

#

It doesn’t let me use two interfaces unless its en0p with wlan0

cursive quarry
#

i'm not sure exactly what the problem is, but i have a script that i've used for hosting an AP before, if you want it

jovial wasp
#

Yes

#

Please

#

🙏🙏🙏

cursive quarry
#

edit the network name and password in hostapd_temp.conf

#

you might have to exit other parts like the name of your wifi interface if it's not wlan0

jovial wasp
#
dnsmasq: no process found
hostapd: no process found
Current MAC:   8a:cf:c5:e3:83:85 (unknown)
Permanent MAC: 18:26:49:f3:9f:4b (unknown)
New MAC:       88:cf:c5:0e:fc:a1 (unknown)
test: interface state UNINITIALIZED->COUNTRY_UPDATE
test: interface state COUNTRY_UPDATE->HT_SCAN
20/40 MHz operation not permitted on channel pri=1 sec=5 based on overlapping BSSes
Fallback to 20 MHz
test: interface state HT_SCAN->ENABLED
test: AP-ENABLED
test: INTERFACE-DISABLED```
#

This is the result, also no AP! I have a feeling this didn't work

#
                 * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
                   total <= 3, #channels <= 2``` Just to confirm, this is a snippet from my 'iw list'
#
Error: Failed to add/activate new connection: A 'wireless' setting is required if no AP path was given.```
#

I added -dd as a parameter to hostapd and it pushed through to broadcasting the ssid but I failed to connect

#

It's just a lot of nl180211

#

When it fails it looks like this: ... test: AP-ENABLED test: Setup of interface done. RTM_NEWLINK: ifi_index=8 ifname=test operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) nl80211: Event message available nl80211: Drv Event 15 (NL80211_CMD_START_AP) received for test test: nl80211: Ignored unknown event (cmd=15) nl80211: Event message available nl80211: Drv Event 60 (NL80211_CMD_FRAME_TX_STATUS) received for test nl80211: MLME event 60 (NL80211_CMD_FRAME_TX_STATUS) on test(24:3a:12:3c:30:db) A1=ff:ff:ff:ff:ff:ff A2=24:3a:12:3c:30:db nl80211: MLME event frame - hexdump(len=26): c0 00 00 00 ff ff ff ff ff ff 24 3a 12 3c 30 db 24 3a 12 3c 30 db 00 00 02 00 nl80211: Frame TX status event A1=ff:ff:ff:ff:ff:ff stype=12 cookie=0x36 ack=1 test: Event TX_STATUS (16) received mgmt::deauth cb RTM_NEWLINK: ifi_index=8 ifname=test operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1003 ([UP]) RTM_NEWLINK: ifi_index=8 ifname=test operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 () nl80211: Interface down (test/test) test: Event INTERFACE_DISABLED (26) received test: INTERFACE-DISABLED RTM_NEWLINK: ifi_index=8 ifname=test wext ifi_family=0 ifi_flags=0x1002 () RTM_NEWLINK: ifi_index=8 ifname=test wext ifi_family=0 ifi_flags=0x1002 () nl80211: Event message available nl80211: Ignored event 33 (NL80211_CMD_TRIGGER_SCAN) for foreign interface (ifindex 3 wdev 0x0) RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) nl80211: Event message available nl80211: Ignored event 34 (NL80211_CMD_NEW_SCAN_RESULTS) for foreign interface (ifindex 3 wdev 0x0)

cursive quarry
jovial wasp
#

fair enough

#

should I just disable network manager

jovial wasp
#

Still can’t connect to the AP though

cursive quarry
#

you might need to configure networkmanager to not manage the test interface

#

not sure, i don't think i had to

cursive quarry
jovial wasp
#

Yes

#

Absolutely there

#

Im going to try a windows machine to isolate iOs

#

Its kinda quirky

#

Good news! The AP connects to the windows machine just fine

cursive quarry
#

you might need to mess with the dhcp-range setting in the dnsmaq config, and try manually setting the IP address on the clients you wanna connect with (maybe DHCP isn't working properly)

#

oh that's cool

jovial wasp
#

But iOS is straight up telling me to go fuck myself

cursive quarry
#

does the windows machine have internet through it?

jovial wasp
#

No unfortunately

#

Im pretty sure network manager uses iwd as the backend but doesnt save any data inside so no ap for the internet connect

#

Windows says im connected but pinging the host machine results in “transmit failed. General failure”

cursive quarry
#

could be DHCP issue

#

have you tried using only networkmanager? like for example the KDE networkmanager panel in systemsettings lets you create a WiFi AP to share internet

jovial wasp
#

Have not

#

I use i3

cursive quarry
#

this here's what it generates for me
File: /etc/NetworkManager/system-connections/share.nmconnection

[connection]
id=share
uuid=a28d54ef-c31c-4489-8644-a5b912f43bd4
type=wifi
autoconnect=false
permissions=user:cdison:;

[wifi]
band=bg
channel=2
mac-address=78:2B:46:C9:74:58
mode=ap
ssid=my_shared_connection

[ipv4]
method=shared

[ipv6]
addr-gen-mode=stable-privacy
method=auto

[proxy]
#

actually that's the wrong one

#

fixed

cursive quarry
#

plasma-nm

#

but that will only be useful on kde

jovial wasp
#

I think I’m just about ready to give up

#

I’ve tried using just iwd, resolvconf isnt working with it and ipados doesnt wanna connect and uhhh yeah im sick of this not working lol

#

AP works semi-reliably when its open

#

Thats about it

jovial wasp