You are not logged in.

Pages: 1 2

#26 2018-10-31 14:18:24

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,579
Website

Re: New Arch Install wireless issue - No Ethernet

Evuflow wrote:

Does this mean that NetworkManager service, wpa_supplicant and dhcpcd services can only be run independently of each other? and if so, may this be why my following attempts at connecting using wpa_supplicant have thus far been unsuccessful?

Yes, that's why I asked you to run wpa_supplicant while no other networking processes are running.  The output you were getting seemed indicative of another process alreay (attempting to) manage the wireless connection.

But it seems you're now at the next step - you have a connection, just not an IP.   In the short term you could try a static IP instead of using dhcpcd.  I have no experience to help with that, but there are wiki sections covering it.

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#27 2018-11-01 03:27:17

Evuflow
Member
Registered: 2018-10-30
Posts: 15

Re: New Arch Install wireless issue - No Ethernet

ewaller wrote:

Another sanity check, what are the output of ip addr    ?
Do you own the router?    Have you access to its logs?

I am surprised that dhcpcd seems to have not worked hmm
Are you sure the router is providing a DHCP server?  Are you sure it is on subnet 192.168.1.x/24?

Output from ip addr:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisk noqueue state UNKNOWN group default qlen 1000
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host
         valid_lft forever preferred_lft forever
2: enp0s25: <NO-CARRIER, BROADCAST, MULTICAST, UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
     link/ether f-:de:f1:c0:ab:c6 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisk mq state UP group default qlen 1000
     link.ether 10:0b:a9:6a:cb:a0 brd ff:ff:ff:ff:ff:ff:ff
     inet6 fe80::6f79:4efd:96ab:8ce5/64 scope link noprefixroute
            valid_lft forever preferred_lft forever

Concerning the router, I do not own it but the owners left it with default log in config so I can get the logs if I need to.
I am sure it's running DHCP, I have no issues connecting other devices, and they are assigned different IP every connection.
I've confirmed the network is a class C as the subnet is 255.255.255.0
This is what I'm getting from ipconfig /all on my windows machine connected to the same AP.

Wireless LAN adapter WiFi:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Marvell AVASTAR Wireless-AC Network Controller
   Physical Address. . . . . . . . . : 98-5F-D3-38-E3-85
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c580:78ff:7461:927a%19(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.37(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Thursday, 1 November 2018 11:24:03 AM
   Lease Expires . . . . . . . . . . : Friday, 2 November 2018 11:24:03 AM
   Default Gateway . . . . . . . . . : fe80::1%19
                                       192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 127426515
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-7C-5C-7B-98-5F-D3-38-E3-85
   DNS Servers . . . . . . . . . . . : fe80::1%19
                                       192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Perhaps it is using IPv6, I'm not sure. Not really familiar with it like I am with IPv4

Offline

#28 2018-11-02 03:16:19

Evuflow
Member
Registered: 2018-10-30
Posts: 15

Re: New Arch Install wireless issue - No Ethernet

So, I've just been setback to a similar situation at post #15, and I'm beginning to feel disheartened. I'm doing a lot of reading but nothing really sticks out as a cause or reason for why it's not working.

What happened was the router running the Viroj_3 AP went offline completely so I've resorted to connecting to Viroj_4 and Viroj_2. Problem is I get stuck at #15, and I can't replicate what worked last time.

I copied across a verbose wpa_supplicant command, perhaps there is something one of you will pick up on:

wpa_supplicant -B -i wlp3s0 -c /etc/wpa_supplicant/wpa_supplicant.conf -dd

wpa_supplicant v2.6
Successfully initialized wpa_supplicant
Initializing interface 'wlp3s0' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
ctrl_interface='/run/wpa_supplicant'
update_config=1
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=7):
     56 69 72 6f 6a 5f 33                              Viroj_3         
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Line: 9 - start of a new network block
ssid - hexdump_ascii(len=7):
     56 69 72 6f 6a 5f 32                              Viroj_2         
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Line: 14 - start of a new network block
ssid - hexdump_ascii(len=7):
     56 69 72 6f 6a 5f 34                              Viroj_4         
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='Viroj_3'
   id=1 ssid='Viroj_2'
   id=2 ssid='Viroj_4'
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 wlp3s0 in phy phy0
nl80211: Set mode ifindex 3 iftype 2 (STATION)
nl80211: Subscribe to mgmt frames with non-AP handle 0x55fa134fd850
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=0104
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 01 04
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=040a
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 04 0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=040b
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 04 0b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=040c
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 04 0c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=040d
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 04 0d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=090a
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 09 0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=090b
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 09 0b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=090c
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 09 0c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=090d
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 09 0d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=0409506f9a09
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=6): 04 09 50 6f 9a 09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=7f506f9a09
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=5): 7f 50 6f 9a 09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=0801
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 08 01
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=06
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=1): 06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=0a07
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 0a 07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=0a11
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 0a 11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=0a1a
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 0a 1a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=1101
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 11 01
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=1102
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 11 02
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=0505
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 05 05
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55fa134fd850 match=0500
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 05 00
nl80211: Failed to register Action frame processing - ignore for now
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)
Add interface wlp3s0 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
wlp3s0: Own MAC address: e6:4b:1b:a6:ae:6b
wpa_driver_nl80211_set_key: ifindex=3 (wlp3s0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp3s0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp3s0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp3s0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp3s0) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp3s0) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0
wlp3s0: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlp3s0: Setting scan request: 0.100000 sec
TDLS: TDLS operation not supported by driver
TDLS: Driver uses internal link setup
TDLS: Driver does not support TDLS channel switching
wlp3s0: WPS: UUID based on MAC address: b7753b88-ce6b-5b3b-8310-e49d03cbbb49
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
wlp3s0: Added interface wlp3s0
wlp3s0: State: DISCONNECTED -> DISCONNECTED
nl80211: Set wlp3s0 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
Daemonize..

