gargoyle-ispy 2016-February-20 02:32.torrent

[Lantis]

Thanks to both of you.

It's a pretty major logic error and it'll take me quite some time to fix.
But I'll add it to my list.

I'm actually wondering whether instead of fixing the logic I just write a fix for archers which reverses their wireless devices.

If either of you are comfortable with it and want to test a theory, you could switch the radio designations for both wifi-device entries in your /etc/config/wireless (don't forget to switch the wifi-Ifaces too). Then issue a Wifi command to refresh the connections.

If you then delete /tmp/cached_basic_vars it will re form itself when you visit the connection basic page again. Everything should just work perfectly then.

[ektus]

Thanks to both of you.

It's a pretty major logic error and it'll take me quite some time to fix.
But I'll add it to my list.

I'm actually wondering whether instead of fixing the logic I just write a fix for archers which reverses their wireless devices.

If either of you are comfortable with it and want to test a theory, you could switch the radio designations for both wifi-device entries in your /etc/config/wireless (don't forget to switch the wifi-Ifaces too). Then issue a Wifi command to refresh the connections.

If you then delete /tmp/cached_basic_vars it will re form itself when you visit the connection basic page again. Everything should just work perfectly then.

Maybe, but it doesn't. After switching to the following configuration (toggle 0/1 for radio_ in all three sections) the WAN connection was lost. Reverting the change put things back to working on 2.4GHz.
The code below shows the entire file.

Code: Select all

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11a'
        option path 'pci0000:01/0000:01:00.0'
        option channel '36'
        option htmode 'VHT80'
        option country 'DE'

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11g'
        option path 'platform/qca955x_wmac'
        option country 'DE'
        option htmode 'HT40-'
        option channel '13'

config wifi-iface 'stacfg'
        option device 'radio0'
        option mode 'sta'
        option network 'wan'
        option key 'secret'
        option ssid 'some_router'
        option encryption 'psk2'

Code: Select all

Wed Feb 24 18:36:46 2016 kern.info kernel: [  660.200000] br-wan: port 1(wlan1) entered disabled state
Wed Feb 24 18:36:46 2016 daemon.notice netifd: Bridge 'br-wan' link is down
Wed Feb 24 18:36:46 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Wed Feb 24 18:36:46 2016 daemon.notice netifd: Interface 'wan' is disabled
Wed Feb 24 18:36:46 2016 daemon.notice netifd: wan (2199): udhcpc: SIOCGIFINDEX: No such device
Wed Feb 24 18:36:46 2016 daemon.notice netifd: wan (2199): Received SIGTERM
Wed Feb 24 18:36:47 2016 daemon.notice netifd: radio0 (3628): Successfully initialized wpa_supplicant
Wed Feb 24 18:36:47 2016 daemon.notice netifd: radio0 (3628): l2_packet_init: ioctl[SIOCGIFINDEX]: No such device
Wed Feb 24 18:36:47 2016 daemon.notice netifd: radio0 (3628): wlan1: Failed to open l2_packet connection for the bridge interface 'br-wan'
Wed Feb 24 18:36:47 2016 daemon.notice netifd: radio0 (3628): nl80211: deinit ifname=wlan1 disabled_11b_rates=0
Wed Feb 24 18:36:47 2016 daemon.notice netifd: radio0 (3628): cat: can't open '/var/run/wpa_supplicant-wlan1.pid': No such file or directory
Wed Feb 24 18:36:47 2016 daemon.notice netifd: radio0 (3628): Command failed: Invalid argument
Wed Feb 24 18:36:47 2016 daemon.notice netifd: radio0 (3628): Interface 0 setup failed: WPA_SUPPLICANT_FAILED

The "Connection/Basic" config page shows parameters for both 2.4GHz and 5GHz, but scan yields only 2.4GHz results. If the board attachment quota were to be extended, I could upload a screenshot.

[Lantis]

You can upload to an external website like imgur and then link to here.

Interesting that had no effect.

If you have reverted back to normal, can you do a
iwinfo
And identify which is your 5ghz wlan (probably wlan0).
Then
iwinfo wlan0 scan
And post the results. This will show whether there is a problem looking for 5gig networks.

[ektus]

You can upload to an external website like imgur and then link to here.

Interesting that had no effect.

If you have reverted back to normal, can you do a
iwinfo
And identify which is your 5ghz wlan (probably wlan0).
Then
iwinfo wlan0 scan
And post the results. This will show whether there is a problem looking for 5gig networks.

There's no wlan0, only wlan1 in the iwinfo output:

Code: Select all

root@Gargoyle:/tmp# iwinfo
wlan1     ESSID: "o2-WLAN37"
          Access Point: xx:xx:xx:xx:11:30
          Mode: Client  Channel: 13 (2.472 GHz)
          Tx-Power: 17 dBm  Link Quality: 34/70
          Signal: -76 dBm  Noise: -95 dBm
          Bit Rate: 135.0 MBit/s
          Encryption: WPA2 PSK (CCMP)
          Type: nl80211  HW Mode(s): 802.11bgn
          Hardware: unknown [Generic MAC80211]
          TX power offset: unknown
          Frequency offset: unknown
          Supports VAPs: yes  PHY name: phy1

root@Gargoyle:/tmp#

Regards
Ektus.

[Lantis]

You'll need to create a wireless config for the 5g to make it work.

Easiest is to set to AP and setup a network.

[ektus]

You'll need to create a wireless config for the 5g to make it work.

Easiest is to set to AP and setup a network.

Doing so did result in no wifi at all. Now I tried a firstboot and setting up from scratch, in AP mode both WLAN LEDs are lit, but I'll have to re-configure the country settings and the wifi scan when switching to client mode still shows only 2.4GHz networks. I'm off to work now, the adventure will resume 12 hours from now...

Logread after switching to AP mode, prior to firstboot, so cannot reproduce:

Code: Select all

Thu Feb 25 05:13:21 2016 daemon.err uhttpd[1636]: uci: Entry not found
Thu Feb 25 05:13:21 2016 daemon.err uhttpd[1636]: uci: Invalid argument
Thu Feb 25 05:13:22 2016 daemon.info dnsmasq[17435]: exiting on receipt of SIGTERM
Thu Feb 25 05:13:22 2016 daemon.err uhttpd[1636]: ls: /sys/bus/mdio_bus/drivers/Marvell*/0:*: No such file or directory
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.400000] br-lan: port 2(eth0) entered disabled state
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.400000] br-lan: port 1(eth1) entered disabled state
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.410000] device eth0 left promiscuous mode
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.410000] br-lan: port 2(eth0) entered disabled state
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.420000] device eth1 left promiscuous mode
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.420000] br-lan: port 1(eth1) entered disabled state
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.460000] eth0: link down
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.460000] eth1: link down
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.470000] eth1: link up (1000Mbps/Full duplex)
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.480000] device eth1 entered promiscuous mode
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.480000] br-lan: port 1(eth1) entered forwarding state
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.490000] br-lan: port 1(eth1) entered forwarding state
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'lan' is enabled
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'lan' is setting up now
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'lan' is now up
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'wan6' is enabled
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.510000] device eth0 entered promiscuous mode
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.510000] br-lan: port 2(eth0) entered forwarding state
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.520000] br-lan: port 2(eth0) entered forwarding state
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'loopback' is enabled
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'loopback' is setting up now
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'loopback' is now up
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Network device 'lo' link is up
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'loopback' has link connectivity
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Network device 'eth1' link is up
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Bridge 'br-lan' link is up
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Feb 25 05:13:25 2016 user.notice upnp daemon: external interface not found, not starting
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Network device 'eth0' link is up
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Feb 25 05:13:25 2016 kern.info kernel: [38859.910000] eth0: link up (1000Mbps/Full duplex)
Thu Feb 25 05:13:25 2016 daemon.notice netifd: Interface 'wan6' is now up
Thu Feb 25 05:13:26 2016 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Thu Feb 25 05:13:26 2016 daemon.notice netifd: radio0 (18180): Configuration file: /var/run/hostapd-phy0.conf
Thu Feb 25 05:13:26 2016 daemon.notice netifd: radio1 (18181): Configuration file: /var/run/hostapd-phy1.conf
Thu Feb 25 05:13:27 2016 user.notice dnsmasq: found already running DHCP-server on interface 'br-lan' refusing to start, use 'option force 1' to override
Thu Feb 25 05:13:27 2016 kern.warn kernel: [38861.270000] ath10k_pci 0000:01:00.0: otp stream is empty, using board.bin contents
Thu Feb 25 05:13:27 2016 kern.info kernel: [38861.490000] br-lan: port 1(eth1) entered forwarding state
Thu Feb 25 05:13:27 2016 kern.info kernel: [38861.520000] br-lan: port 2(eth0) entered forwarding state
Thu Feb 25 05:13:28 2016 daemon.err uhttpd[1636]: uci: Entry not found
Thu Feb 25 05:13:28 2016 daemon.err uhttpd[1636]: arping: interface eth0 not found: No such device
Thu Feb 25 05:13:28 2016 daemon.err uhttpd[1636]: ping: sendto: Network is unreachable
Thu Feb 25 05:13:29 2016 kern.info kernel: [38863.400000] device wlan0 entered promiscuous mode
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Feb 25 05:13:29 2016 daemon.info dnsmasq[18394]: started, version 2.73 cachesize 150
Thu Feb 25 05:13:29 2016 daemon.info dnsmasq[18394]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Thu Feb 25 05:13:29 2016 daemon.info dnsmasq[18394]: DNS service limited to local subnets
Thu Feb 25 05:13:29 2016 daemon.info dnsmasq[18394]: using local addresses only for domain lan
Thu Feb 25 05:13:29 2016 daemon.info dnsmasq[18394]: reading /tmp/resolv.conf.auto
Thu Feb 25 05:13:29 2016 daemon.info dnsmasq[18394]: using local addresses only for domain lan
Thu Feb 25 05:13:29 2016 daemon.info dnsmasq[18394]: using nameserver 8.8.8.8#53
Thu Feb 25 05:13:29 2016 daemon.info dnsmasq[18394]: read /etc/hosts - 2 addresses
Thu Feb 25 05:13:29 2016 daemon.info dnsmasq[18394]: read /tmp/hosts/dhcp - 1 addresses
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): Hardware does not support configured mode
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): wlan0: IEEE 802.11 Hardware does not support configured mode (1) (hw_mode in hostapd.conf)
Thu Feb 25 05:13:29 2016 daemon.warn hostapd: wlan0: IEEE 802.11 Hardware does not support configured mode (1) (hw_mode in hostapd.conf)
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): Could not select hw_mode and channel. (-2)
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): wlan0: interface state COUNTRY_UPDATE->DISABLED
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): wlan0: AP-DISABLED
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): wlan0: Unable to setup interface.
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): wlan0: interface state DISABLED->DISABLED
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): wlan0: AP-DISABLED
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): hostapd_free_hapd_data: Interface wlan0 wasn't started
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Thu Feb 25 05:13:29 2016 kern.info kernel: [38863.440000] device wlan0 left promiscuous mode
Thu Feb 25 05:13:29 2016 kern.info kernel: [38863.450000] br-lan: port 3(wlan0) entered disabled state
Thu Feb 25 05:13:29 2016 daemon.warn hostapd: wlan1: IEEE 802.11 Configured channel (36) not found from the channel list of current mode (1) IEEE 802.11g
Thu Feb 25 05:13:29 2016 daemon.warn hostapd: wlan1: IEEE 802.11 Hardware does not support configured channel
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): wlan1: IEEE 802.11 Configured channel (36) not found from the channel list of current mode (1) IEEE 802.11g
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): wlan1: IEEE 802.11 Hardware does not support configured channel
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): Could not select hw_mode and channel. (-3)
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): wlan1: interface state COUNTRY_UPDATE->DISABLED
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): wlan1: AP-DISABLED
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): wlan1: Unable to setup interface.
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): wlan1: interface state DISABLED->DISABLED
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): wlan1: AP-DISABLED
Thu Feb 25 05:13:29 2016 kern.info kernel: [38863.560000] device wlan1 entered promiscuous mode
Thu Feb 25 05:13:29 2016 kern.info kernel: [38863.580000] device wlan1 left promiscuous mode
Thu Feb 25 05:13:29 2016 kern.info kernel: [38863.580000] br-lan: port 3(wlan1) entered disabled state
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): cat: can't open '/var/run/wifi-phy0.pid': No such file or directory
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): cat: can't open '/var/run/wifi-phy1.pid': No such file or directory
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): Command failed: Invalid argument
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio1 (18181): Device setup failed: HOSTAPD_START_FAILED
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): Command failed: Invalid argument
Thu Feb 25 05:13:29 2016 daemon.notice netifd: radio0 (18180): Device setup failed: HOSTAPD_START_FAILED

