gargoyle-ispy 2017-June-14 21:40.torrent

Want to share your OpenWrt / Gargoyle knowledge? Implemented a new feature? Let us know here.

Moderator: Moderators

Lantis
Moderator
Posts: 6735
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by Lantis »

sigwx wrote:Updated a WD My Net N750, did -not- preserve settings. So far have noticed:
  • - Adding themes from plugins (just the version 1.9.2-1 entries) does not cause the Themes item to show up under system, so I can't enable them
Only the Gargoyle modern and Dark One are updated. The others will not show up in the menu.
- The Connection Basic config for the 5Ghz allows selection of frequencies that aren't supported? I tried channel 60 and the system logs reports:
I get this same message for selections from 52 thru 140.
[/list]
Those are DFS channels. They may not be available in your area, or there is another issue
Can you please provide the output of:
iw phy1 info
(Assuming phy1 is your 5ghz, otherwise do phy0)
And
iw reg get
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

Lantis
Moderator
Posts: 6735
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by Lantis »

sigwx wrote:Trying on a Linksys WRT1900ACS and noticed that the 5Ghz spectrum analyzer doesn't produce a chart. I know 5Ghz is on and working as I'm connected to it ;-). I don't see anything in the log to help diagnose, is there a way to run it via command line to see why its not working? Thanks!
You won't see your own local signal, only others. Fire up another 5ghz router and see.
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

sigwx
Posts: 70
Joined: Fri Oct 23, 2015 4:14 am

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by sigwx »

Sorry I was unclear with my statement. There a graph was never generated for 5Ghz, worked fine for 2.4Ghz. Never figured out why.... but after several attempts to find a channel that all my devices could reach, it started displaying a graph. Odd.

Its also showing my other Gargoyle (I have two) as 80+80MHz when its configured for 40MHz 2nd channel below, not sure if that makes sense or not.

sigwx
Posts: 70
Joined: Fri Oct 23, 2015 4:14 am

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by sigwx »

Lantis wrote:
sigwx wrote:Updated a WD My Net N750, did -not- preserve settings. So far have noticed:
  • - Adding themes from plugins (just the version 1.9.2-1 entries) does not cause the Themes item to show up under system, so I can't enable them