Edit: Had the idea of trying to connect to my phone via tethering, as this was the network that was working when I installed Arch, while I have never managed to connect using Viroj yet. Unfortunately the same results as n post #15

Last edited by Evuflow (2018-11-02 03:20:46)

Offline

#29 2018-11-02 07:45:49

seth
Member
Registered: 2012-09-03
Posts: 51,945

Re: New Arch Install wireless issue - No Ethernet

Just a quick heads up, because I'm not sure this is clear: as long as you're attempting manual connections, you need to have networkmanager stopped (not running, check the service status)
I'm saying that because in your OP, the interface already was up (probably brought by NM) before you attempted to bring it (thus no change in the ip l output)

wpa_supplicant is then supposed to give you the carrier and afterwards you'll have to obtain some IP (eg. using dhcpcd or dhclient, try "dhclient -v" in case there might be issues w/ the dhcp implementation and dhcpcd's default approach)

Sanity check: this is not some sort of eduroam network (or anything w/ a multistep authentication)?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#30 2018-11-02 08:29:53

Evuflow
Member
Registered: 2018-10-30
Posts: 15

Re: New Arch Install wireless issue - No Ethernet

Thanks for the clarification Seth, I'm pretty familiar with the process now, since I've been doing a lot of reading on how this all works. But still can't find the reason why it's not working.

To your point about the Network, It is not an eduroam network and doesn't have multistep authentication, just average WPA2-PSK security. The model seems to be ZTE F668. A Chinese brand I think. I've just moved into an apartment in Thailand and this is just what I have at hand to work with essentially.

Offline

#31 2018-11-02 12:21:25

seth
Member
Registered: 2012-09-03
Posts: 51,945

Re: New Arch Install wireless issue - No Ethernet

You had a carrier in post #27, so if nothing else manipualates the interface, you must have succesfully run wpa_supplicant and should be able to obtain an IP one way or another.
Please try dhclient or dhcpcd (either in verbose and non-forking mode) and see what happens. Also check the router log (if eg. a MAC filter denies an IP for that MAC or similar)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1 2

Board footer

Powered by FluxBB