Bananian
Can't connect via wifi after disconnecting wired network
11
2273
View: 2273|Reply: 11
|
[Bananian]
Can't connect via wifi after disconnecting wired network
[Copy link]
|
|
Edited by AR9285 at Mon Sep 28, 2015 04:56
Hi,
I'm using bananian 15.08 on banana pro, /etc/network/interfaces and wpa_suppicant.conf are configured per wiki.
Both wireless and wired network are connected, say:
Wired network: 192.168.1.106
Wireless network: 192.168.1.105
And I can ssh to the bPro via both wireless and wired network.
However:
1. I can't see the wireless client in router's page, only wired client are shown
2. After pulling out the ethernet cable, I can't connect to the bPro via wireless. Reconnecting the ethernet cable and check the log only to found out that wireless stay connected after ethernet cable are unplugged. But I cannot connect to it.
Here is the log:
- Sep 28 17:47:26 debian-bpro dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
- Sep 28 17:47:26 debian-bpro dhclient: DHCPOFFER from 192.168.1.1
- Sep 28 17:47:26 debian-bpro dhclient: DHCPACK from 192.168.1.1
- Sep 28 17:47:26 debian-bpro dhclient: bound to 192.168.1.105 -- renewal in 77403 seconds.
- Sep 28 17:47:28 debian-bpro ntpd[1212]: Listen normally on 9 wlan0 192.168.1.105 UDP 123
- Sep 28 17:47:28 debian-bpro ntpd[1212]: peers refreshed
- Sep 28 17:47:32 debian-bpro kernel: [ 916.484365] [ap6210] Chip: a962 Rev 1 Pkg 9
- Sep 28 17:47:32 debian-bpro kernel: [ 927.423911] wlan0: no IPv6 routers present
- Sep 28 17:49:54 debian-bpro kernel: [ 1069.487608] PHY: sunxi_gmac-0:00 - Link is Down
- Sep 28 17:50:15 debian-bpro kernel: [ 1090.498314] PHY: sunxi_gmac-0:00 - Link is Up - 100/Full
Copy the Code
Also it seems that I cannot reliably get DHCPOFFER from the router.
Any ideas?
Thanks! |
|
|
|
|
|
|
|
Hi AR9285,
could you paste the settings from your /etc/network/interfaces file?
There must be an entry something like:
auto wlan0
iface wlan0 inet dhcp
greets
Nebkas
|
|
|
|
|
|
|
|
Edited by AR9285 at Mon Sep 28, 2015 05:24
Thanks.
/etc/network/interfaces :
- # interfaces(5) file used by ifup(8) and ifdown(8)
- # Include files from /etc/network/interfaces.d:
- source-directory /etc/network/interfaces.d
- auto lo
- iface lo inet loopback
- auto eth0
- # dhcp configuration
- iface eth0 inet dhcp
- # static ip configuration
- #iface eth0 inet static
- # address 192.168.6.241
- # netmask 255.255.255.0
- # gateway 192.168.6.1
- auto wlan0
- iface wlan0 inet dhcp
- pre-up wpa_supplicant -d -B -Dwext -i wlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
- pre-down killall -q wpa_supplicant
Copy the Code
wpa_suppicant.conf:
- ap_scan=1 # use the wpa_supplicant to scan and choose the AP
- network={
- ssid="myAP"
- psk="blah"
- }
Copy the Code
Now only once in 10 attempts I can get DHCPACK and bound to an address. The other 9 times no DHCPOFFER was received, no DHCPDISCOVER shown up in router's log.
Thanks!
|
|
|
|
|
|
|
|
Edited by AR9285 at Mon Sep 28, 2015 05:30
Because I used '-d' switch on wpa_suppicant, I see some suspicious output: (wlan0: State: DISCONNECTED -> DISCONNECTED)
- WEXT: cfg80211-based driver detected
- wext: interface wlan0 phy: phy0
- rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
- rfkill: initial event: idx=1 type=1 op=0 soft=0 hard=0
- SIOCGIWRANGE: WE(compiled)=22 WE(source)=19 enc_capa=0xf
- capabilities: key_mgmt 0xf enc 0x1f flags 0x0
- netlink: Operstate: ifindex=4 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)
- Add interface wlan0 to a new radio phy0
- wlan0: Own MAC address: 98:3b:16:e8:11:72
- wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
- wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
- wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
- wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
- wpa_driver_wext_set_key: alg=0 key_idx=4 set_tx=0 seq_len=0 key_len=0
- ioctl[SIOCSIWENCODEEXT]: Invalid argument
- Driver did not support SIOCSIWENCODEEXT
- wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
- ioctl[SIOCSIWENCODEEXT]: Invalid argument
- Driver did not support SIOCSIWENCODEEXT
- wpa_driver_wext_set_countermeasures
- wlan0: RSN: flushing PMKID list in the driver
- wlan0: Setting scan request: 0.100000 sec
- TDLS: TDLS operation not supported by driver
- TDLS: Driver uses internal link setup
- wlan0: WPS: UUID based on MAC address: 6b35fe7f-aaec-5797-8b6a-07b3edaa6cf9
- EAPOL: SUPP_PAE entering state DISCONNECTED
- EAPOL: Supplicant port status: Unauthorized
- 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: DISCONNECTED -> DISCONNECTED
- wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
- netlink: Operstate: ifindex=4 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
- Daemonize..
- Internet Systems Consortium DHCP Client 4.3.1
- Copyright 2004-2014 Internet Systems Consortium.
- All rights reserved.
- For info, please visit [url=https://www.isc.org/software/dhcp/]https://www.isc.org/software/dhcp/[/url]
- Listening on LPF/wlan0/98:3b:16:e8:11:72
- Sending on LPF/wlan0/98:3b:16:e8:11:72
- Sending on Socket/fallback
- DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
- DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
- ....
- (no dhcpoffer received.)
Copy the Code
...and also in syslog: ([ap6210] wl_iw_set_wap: WLC_REASSOC failed (-22).)
- Sep 28 19:25:29 debian-bpro dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
- Sep 28 19:25:30 debian-bpro kernel: [ 669.625858] [ap6210] Chip: a962 Rev 1 Pkg 9
- Sep 28 19:25:30 debian-bpro kernel: [ 671.089844] [ap6210] scan is not ready
- Sep 28 19:25:30 debian-bpro kernel: [ 671.117352] [ap6210] Setting the D11auth 1
- Sep 28 19:25:30 debian-bpro kernel: [ 671.140090] [ap6210] wl_iw_set_wap: WLC_REASSOC failed (-22).
- Sep 28 19:25:32 debian-bpro dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
- Sep 28 19:25:34 debian-bpro ntpd[1348]: Listen normally on 9 wlan0 fe80::9a3b:16ff:fee8:1172 UDP 123
- Sep 28 19:25:34 debian-bpro ntpd[1348]: peers refreshed
- Sep 28 19:25:40 debian-bpro kernel: [ 680.713882] wlan0: no IPv6 routers present
Copy the Code |
|
|
|
|
|
|
|
May you could put this into your /etc/network/interfaces
- allow-hotplug eth0
- allow-hotplug wlan0
Copy the Code
Does it work in static configuration from wlan0? |
|
|
|
|
|
|
|
Edited by AR9285 at Mon Sep 28, 2015 05:47
Thanks.
I can use static ip address to connect, but the problem in #1 persists.
- auto wlan0
- allow-hotplug wlan0
- iface wlan0 inet static
- pre-up wpa_supplicant -d -B -Dwext -i wlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
- address 192.168.1.110
- netmask 255.255.255.0
- pre-down killall -q wpa_supplicant
Copy the Code
While connected:
- # iwconfig
- wlan0 Link encap:Ethernet HWaddr 98:3b:16:e8:11:72
- inet addr:192.168.1.110 Bcast:192.168.1.255 Mask:255.255.255.0
- inet6 addr: fe80::9a3b:16ff:fee8:1172/64 Scope:Link
- UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
- RX packets:26 errors:0 dropped:0 overruns:0 frame:0
- TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
- collisions:0 txqueuelen:1000
- RX bytes:2542 (2.4 KiB) TX bytes:11754 (11.4 KiB)
Copy the Code
- #route -nv
- Kernel IP routing table
- Destination Gateway Genmask Flags Metric Ref Use Iface
- 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
- 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
- 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
Copy the Code
And I can ping 192.168.1.110 from my other machine.
After pulling out the ethernet cable, I cannot ping 192.168.1.110 anymore. |
|
|
|
|
|
|
|
ah ok.
Try to add:
and maybe a nameserver to your wlan0 device
It seems like wlan0 doesn' know where to put the packages |
|
|
|
|
|
|
|
And what does show you
iptables -nvL
|
|
|
|
|
|
|
|
1. rt5370 USB wifi adapter - same problem, but can get DHCPACK more reliably
2. static address - same problem
So:
1. not ap6120 driver issue, not an ap6181 hardware issue
2. not DHCP issue
What could be the problem? |
|
|
|
|
|
|
|
In your logfile i'd seen that u use the 'wext' driver for your wlan0. Maybe you can use a propper rt5370 driver.
Sorry that I couldn't help you so long |
|
|
|
|
|
|