Only the Gargoyle modern and Dark One are updated. The others will not show up in the menu.
Interesting, I was able to download/enable the Light-Theme from my WRT1900ACS and use it and guessed that the 1.9.2-1 versions were 'updated'. Thanks for the info!
Lantis wrote:
sigwx wrote: - The Connection Basic config for the 5Ghz allows selection of frequencies that aren't supported? I tried channel 60 and the system logs reports:
I get this same message for selections from 52 thru 140.
[/list]
Those are DFS channels. They may not be available in your area, or there is another issue
Can you please provide the output of:
iw phy1 info
(Assuming phy1 is your 5ghz, otherwise do phy0)
And
iw reg get
Sure thing (I'm in the US and its a US model):

Code: Select all

# iw phy1 info
Wiphy phy1
        max # scan SSIDs: 4
        max scan IEs length: 2261 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Device supports T-DLS.
        Available Antennas: TX 0x7 RX 0x7
        Configured Antennas: TX 0x7 RX 0x7
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * outside context of a BSS
        Band 2:
                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
                Frequencies:
                        * 5180 MHz [36] (17.0 dBm)
                        * 5200 MHz [40] (17.0 dBm)
                        * 5220 MHz [44] (17.0 dBm)
                        * 5240 MHz [48] (17.0 dBm)
                        * 5260 MHz [52] (17.0 dBm) (no IR, radar detection)
                        * 5280 MHz [56] (17.0 dBm) (no IR, radar detection)
                        * 5300 MHz [60] (17.0 dBm) (no IR, radar detection)
                        * 5320 MHz [64] (17.0 dBm) (no IR, radar detection)
                        * 5500 MHz [100] (22.0 dBm) (no IR, radar detection)
                        * 5520 MHz [104] (22.0 dBm) (no IR, radar detection)
                        * 5540 MHz [108] (22.0 dBm) (no IR, radar detection)
                        * 5560 MHz [112] (22.0 dBm) (no IR, radar detection)
                        * 5580 MHz [116] (22.0 dBm) (no IR, radar detection)
                        * 5600 MHz [120] (22.0 dBm) (no IR, radar detection)
                        * 5620 MHz [124] (22.0 dBm) (no IR, radar detection)
                        * 5640 MHz [128] (22.0 dBm) (no IR, radar detection)
                        * 5660 MHz [132] (22.0 dBm) (no IR, radar detection)
                        * 5680 MHz [136] (22.0 dBm) (no IR, radar detection)
                        * 5700 MHz [140] (22.0 dBm) (no IR, radar detection)
                        * 5745 MHz [149] (22.0 dBm)
                        * 5765 MHz [153] (22.0 dBm)
                        * 5785 MHz [157] (22.0 dBm)
                        * 5805 MHz [161] (22.0 dBm)
                        * 5825 MHz [165] (22.0 dBm)
        valid interface combinations:
                 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

                 * #{ 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

Code: Select all

# iw reg get
global
country US: DFS-FCC
        (2402 - 2472 @ 40), (N/A, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)

phy#1
country US: DFS-FCC
        (2402 - 2472 @ 40), (N/A, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)

phy#0
country US: DFS-FCC
        (2402 - 2472 @ 40), (N/A, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)

global
country US: DFS-FCC
        (2402 - 2472 @ 40), (N/A, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)

Lantis
Moderator
Posts: 6735
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by Lantis »

sigwx wrote:Sorry I was unclear with my statement. There a graph was never generated for 5Ghz, worked fine for 2.4Ghz. Never figured out why.... but after several attempts to find a channel that all my devices could reach, it started displaying a graph. Odd.

Its also showing my other Gargoyle (I have two) as 80+80MHz when its configured for 40MHz 2nd channel below, not sure if that makes sense or not.
Yes there is a little bit of broken logic surrounding the more complex bandwidths. I was using test data provided from another user but a test sample of one should never Be the basis for programming :P it's on my list of things to investigate.
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

Lantis
Moderator
Posts: 6735
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by Lantis »

sigwx wrote:
Lantis wrote:
sigwx wrote:Updated a WD My Net N750, did -not- preserve settings. So far have noticed:
  • - Adding themes from plugins (just the version 1.9.2-1 entries) does not cause the Themes item to show up under system, so I can't enable them
Only the Gargoyle modern and Dark One are updated. The others will not show up in the menu.
Interesting, I was able to download/enable the Light-Theme from my WRT1900ACS and use it and guessed that the 1.9.2-1 versions were 'updated'. Thanks for the info!
Lantis wrote:
sigwx wrote: - The Connection Basic config for the 5Ghz allows selection of frequencies that aren't supported? I tried channel 60 and the system logs reports:
I get this same message for selections from 52 thru 140.
[/list]
Those are DFS channels. They may not be available in your area, or there is another issue
Can you please provide the output of:
iw phy1 info
(Assuming phy1 is your 5ghz, otherwise do phy0)
And
iw reg get
Sure thing (I'm in the US and its a US model):

Code: Select all

# iw phy1 info
Wiphy phy1
        max # scan SSIDs: 4
        max scan IEs length: 2261 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Device supports T-DLS.
        Available Antennas: TX 0x7 RX 0x7
        Configured Antennas: TX 0x7 RX 0x7
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * outside context of a BSS
        Band 2:
                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
                Frequencies:
                        * 5180 MHz [36] (17.0 dBm)
                        * 5200 MHz [40] (17.0 dBm)
                        * 5220 MHz [44] (17.0 dBm)
                        * 5240 MHz [48] (17.0 dBm)
                        * 5260 MHz [52] (17.0 dBm) (no IR, radar detection)
                        * 5280 MHz [56] (17.0 dBm) (no IR, radar detection)
                        * 5300 MHz [60] (17.0 dBm) (no IR, radar detection)
                        * 5320 MHz [64] (17.0 dBm) (no IR, radar detection)
                        * 5500 MHz [100] (22.0 dBm) (no IR, radar detection)
                        * 5520 MHz [104] (22.0 dBm) (no IR, radar detection)
                        * 5540 MHz [108] (22.0 dBm) (no IR, radar detection)
                        * 5560 MHz [112] (22.0 dBm) (no IR, radar detection)
                        * 5580 MHz [116] (22.0 dBm) (no IR, radar detection)
                        * 5600 MHz [120] (22.0 dBm) (no IR, radar detection)
                        * 5620 MHz [124] (22.0 dBm) (no IR, radar detection)
                        * 5640 MHz [128] (22.0 dBm) (no IR, radar detection)
                        * 5660 MHz [132] (22.0 dBm) (no IR, radar detection)
                        * 5680 MHz [136] (22.0 dBm) (no IR, radar detection)
                        * 5700 MHz [140] (22.0 dBm) (no IR, radar detection)
                        * 5745 MHz [149] (22.0 dBm)
                        * 5765 MHz [153] (22.0 dBm)
                        * 5785 MHz [157] (22.0 dBm)
                        * 5805 MHz [161] (22.0 dBm)
                        * 5825 MHz [165] (22.0 dBm)
        valid interface combinations:
                 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

                 * #{ 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

Code: Select all

# iw reg get
global
country US: DFS-FCC
        (2402 - 2472 @ 40), (N/A, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)

phy#1
country US: DFS-FCC
        (2402 - 2472 @ 40), (N/A, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)

phy#0
country US: DFS-FCC
        (2402 - 2472 @ 40), (N/A, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)

global
country US: DFS-FCC
        (2402 - 2472 @ 40), (N/A, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)
The themes still show up as valid to install (and version numbers look new, but are just byproducts of the build code). But enabling them on the new GUI will probably look terrible and not function well.

Have you set your country to US for each of your interfaces? It looks like it is set to global, which is probably why it isn't working properly.
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

sigwx
Posts: 70
Joined: Fri Oct 23, 2015 4:14 am

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by sigwx »

Lantis wrote:
sigwx wrote:
Lantis wrote: Have you set your country to US for each of your interfaces? It looks like it is set to global, which is probably why it isn't working properly.
I'm not sure on how to do that, is it just adding "country='US'" to the wireless config file?

How do you tell what its configured for? It looked like from the "iw reg get" results

Code: Select all

...
phy#1
country US: DFS-FCC
...
that it was set for US?

sigwx
Posts: 70
Joined: Fri Oct 23, 2015 4:14 am

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by sigwx »

sigwx wrote:
Lantis wrote:
sigwx wrote:
I'm not sure on how to do that, is it just adding "country='US'" to the wireless config file?

How do you tell what its configured for? It looked like from the "iw reg get" results

Code: Select all

...
phy#1
country US: DFS-FCC
...
that it was set for US?

Manually setting "country='US'" and then channel 64 and all seems well... Thanks for the help!

Lantis
Moderator
Posts: 6735
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by Lantis »

No worries. Thought that would be the answer.
That sets up the correct regulatory settings and lets the DFS module fire.
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

sigwx
Posts: 70
Joined: Fri Oct 23, 2015 4:14 am

Re: gargoyle-ispy 2017-June-14 21:40.torrent

Post by sigwx »

I don't remember if I was using channel 64 before, but I don't remember making the manual change to the wireless config. I think i was back at 1.9.1 before, could this have changed with 1.9.2?

Post Reply