[yabba235]

Hi !
Is openwrt repo still dow ?
I can't upgrade opkg:

root@Gargoyle:~# opkg update
Downloading http://downloads.openwrt.org/chaos_calm ... ackages.gz.
wget: can't connect to remote host (78.24.191.183): Connection refused
Collected errors:
* opkg_download: Failed to download http://downloads.openwrt.org/chaos_calm ... ackages.gz, wget returned 1.
root@Gargoyle:~# ping -c 3 78.24.191.183
PING 78.24.191.183 (78.24.191.183): 56 data bytes
64 bytes from 78.24.191.183: seq=0 ttl=52 time=53.810 ms
64 bytes from 78.24.191.183: seq=1 ttl=52 time=53.706 ms
64 bytes from 78.24.191.183: seq=2 ttl=52 time=54.619 ms

--- 78.24.191.183 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 53.706/54.045/54.619 ms
root@Gargoyle:~#
but can connect to repo web.

BTW: from web browser i can download any package , so I don't know what happens.

[ektus]

You'll need to create a wireless config for the 5g to make it work.

Easiest is to set to AP and setup a network.

Doing so did result in no wifi at all. Now I tried a firstboot and setting up from scratch, in AP mode both WLAN LEDs are lit, but I'll have to re-configure the country settings and the wifi scan when switching to client mode still shows only 2.4GHz networks. I'm off to work now, the adventure will resume 12 hours from now...

