You are not logged in.
- Topics: Active | Unanswered
#1 2015-07-15 01:15:10
- C6H8C6
- Member
- Registered: 2014-12-22
- Posts: 7
[SOLVED] unable to get ip configuration via dhcpcd
Hello Community,
I am trying to reinstall arch on my desktop pc and i seem to be unable to get a ip configuration via dhcpcd.
I am using a TL-WN881ND PCI-Express WLan Card (Atheros AR9287 Chipset).
The access point is an "FritzBox! 3272" (A consumer class combination of router, switch, access point and whatnot).
The access point contains a working dhcp server (my arch powered notebook gets its configuration from this server).
Here is my /etc/wpa_supplicant/wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="Jedinet"
proto=RSN
group=CCMP
pairwise=CCMP
psk=<GENERATED_BY_WPA_PASSPHRASE>
}If i try to start wpa_supplicant, i get the following:
# wpa_supplicant -i wlp2s0 -B -c /etc/wpa_supplicant/wpa_supplicant.conf -dd
wpa_supplicant v2.3
Successfully initialized wpa_supplicant
Initializing interface 'wlp2s0' 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='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 1043 - start of a new network block
ssid - hexdump_ascii(len=7):
4a 65 64 69 6e 65 74 Jedinet
proto: 0x2
group: 0x10
pairwise: 0x10
PSK - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='Jedinet'
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: TDLS supported
nl80211: TDLS external setup
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: Supported cipher 00-0f-ac:6
nl80211: Supported cipher 00-0f-ac:13
nl80211: Supported cipher 00-0f-ac:11
nl80211: Supported cipher 00-0f-ac:12
nl80211: Using driver-based off-channel TX
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: interface wlp2s0 in phy phy0
nl80211: Set mode ifindex 3 iftype 2 (STATION)
nl80211: Subscribe to mgmt frames with non-AP handle 0x143f230
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=040a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=040b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=040c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=040d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=090a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=090b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=090c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=090d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=0409506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=7f506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=040e
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x143f230 match=0a11
netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)
nl80211: driver param='(null)'
Add interface wlp2s0 to a new radio phy0
nl80211: Regulatory information - country=CN (DFS-FCC)
nl80211: 2402-2482 @ 40 MHz 20 mBm
nl80211: 5170-5250 @ 80 MHz 23 mBm
nl80211: 5250-5330 @ 80 MHz 23 mBm (DFS)
nl80211: 5735-5835 @ 80 MHz 30 mBm
nl80211: 57240-59400 @ 2160 MHz 28 mBm
nl80211: 59400-63720 @ 2160 MHz 44 mBm
nl80211: 63720-65880 @ 2160 MHz 28 mBm
nl80211: Added 802.11b mode based on 802.11g information
wlp2s0: Own MAC address: <MAC_OF_WLP2S0>
wpa_driver_nl80211_set_key: ifindex=3 (wlp2s0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp2s0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp2s0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp2s0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp2s0) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlp2s0) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0
wlp2s0: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlp2s0: SettingTrying to use dhcpcd:
# dhcpcd wlp2s0 -debug
add_environ: no assignment: bug
add_environ: no assignment: bug
timed out
dhcpcd-6.9.0 starting
wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
wlp2s0: waiting for carrier
dhcpcd exited'add_environ: no assignment: bug'
Certainly dosn't look right, but i wasn't able to dig up anything useful on that.
Trying to use dhclient:
# dhclient -v wlp2s0
Internet Systems Consortium DHCP Client 4.3.2
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit [url]https://www.isc.org/software/dhcp/[/url]
Listening on LPF/wlp2s0/<MAC_OF_WLP2S0>
Sending on LPF/wlp2s0/<MAC_OF_WLP2S0>
Sending on Socket/fallback
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.'No DHCPOFFERS received.'
I do not understand why.
Other info:
# lsmod | grep ath9k
ath9k 135168 0
ath9k_common 28672 1 ath9k
ath9k_hw 442368 2 ath9k_common,ath9k
ath 28672 3 ath9k_common,ath9k,ath9k_hw
led_class 16384 1 ath9k
mac80211 655360 1 ath9k
cfg80211 483328 4 ath,ath9k_common,ath9k,mac80211# lspci -vv -s 02:00.0
02:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Qualcomm Atheros Device 30a4
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fe7f0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: 00000000 Data: 0000
Capabilities: [60] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number <SOME_NUMBER>
Capabilities: [170 v1] Power Budgeting <?>
Kernel driver in use: ath9k
Kernel modules: ath9kWLan worked with this exact piece of hardware in the past (about one year ago), sadly i don't have the config files i used back then.
Has anybody a clue of what might be going on?
-C6H8C6
Last edited by C6H8C6 (2015-07-20 00:16:02)
Yes, you are right: of course the second 'C' in my name should be a 'O' 
Offline
#2 2015-07-15 03:17:29
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 20,350
Re: [SOLVED] unable to get ip configuration via dhcpcd
Let's back up a couple steps.
If you would, what are the outputs of:
ip link
iw list
and of
sudo iw wlp2s0 scan
ewaller@turing ~ 1009 %ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether d0:bf:9c:97:e9:4c brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 34:e6:ad:17:fe:53 brd ff:ff:ff:ff:ff:ff
ewaller@turing ~ 1010 %iw list
Wiphy phy0
max # scan SSIDs: 20
max scan IEs length: 425 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Supported Ciphers:
* CCMP (00-0f-ac:4)
* 00-0f-ac:10
* TKIP (00-0f-ac:2)
* GCMP (00-0f-ac:8)
* 00-0f-ac:9
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* CMAC (00-0f-ac:6)
* 00-0f-ac:13
* 00-0f-ac:11
* 00-0f-ac:12
* WPI-SMS4 (00-14-72:1)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x1162
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-7
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] (22.0 dBm)
* 2417 MHz [2] (22.0 dBm)
* 2422 MHz [3] (22.0 dBm)
* 2427 MHz [4] (22.0 dBm)
* 2432 MHz [5] (22.0 dBm)
* 2437 MHz [6] (22.0 dBm)
* 2442 MHz [7] (22.0 dBm)
* 2447 MHz [8] (22.0 dBm)
* 2452 MHz [9] (22.0 dBm)
* 2457 MHz [10] (22.0 dBm)
* 2462 MHz [11] (22.0 dBm)
* 2467 MHz [12] (22.0 dBm) (no IR)
* 2472 MHz [13] (22.0 dBm) (no IR)
Band 2:
Capabilities: 0x1162
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-7
VHT Capabilities (0x33807120):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
short GI (80 MHz)
SU Beamformee
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 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:
* 5180 MHz [36] (22.0 dBm) (no IR)
* 5200 MHz [40] (22.0 dBm) (no IR)
* 5220 MHz [44] (22.0 dBm) (no IR)
* 5240 MHz [48] (22.0 dBm) (no IR)
* 5260 MHz [52] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5280 MHz [56] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5300 MHz [60] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5320 MHz [64] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5500 MHz [100] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5520 MHz [104] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5540 MHz [108] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5560 MHz [112] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5580 MHz [116] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5600 MHz [120] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5620 MHz [124] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5640 MHz [128] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5660 MHz [132] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5680 MHz [136] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5700 MHz [140] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5720 MHz [144] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 174095 sec)
DFS CAC time: 60000 ms
* 5745 MHz [149] (22.0 dBm) (no IR)
* 5765 MHz [153] (22.0 dBm) (no IR)
* 5785 MHz [157] (22.0 dBm) (no IR)
* 5805 MHz [161] (22.0 dBm) (no IR)
* 5825 MHz [165] (22.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
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* start_sched_scan
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* channel_switch
* Unknown command (104)
* Unknown command (105)
* connect
* disconnect
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
WoWLAN support:
* wake up on disconnect
* wake up on magic packet
* wake up on pattern match, up to 20 patterns of 16-128 bytes,
maximum packet offset 0 bytes
* can do GTK rekeying
* wake up on GTK rekey failure
* wake up on EAP identity request
* wake up on 4-way handshake
* wake up on rfkill release
* wake up on TCP connection
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
total <= 3, #channels <= 2
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 per-vif TX power setting
P2P GO supports CT window setting
P2P GO supports opportunistic powersave setting
Driver supports a userspace MPM
Device supports static SMPS
Device supports dynamic SMPS
ewaller@turing ~ 1011 %sudo iw wlo1 scan
BSS c4:3d:c7:5d:eb:8c(on wlo1) -- associated
TSF: 897838943376 usec (10d, 09:23:58)
freq: 5745
beacon interval: 100 TUs
capability: ESS Privacy (0x0011)
signal: -65.00 dBm
last seen: 0 ms ago
Information elements from Probe Response frame:
SSID: Woodlyn-hi
Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
* Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
HT capabilities:
Capabilities: 0x87e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 7935 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT RX MCS rate indexes supported: 0-15, 32
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 149
* secondary channel offset: above
* STA channel width: any
* RIFS: 1
* HT protection: 20 MHz
* non-GF present: 1
* OBSS non-GF present: 1
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
WMM: * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS c4:3d:c7:5d:eb:8f(on wlo1)
TSF: 3806669602757 usec (44d, 01:24:29)
freq: 2412
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -63.00 dBm
last seen: 0 ms ago
SSID: Woodlyn
Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0
DS Parameter set: channel 1
ERP: <no flags>
ERP D4.0: <no flags>
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
* Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
Extended supported rates: 6.0 9.0 12.0 48.0
WMM: * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS 78:54:2e:17:d3:ee(on wlo1)
TSF: 30570348094507 usec (353d, 19:45:48)
freq: 2412
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble (0x0031)
signal: -89.00 dBm
last seen: 0 ms ago
SSID: mcfab
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 1
Country: US Environment: Indoor/Outdoor
Channels [1 - 11] @ 30 dBm
ERP: Use_Protection
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x11ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT RX MCS rate indexes supported: 0-15
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 1
* secondary channel offset: above
* STA channel width: any
* RIFS: 0
* HT protection: non-HT mixed
* non-GF present: 0
* OBSS non-GF present: 1
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities: HT Information Exchange Supported
WMM: * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
RSN: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: CCMP TKIP
* Authentication suites: PSK
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 13c2db36-1dd2-11b2-bcdb-902ff1e85513
* Manufacturer: D-Link
* Model: D-Link Repeater
* Model Number: DAP-1320
* Serial Number: none
* Primary Device Type: 6-0050f204-1
* Device name: DAP-1320
* Config methods: PBC
* RF Bands: 0x1
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 38:2c:4a:e3:81:48(on wlo1)
TSF: 187080502806 usec (2d, 03:58:00)
freq: 2437
beacon interval: 100 TUs
capability: ESS Privacy ShortSlotTime RadioMeasure (0x1411)
signal: -88.00 dBm
last seen: 4366 ms ago
Information elements from Probe Response frame:
SSID: CINDY-PC_Network
Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0
DS Parameter set: channel 6
TIM: DTIM Count 0 DTIM Period 3 Bitmap Control 0x0 Bitmap[0] 0x0
ERP: <no flags>
ERP D4.0: <no flags>
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
Extended supported rates: 6.0 9.0 12.0 48.0
BSS Load:
* station count: 1
* channel utilisation: 71/255
* available admission capacity: 0 [*32us]
HT capabilities:
Capabilities: 0x19ad
RX LDPC
HT20
SM Power Save disabled
RX HT20 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT RX MCS rate indexes supported: 0-23
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 6
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: non-HT mixed
* non-GF present: 0
* OBSS non-GF present: 1
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities: HT Information Exchange Supported, Extended Channel Switching, BSS Transition, 6
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
WMM: * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS 00:0e:58:a8:46:69(on wlo1)
TSF: 30606795367143 usec (354d, 05:53:15)
freq: 2437
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble (0x0031)
signal: -79.00 dBm
last seen: 4356 ms ago
Information elements from Probe Response frame:
SSID: \x00
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x0 (+ 7 octets)
Extended supported rates: 24.0 36.0 48.0 54.0
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
BSS 10:0d:7f:9d:28:26(on wlo1)
TSF: 768807741582 usec (8d, 21:33:27)
freq: 2462
beacon interval: 200 TUs
capability: ESS Privacy ShortSlotTime (0x0411)
signal: -83.00 dBm
last seen: 0 ms ago
SSID: jands
Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0
DS Parameter set: channel 11
ERP: <no flags>
ERP D4.0: <no flags>
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
Extended supported rates: 6.0 9.0 12.0 48.0
HT capabilities:
Capabilities: 0x19fd
RX LDPC
HT20
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT RX MCS rate indexes supported: 0-23
HT TX MCS rate indexes are undefined
HT operation:
* primary channel: 11
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 1
* HT protection: nonmember
* non-GF present: 1
* OBSS non-GF present: 1
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities: HT Information Exchange Supported
WPS: * Version: 1.0
* Wi-Fi Protected Setup State: 2 (Configured)
* Response Type: 3 (AP)
* UUID: 58f29403-aba9-a4ad-4828-77ea0574e03f
* Manufacturer: NETGEAR, Inc.
* Model: WNDR4500
* Model Number: WNDR4500
* Serial Number: 4536
* Primary Device Type: 6-0050f204-1
* Device name: WNDR4500
* Config methods: Label
* RF Bands: 0x3
* Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
WMM: * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 6016 usec
* VO: CW 3-7, AIFSN 2, TXOP 3264 usec
ewaller@turing ~ 1012 %Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
#3 2015-07-15 10:12:30
- C6H8C6
- Member
- Registered: 2014-12-22
- Posts: 7
Re: [SOLVED] unable to get ip configuration via dhcpcd
Hello ewaller,
thank you for your resonse (:
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether <MAC_OF_ENP1S0> brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether <MAC_OF_WLP2S0> brd ff:ff:ff:ff:ff:ffi tried to activate the interface, but it seems like that dosn't work:
# ip link set wlp2s0 up
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether <MAC_OF_ENP1S0> brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether <MAC_OF_WLP2S0> brd ff:ff:ff:ff:ff:ffOutput of the two other commands:
# iw list
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Device supports T-DLS.
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
* CMAC (00-0f-ac:6)
* 00-0f-ac:13
* 00-0f-ac:11
* 00-0f-ac:12
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* WDS
* monitor
* mesh point
* P2P-client
* P2P-GO
Band 1:
Capabilities: 0x11ee
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
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 [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)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (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
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* tdls_mgmt
* tdls_oper
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* channel_switch
* Unknown command (104)
* connect
* disconnect
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:
* #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1,
total <= 2048, #channels <= 1, STA/AP BI must match
* #{ WDS } <= 2048,
total <= 2048, #channels <= 1, STA/AP BI must match
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
P2P GO supports CT window setting
Driver supports a userspace MPM
Device supports active monitor (which will ACK incoming frames)
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)# iw wlp2s0 scan
BSS 9c:c7:a6:75:e7:90(on wlp2s0)
TSF: 850913992184 usec (9d, 20:21:53)
freq: 2412
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -86.00 dBm
last seen: 740 ms ago
Information elements from Probe Response frame:
SSID: Jedinet
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 1
Country: DE Environment: Indoor/Outdoor
Channels [1 - 13] @ 20 dBm
ERP: <no flags>
Extended supported rates: 24.0 36.0 48.0 54.0
HT capabilities:
Capabilities: 0x11ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-23
HT operation:
* primary channel: 1
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 1
* HT protection: no
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Overlapping BSS scan params:
* passive dwell: 20 TUs
* active dwell: 10 TUs
* channel width trigger scan interval: 300 s
* scan passive total per channel: 200 TUs
* scan active total per channel: 20 TUs
* BSS width channel transition delay factor: 5
* OBSS Scan Activity Threshold: 0.25 %
Extended capabilities: HT Information Exchange Supported, 6
WMM: * Parameter version 1
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK
* Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)-C6H8C6
Yes, you are right: of course the second 'C' in my name should be a 'O'
Offline
#4 2015-07-15 14:11:50
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 20,350
Re: [SOLVED] unable to get ip configuration via dhcpcd
Hello Ascorbic acid,
No problem 
The good news is that it appears that the network is working and can see an access point (Jedinet).
After you run wpa_supplicant, but before you run dhcpcd, look at the output of ip link. We need to ensure that it is associated before we go any further.
Is there a reason you chose to use wpa_supplicant by itself and not in conjunction with netctl or NetworkManager? Are you certain that nothing else has been enabled that is trying to control your NIC? Post the output of systemctl --type service --no-pager and of ls -l /etc/systemd/system
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
#5 2015-07-15 15:24:42
- C6H8C6
- Member
- Registered: 2014-12-22
- Posts: 7
Re: [SOLVED] unable to get ip configuration via dhcpcd
Hello ewaller,
Here's the output of ip link after wpa_supplicant started, but before dhcpcd started:
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether <MAC_OF_ENP1S0> brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether <MAC_OF_WLP2S0> brd ff:ff:ff:ff:ff:ff# dhcpcd wlp2s0 -debug
add_environ: no assignment: bug
add_environ: no assignment: bug
timed out
dhcpcd-6.9.0 starting
wlp2s0: disabling kernel IPv6 RA support
wlp2s0: adding address fe80::2ff3:b2c6:75b:58cc
wlp2s0: pltime infinity, vltime infinity
wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
wlp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
wlp2s0: waiting for carrier
dhcpcd exitedIs there a reason you chose to use wpa_supplicant by itself and not in conjunction with netctl or NetworkManager?
The wpa_supplicant-only solution is only temporary: once the setup is complete i normally use wicd. However as wicd uses wpa_supplicant in the
background (afaik) i thought it couldn't hurt to have wpa_supplicant itself working (I am not absolutely sure that wpa_supplicant
isn't the problem as i have experienced it failing silently in the past).
Should i try installing wicd offline into the live-usb environment?
Are you certain that nothing else has been enabled that is trying to control your NIC?
Yes pretty much, as i am in the installation live-usb environment and the only commands i executed are the ones that i posted here.
The output of the two other commands:
# systemctl --type service --no-pager
UNIT LOAD ACTIVE SUB
dbus.service loaded active running D-Bus System Message Bus
● dhcpcd@enp1s0.service loaded failed failed dhcpcd on enp1s0
getty@tty1.service loaded active running Getty on tty1
haveged.service loaded active running Entropy Harvesting Daemon
kmod-static-nodes.service loaded active exited Create list of required static device nodes for the current kernel
ldconfig.service loaded active exited Rebuild Dynamic Linker Cache
lvm2-lvmetad.service loaded active running LVM2 metadata daemon
lvm2-pvscan@8:3.service loaded active exited LVM2 PV scan on device 8:3
pacman-init.service loaded active exited Initializes Pacman keyring
systemd-hwdb-update.service loaded active exited Rebuild Hardware Database
systemd-journal-catalog-update.service loaded active exited Rebuild Journal Catalog
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-rfkill@rfkill0.service loaded active exited Load/Save RF Kill Switch Status of rfkill0
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-sysusers.service loaded active exited Create System Users
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-done.service loaded active exited Update is Completed
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
user@0.service loaded active running User Manager for UID 0
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
29 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.# ls -l /etc/systemd/system
total 24
-rw-r--r-- 1 root root 203 Apr 24 17:19 choose-mirror.service
lrwxrwxrwx 1 root root 41 Jul 1 16:58 default.target -> /usr/lib/systemd/system/multi-user.target
-rw-r--r-- 1 root root 134 Apr 24 17:19 etc-pacman.d-gnupg.mount
drwxr-xr-x 2 root root 4096 Jul 1 16:56 getty.target.wants
drwxr-xr-x 2 root root 4096 Apr 24 20:36 getty@tty1.service.d
drwxr-xr-x 2 root root 4096 Jul 1 16:58 multi-user.target.wants
-rw-r--r-- 1 root root 325 Apr 24 17:19 pacman-init.service-C6H8C6
Yes, you are right: of course the second 'C' in my name should be a 'O'
Offline
#6 2015-07-15 15:48:35
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 20,350
Re: [SOLVED] unable to get ip configuration via dhcpcd
Is wifi-menu functional on your machine? If so, that is the going to be the path of least resistance.
If not, you should be able to use https://wiki.archlinux.org/index.php/Netctl. I find it to be be a much simpler way to control wpa_supplicant. If you plan to go on and install wicd, then don't enable your netctl protocol, just start it. FWIW, I used to use wicd, but it had fallen into disrepair for a while; has it made a comeback?
You could install wicd off-line, but it might be easier to go back to your install media, chroot into your Arch system, and install wicd while in the chroot environment.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
#7 2015-07-15 18:44:47
- C6H8C6
- Member
- Registered: 2014-12-22
- Posts: 7
Re: [SOLVED] unable to get ip configuration via dhcpcd
Hello ewaller,
Remark: I meanwhile rebooted the live-usb to make sure that our previous attempts don't mess anything up.
Is wifi-menu functional on your machine?
Well, that depends on your definition of functional (:
If i run
# wifi-menuThe computer scans for WLANs. It detects "Jedinet", but when i enter the passphrase and try to connect, the screen goes dark for about 15 to 20 seconds and then it says "CONNECTION FAILED" and asks me whether i want to save the generated profile regardless.
I also tried netctl with the following config [filename: "myprofile"]:
(This is one of the example profiles; the only things i changed are the SSID, the Interface and the passphrase)
Description='A simple WPA encrypted wireless connection'
Interface=wlp2s0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='Jedinet'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='<MY_WLAN_PASSPHRASE'
# Uncomment this if your ssid is hidden
#Hidden=yes
# Set a priority for automatic profile selection
#Priority=10Trying to start the profile:
# netctl start myprofile
Job for netctl@myprofile.service failed because the control process exited with error code. See "systemctl status netctl@myprofile.service" and "journalctl -xe" for details.# systemctl status netctl@myprofile.service
● netctl@myprofile.service - Networking for netctl profile myprofile
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2015-07-15 18:36:30 UTC; 1min 42s ago
Docs: man:netctl.profile(5)
Process: 3641 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 3641 (code=exited, status=1/FAILURE)
Jul 15 18:36:14 archiso systemd[1]: Starting Networking for netctl profile myprofile...
Jul 15 18:36:14 archiso network[3641]: Starting network profile 'myprofile'...
Jul 15 18:36:30 archiso network[3641]: WPA association/authentication failed for interface 'wlp2s0'
Jul 15 18:36:30 archiso network[3641]: Failed to bring the network up for profile 'myprofile'
Jul 15 18:36:30 archiso systemd[1]: netctl@myprofile.service: Main process exited, code=exited, status=1/FAILURE
Jul 15 18:36:30 archiso systemd[1]: Failed to start Networking for netctl profile myprofile.
Jul 15 18:36:30 archiso systemd[1]: netctl@myprofile.service: Unit entered failed state.
Jul 15 18:36:30 archiso systemd[1]: netctl@myprofile.service: Failed with result 'exit-code'.# journalctl -xe
-- Subject: Unit netctl@myprofile.service has begun start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
--
-- Unit netctl@myprofile.service has begun starting up.
Jul 15 18:36:14 archiso network[3641]: Starting network profile 'myprofile'...
Jul 15 18:36:14 archiso kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Jul 15 18:36:15 archiso kernel: wlp2s0: authenticate with <MAC_OF_ACCESS_POINT>:90
Jul 15 18:36:15 archiso kernel: wlp2s0: send auth to <MAC_OF_ACCESS_POINT>:90 (try 1/3)
Jul 15 18:36:15 archiso kernel: wlp2s0: <MAC_OF_ACCESS_POINT>:90 denied authentication (status 37)
Jul 15 18:36:15 archiso kernel: wlp2s0: authenticate with <MAC_OF_ACCESS_POINT>:90
Jul 15 18:36:16 archiso kernel: wlp2s0: send auth to <MAC_OF_ACCESS_POINT>:90 (try 1/3)
Jul 15 18:36:16 archiso kernel: wlp2s0: <MAC_OF_ACCESS_POINT>:90 denied authentication (status 37)
Jul 15 18:36:17 archiso kernel: wlp2s0: authenticate with <MAC_OF_ACCESS_POINT>:90
Jul 15 18:36:17 archiso kernel: wlp2s0: send auth to <MAC_OF_ACCESS_POINT>:90 (try 1/3)
Jul 15 18:36:17 archiso kernel: wlp2s0: <MAC_OF_ACCESS_POINT>:90 denied authentication (status 37)
Jul 15 18:36:19 archiso kernel: wlp2s0: authenticate with <MAC_OF_ACCESS_POINT>:90
Jul 15 18:36:19 archiso kernel: wlp2s0: send auth to <MAC_OF_ACCESS_POINT>:90 (try 1/3)
Jul 15 18:36:19 archiso kernel: wlp2s0: <MAC_OF_ACCESS_POINT>:90 denied authentication (status 37)
Jul 15 18:36:30 archiso network[3641]: WPA association/authentication failed for interface 'wlp2s0'
Jul 15 18:36:30 archiso network[3641]: Failed to bring the network up for profile 'myprofile'
Jul 15 18:36:30 archiso systemd[1]: netctl@myprofile.service: Main process exited, code=exited, status=1/FAILURE
Jul 15 18:36:30 archiso systemd[1]: Failed to start Networking for netctl profile myprofile.
-- Subject: Unit netctl@myprofile.service has failed
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
--
-- Unit netctl@myprofile.service has failed.
--
-- The result is failed.
Jul 15 18:36:30 archiso systemd[1]: netctl@myprofile.service: Unit entered failed state.
Jul 15 18:36:30 archiso systemd[1]: netctl@myprofile.service: Failed with result 'exit-code'.I notices something strange with the MAC Addresses in this last one:
The MAC Address of the access point is XX:XX:XX:XX:XX:8e (determined by using wireshark to sniff the traffic from my laptop)
But the output of journalctl -xe says XX:XX:XX:XX:XX:90 [all the X are identical]
What is this? The last three bytes of the MAC address are supposed to be a serial number assigned by the vendor. Because it is a serial number there cannot be any flags, right? Why then are there four bits flipped?
About wicd:
Well, i have used it for about a year now and sofar it hasn't made me any difficulties.
I use it to connect to my private LAN, private WLAN and to the WLAN at university -> it worked.
Can't tell more (source code quality, robustness, ...) though as i havn't played around with it much and havn't looked at the source.
EDIT:
You could install wicd off-line, but it might be easier to go back to your install media, chroot into your Arch system, and install wicd while in the chroot environment.
Do i understand this correctly: boot into the live-environment, setup the base system and then do a offline installation of wicd?
-C6H8C6
Last edited by C6H8C6 (2015-07-15 18:57:21)
Yes, you are right: of course the second 'C' in my name should be a 'O'
Offline
#8 2015-07-15 20:41:47
- Head_on_a_Stick
- Member
- From: The Wirral
- Registered: 2014-02-20
- Posts: 8,778
- Website
Re: [SOLVED] unable to get ip configuration via dhcpcd
Can we see:
ls -l /etc/systemd/system/multi-user.target.wantsJin, Jîyan, Azadî
Offline
#9 2015-07-15 20:51:23
- C6H8C6
- Member
- Registered: 2014-12-22
- Posts: 7
Re: [SOLVED] unable to get ip configuration via dhcpcd
Hello Head_on_a_Stick,
Here it is:
# ls -l /etc/systemd/system/multi-user.target.wants
total 0
lrwxrwxrwx 1 root root 41 Jul 1 16:58 choose-mirror.service -> /etc/systemd/system/choose-mirror.service
lrwxrwxrwx 1 root root 39 Jul 1 16:58 pacman-init.service -> /etc/systemd/system/pacman-init.service
lrwxrwxrwx 1 root root 40 Jul 1 16:56 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target-C6H8C6
Yes, you are right: of course the second 'C' in my name should be a 'O'
Offline
#10 2015-07-16 00:29:09
- Tarqi
- Member
- From: Ixtlan
- Registered: 2012-11-27
- Posts: 179
- Website
Re: [SOLVED] unable to get ip configuration via dhcpcd
nl80211: Regulatory information - country=CN (DFS-FCC)
Are you in China? If not, install and setup crda / wireless-regdb.
wlp2s0: waiting for carrier dhcpcd exited
So there is no carrier... what means, there is no "cable plugged", i.e. no Layer 1 connection.
signal: -86.00 dBm Country: DE Environment: Indoor/Outdoor Channels [1 - 13] @ 20 dBm
-86.00 dBm is enough to see the AP, but not to successfully establish a connection. And obviously you are not in China...
Jul 15 18:36:15 archiso kernel: wlp2s0: send auth to <MAC_OF_ACCESS_POINT>:90 (try 1/3) Jul 15 18:36:15 archiso kernel: wlp2s0: <MAC_OF_ACCESS_POINT>:90 denied authentication (status 37)
De-authentication initiated from the client side, as explained (for example) here. You might get the official 802.11 codes here.
But the output of journalctl -xe says XX:XX:XX:XX:XX:90 [all the X are identical]
BSS 9c:c7:a6:75:e7:90(on wlp2s0)
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether <MAC_OF_WLP2S0> brd ff:ff:ff:ff:ff:ff
I always hated all those nonsense "privacy" stuff by blanking out internal ips and/or mac-addresses. This is so useless, it doesn't add any privacy and makes it just more difficult to recognize a problem in a reasonable way. So I can't help you here, sorry.
WLan worked with this exact piece of hardware in the past (about one year ago), sadly i don't have the config files i used back then.
As stated above, I guess you had crda / wireless-regdb installed before. These will alter the transmit power and channel selection of the device and lets both ends play better together and might help. Maybe you need to move nearer to your AP.
Not to be rude: Don't just post your logs. Read them.
However, I might be wrong anyway. If so, please appreciate my apologize 
Edit1: Cosmetics (I like that )
Edit2: Added the IEEEE stuff (and that little rant, sorry for this)
Last edited by Tarqi (2015-07-16 01:09:07)
Knowing others is wisdom, knowing yourself is enlightenment. ~Lao Tse
Offline
#11 2015-07-16 15:51:33
- C6H8C6
- Member
- Registered: 2014-12-22
- Posts: 7
Re: [SOLVED] unable to get ip configuration via dhcpcd
Hello Tarqi,
Are you in China? If not, install and setup crda / wireless-regdb.
Both crda and wireless-regdb are included in the live environment. I changed the regulatory domain to DE and tried again, but it didn't solve the problem.
So there is no carrier... what means, there is no "cable plugged", i.e. no Layer 1 connection.
Yes, i know. The question is: Why is it unable to establish a layer 1 connection. As you have pointed out the signal is very weak, but my laptop is doing just fine under the same circumstances. Because of that i don't think this is the problem (correct me if i am wrong).
De-authentication initiated from the client side, as explained (for example) here. You might get the official 802.11 codes here.
OK, thanks for the link. I'll do some reading about that in the evening.
I always hated all those nonsense "privacy" stuff by blanking out internal ips and/or mac-addresses. This is so useless, it doesn't add any privacy and makes it just more difficult to recognize a problem in a reasonable way. So I can't help you here, sorry.
I have to disagree with you on that one.
Not to hide the MAC-Address makes users trackable across sites and pseudonyms. This is a compromise of security and can e.g. in the case of opposition members or political activists have serious consequences for them.
About the "issue" with the flipping bits: This was just ment to be an interesting side note. I don't understand why those bits flipped and so i asked, just in case one of you happened to know something about this. I don't think it is responsible for my problem.
Not to be rude: Don't just post your logs. Read them.
Sorry if it appeared like that. I will try harder next time.
EDIT:
I just removed and reinstalled the nic to make sure the problem isn't with the physical connection with the motherboard. The error remains.
I attached a external antenna to the nic. Now i have signal strenght of -75.00dBm to -80.00dBm; still not great but already much better than on my notebook. The error remains.
-> I think the weak signal can be ruled out as cause of the problem
EDIT (2):
I sniffed the traffic with wireshark.
The computer in question sends 56 probe requests to the broadcast address and one frame of type authentication directly to the address of the access point (all within one connection-attempt with dhcpcd). It dosn't receive any answers though.
Both, my notebook and the desktop pc run wpa_supplicant version 2.3 and dhcpcd version 6.9.0 so that shouldn't be the problem.
I think it might be some type of incompatibility between the nic/its driver and the access point, but i am not sure how to confirm that or prove it wrong.
EDIT (3):
I solved it. While checking the access point i discovered a new setting that was apparently introduced in one of the recent firmware updates: The access point did MAC Address whitelisting.
I am not certain whether this is the default behaviour or someone enabled it on purpose (i am not the only one with the password for the access point) but it works now.
Anyway: Thanks to you for your efforts ewaller, Head_on_a_Stick and Tarqi.
-C6H8C6
Last edited by C6H8C6 (2015-07-20 00:13:23)
Yes, you are right: of course the second 'C' in my name should be a 'O'
Offline