Okay, I'm a little further now. After firstboot with the device in AP mode, both radios were available. Still no scan results on 5GHz, though, at least not in the GUI.
Switch WAN to Wireless (DHCP) with the 2.4GHz host: 5GHz radio is off.
Switch wireless to client+AP: no change. Toggled WAN mode back to wired and again to wireless, with wirelss in Client+AP: Both radios are on, 2.4GHz connection to the host established, iwinfo wlan0 scan yields one result and iwinfo wlan1 scan yields 25 results.
The scan in the GUI still shows only 2.4GHz networks, and so does the spectrum analyser plugin. The latter shows an empty graph for 5GHz, though, so it at least recognized the radio now.

The 5GHz radio still won't work in client mode, though. I can't test AP mode due to lack of 5GHz devices

Phew, what a struggle... But we're getting there

Regards
Ektus.

[Lantis]

I'm actually really confused about where to go next mate. If you can find the network in the command line then it should appear in both the spectrum analyser and the connection basic. They both use the same command.

[ektus]

I'm actually really confused about where to go next mate. If you can find the network in the command line then it should appear in both the spectrum analyser and the connection basic. They both use the same command.

All I can do is enter commands as requested and play around in the GUI.

Code: Select all

root@Gargoyle:~# iwinfo wlan0 scan
Cell 01 - Address: xx:xx:xx:xx:11:31
          ESSID: "o2-WLAN37-5G"
          Mode: Master  Channel: 36
          Signal: -83 dBm  Quality: 27/70
          Encryption: WPA2 PSK (CCMP)

root@Gargoyle:~#

Looks good, but doesn't show in the GUI. What can I do to help debugging? I'll have another half an hour tomorrow morning (8 hours from now) and then again Sunday evening (GMT+1).

Regards
Ektus.