Wifi Range Extender - Best way to configure

Installing and Using OpenWrt Network and Wireless Configuration
1

Dear community,

I am running a Linksys WRT3200ACM with OpenWrt and noticed my WLAN does not reach quite as far as I'd like it to reach.
So I figured, I'll buy a Wifi Range Extender/Repeater - my choice fell on NETGEARs EX3800, which also has - luckily - OpenWrt support.
I was able to flash OpenWrt on it and can login via SSH to it without any issues.

However, I am actually unsure, how to achieve what I want to achieve with the EX3800.
My goal is to have the EX3800 replicate/extend the current WIFI signal of both bands (2.4GHz and 5GHz) from the existing network, without building up a new subnet for clients connecting to the EX3800. The EX3800 should be connected wireless to the existing network and replicate/extend the signal of it.
I simply want the clients connecting via Wifi to be able to switch to the EX3800 if the signal of the WRT3200ACM is too low.

I read about different scenarios (either connecting the EX3800 as client to the WRT3200ACM and build up its own network or connecting the EX3800 and the WRT3200ACM via mesh together) and certainly I am unsure, which approach I should choose.
I have never used mesh; This however seems like the "proper" way to go after a quick research.
Furthermore I have checked, both the WRT3200ACM and the EX3800 are "mesh-able", so theoretically it should work out.

What I want to know from the more advanced users here:

  • Is the approach using mesh correct?
  • Are there any good guides I can refer to?
  • If mesh is the correct approach, could you point me to any good background articles about mesh? I want to understand what I am doing, rather than "just doing it to make it work"

My questions might seem noobish, but as I said, I never had this scenario and therefore I am really new to it.

Thank you very much!

Regards,
Steffen

2

The open-source drivers for the WRT3200ACM do not support mesh networks issue 268; you can discard that approach.

It can do WDS-AP however, but you must disable WPA's group key handshake issue 242; and I do not know if the EX3800 can do WDS-STA (and is compatible with the WRT3200ACM).

If possible, I would go for WDS. Otherwise, there are the other less-than-ideal scenarios, like tunneling, relayd, or double-NATing... pick your choice.

1 Like
3

Hello eduperez,

damn, too bad, I was hoping to use mesh!
How could I find out, whether the EX3800 supports WDS-STA?
Also: Could you point me to a guide, how to setup WDS on both devices?

Thank you!

Regards,
Steffen

4

Hello everybody,

I have followed the procedure as described in https://openwrt.org/docs/guide-user/network/wifi/atheroswds.
I think the WDS connection succeeded, as I am able to SSH to the EX3800 from the WRT3200ACM, without any cables connected.

However, there seems to be a strange issue:
On the WRT3200ACM I receive tons and tons of the following messages:

Wed Feb 20 13:54:11 2019 kern.warn kernel: [691297.626094] br-lan: received packet on wlan1.sta2 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:11 2019 kern.warn kernel: [691297.636864] br-lan: received packet on wlan1.sta2 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:11 2019 kern.err kernel: [691297.848227] ieee80211 phy0: slow: space 3774(5410) is not enough
Wed Feb 20 13:54:11 2019 kern.err kernel: [691298.445113] ieee80211 phy0: slow: space 3774(4258) is not enough
Wed Feb 20 13:54:12 2019 kern.err kernel: [691298.905267] ieee80211 phy0: slow: space 3774(4442) is not enough
Wed Feb 20 13:54:12 2019 kern.err kernel: [691299.141673] ieee80211 phy0: slow: space 3774(4443) is not enough
Wed Feb 20 13:54:13 2019 kern.err kernel: [691299.713183] ieee80211 phy0: slow: space 3774(4426) is not enough
Wed Feb 20 13:54:13 2019 kern.err kernel: [691300.198558] ieee80211 phy0: slow: space 3774(4371) is not enough
Wed Feb 20 13:54:13 2019 kern.err kernel: [691300.288790] ieee80211 phy0: slow: space 3774(4586) is not enough
Wed Feb 20 13:54:14 2019 kern.err kernel: [691300.508832] ieee80211 phy0: slow: space 3774(4514) is not enough
Wed Feb 20 13:54:15 2019 kern.err kernel: [691301.690143] ieee80211 phy0: slow: space 3774(4443) is not enough
Wed Feb 20 13:54:15 2019 kern.err kernel: [691301.722479] ieee80211 phy0: slow: space 3774(4586) is not enough
Wed Feb 20 13:54:15 2019 kern.err kernel: [691302.420193] ieee80211 phy0: slow: space 3774(4258) is not enough
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.853492] net_ratelimit: 1150 callbacks suppressed
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.853496] br-lan: received packet on wlan0.sta4 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.877533] br-lan: received packet on wlan0.sta4 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:16 2019 kern.err kernel: [691302.885926] ieee80211 phy0: slow: space 3774(4258) is not enough
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.888802] br-lan: received packet on wlan1.sta2 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.905272] br-lan: received packet on wlan1.sta2 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.916026] br-lan: received packet on wlan1.sta2 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.930877] br-lan: received packet on wlan1.sta2 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.941632] br-lan: received packet on wlan1.sta2 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.952385] br-lan: received packet on wlan1.sta2 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.963138] br-lan: received packet on wlan1.sta2 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:16 2019 kern.warn kernel: [691302.974118] br-lan: received packet on wlan0.sta4 with own address as source address (addr:62:38:e0:cd:92:00, vlan:0)
Wed Feb 20 13:54:17 2019 kern.err kernel: [691303.703421] ieee80211 phy0: slow: space 3774(4586) is not enough
Wed Feb 20 13:54:17 2019 kern.err kernel: [691303.807390] ieee80211 phy0: slow: space 3774(4370) is not enough
Wed Feb 20 13:54:17 2019 kern.err kernel: [691303.877808] ieee80211 phy0: slow: space 3774(4426) is not enough
Wed Feb 20 13:54:18 2019 kern.err kernel: [691304.984240] ieee80211 phy0: slow: space 3774(4586) is not enough
Wed Feb 20 13:54:19 2019 kern.err kernel: [691305.580103] ieee80211 phy0: slow: space 3774(4515) is not enough
Wed Feb 20 13:54:19 2019 kern.err kernel: [691305.603819] ieee80211 phy0: slow: space 3774(4443) is not enough

Any ideas what the issue might be?

For reference following my configuration from the WRT3200ACM:

root@OpenWrt:~# cat /etc/config/wireless 

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path 'soc/soc:pcie/pci0000:00/0000:00:01.0/0000:01:00.0'
        option txpower '20'
        option htmode 'VHT80'
        option country 'DE'
        option turbo '1'
        option bursting '1'
        option channel '36'
        option legacy_rates '1'

config wifi-iface
        option device 'radio0'
        option mode 'ap'
        option network 'lan'
        option ssid 'REMOVED'
        option encryption 'psk2'
        option key 'REMOVED'
        option disassoc_low_ack '0'
        option wds '1'
        option wpa_group_rekey '0'

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11g'
        option path 'soc/soc:pcie/pci0000:00/0000:00:02.0/0000:02:00.0'
        option htmode 'HT40'
        option txpower '20'
        option country 'DE'
        option legacy_rates '1'
        option channel '11'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option macaddr '26:f5:a2:27:04:11'
        option ssid 'REMOVED'
        option encryption 'psk2'
        option key 'REMOVED'
        option wds '1'
        option wpa_group_rekey '0'

config wifi-device 'radio2'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'platform/soc/soc:internal-regs/f10d8000.sdhci/mmc_host/mmc0/mmc0:0001/mmc0:0001:1'
        option htmode 'VHT80'

root@OpenWrt:~# 


root@OpenWrt:~# cat /etc/config/network 

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd89:d980:8713::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0.1'
        option proto 'static'
        option ipaddr '10.10.40.1'
        option netmask '255.255.255.0'

config interface 'wan'
        option ifname 'eth1.2'
        option proto 'static'
        option delegate '0'
        option netmask '255.255.255.0'
        option gateway '192.168.0.1'
        option broadcast '192.168.0.255'
        option dns '8.8.8.8 8.8.4.4 1.1.1.1'
        option ipaddr '192.168.0.101'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 1 2 3 5t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '4 6t'

config route
        option interface 'wan'
        option target '10.10.10.0'
        option netmask '255.255.255.0'
        option gateway '192.168.0.100'

config route
        option interface 'wan'
        option target '10.10.20.0'
        option netmask '255.255.255.0'
        option gateway '192.168.0.100'

config route
        option interface 'wan'
        option target '10.10.30.0'
        option netmask '255.255.255.0'
        option gateway '192.168.0.100'


root@OpenWrt:~# ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 532
    link/ether 60:38:e0:cd:92:00 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6238:e0ff:fecd:9200/64 scope link 
       valid_lft forever preferred_lft forever
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 532
    link/ether 62:38:e0:cd:92:00 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6038:e0ff:fecd:9200/64 scope link 
       valid_lft forever preferred_lft forever
325: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 62:38:e0:cd:92:00 brd ff:ff:ff:ff:ff:ff
    inet 10.10.40.1/24 brd 10.10.40.255 scope global br-lan
       valid_lft forever preferred_lft forever
326: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP qlen 1000
    link/ether 62:38:e0:cd:92:00 brd ff:ff:ff:ff:ff:ff
327: eth1.2@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 60:38:e0:cd:92:00 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.101/24 brd 192.168.0.255 scope global eth1.2
       valid_lft forever preferred_lft forever
328: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP qlen 1000
    link/ether 26:f5:a2:27:04:11 brd ff:ff:ff:ff:ff:ff
329: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP qlen 1000
    link/ether 60:38:e0:cd:92:02 brd ff:ff:ff:ff:ff:ff
330: wlan1.sta2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UNKNOWN qlen 1000
    link/ether 26:f5:a2:27:04:11 brd ff:ff:ff:ff:ff:ff
331: wlan0.sta4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UNKNOWN qlen 1000
    link/ether 60:38:e0:cd:92:02 brd ff:ff:ff:ff:ff:ff
root@OpenWrt:~#

And the configuration from the EX3800:

root@RepeaterWrt:~# cat /etc/config/wireless 

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
        option htmode 'VHT80'
        option country 'DE'
        option turbo '1'
        option bursting '1'
        option channel '36'
        option legacy_rates '1'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'sta'
        option ssid 'REMOVED'
        option encryption 'psk2'
        option key 'REMOVED'
        option disassoc_low_ack '0'
        option wds '1'
        option wpa_group_rekey '0'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '11'
        option hwmode '11g'
        option path 'platform/10180000.wmac'
        option htmode 'HT40'
        option txpower '20'
        option country 'DE'
        option legacy_rates '1'
        option channel '11'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'sta'
        option ssid 'REMOVED'
        option encryption 'psk2'
        option key 'REMOVED'
        option wds '1'
        option wpa_group_rekey '0'

root@RepeaterWrt:~# 

root@RepeaterWrt:~# cat /etc/config/network 

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd1b:19d4:0209::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0'
        option proto 'static'
        option ipaddr '10.10.40.3'
        option netmask '255.255.255.0'
        option ip6assign '60'

config device 'lan_dev'
        option name 'eth0'
        option macaddr '78:d2:94:10:b6:a4'

root@RepeaterWrt:~# 

root@RepeaterWrt:~# ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UNKNOWN qlen 1000
    link/ether 78:d2:94:10:b6:a4 brd ff:ff:ff:ff:ff:ff
5: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 78:d2:94:10:b6:a4 brd ff:ff:ff:ff:ff:ff
    inet 10.10.40.3/24 brd 10.10.40.255 scope global br-lan
       valid_lft forever preferred_lft forever
    inet6 fd1b:19d4:209::1/60 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::7ad2:94ff:fe10:b6a4/64 scope link 
       valid_lft forever preferred_lft forever
6: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP qlen 1000
    link/ether 78:d2:94:10:b6:a3 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::7ad2:94ff:fe10:b6a3/64 scope link 
       valid_lft forever preferred_lft forever
7: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP qlen 1000
    link/ether 78:d2:94:10:b6:a4 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::7ad2:94ff:fe10:b6a4/64 scope link 
       valid_lft forever preferred_lft forever
root@RepeaterWrt:~#
5

You have created two links between the routers, and at both ends the links are bridged together... in general, you should not create loops between two nodes in a network, unless you know what you are doing, and do it explicitly (you will need to enable STP for this to work).

Unless you really need all the bandwidth, you do not have to create two links; you can use just the 5GHz radio for the link, and still serve both the 2.4GHz and 5GHz bands on the extender. Or you can use the 5GHz band to extend the 2.4GHz band, and viceversa. Or you can try some more esoteric configurations. But just do not bridge the links together on the extender.

2 Likes
6

Hello eduperez,

thank you for your answer, this actually solves my problem!
However, I have another question regarding the wifi of the EX3800 you might be able to answer.
I want to use the 5GHz network as WDS "bridge" and also replicate the 5GHz and 2.4Ghz wifi network from the WRT3200ACM.
If I create the WDS "bridge" with the 2.4GHz channel I can bring up the WDS bridge and also both additional wifi networks.
However, when I try to do the same with the 5GHz network (=creating the WDS bridge with the 5GHz network) I fail bringing up the additional 5GHz interface.
I want to use the 5GHz to have more bandwidth available within the bridge (for downloads for example).

When I take a look at iw list on the EX3800 I see the following information:

root@RepeaterWrt:~# iw list
Wiphy phy1
        max # scan SSIDs: 4
        max scan IEs length: 2257 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short long limit: 2
        Coverage class: 0 (up to 0m)
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 1:
                Capabilities: 0x2fe
                        HT20/HT40
                        SM Power Save disabled
                        RX Greenfield
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 2-streams
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 2 usec (0x04)
                HT TX/RX MCS rate indexes supported: 0-15, 32
                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)
        valid interface combinations:
                 * #{ managed, AP, mesh point } <= 8,
                   total <= 8, #channels <= 1
        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
        Supported extended features:
                * [ RRM ]: RRM
                * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
Wiphy phy0
        max # scan SSIDs: 4
        max scan IEs length: 2247 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 2:
                Capabilities: 0x1ff
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX Greenfield
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        No 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-15
                VHT Capabilities (0x018001b0):
                        Max MPDU length: 3895
                        Supported Channel Width: neither 160 nor 80+80
                        RX LDPC
                        short GI (80 MHz)
                        TX STBC
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        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: MCS 0-9
                        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
                Frequencies:
                        * 5180 MHz [36] (20.0 dBm)
                        * 5200 MHz [40] (20.0 dBm)
                        * 5220 MHz [44] (20.0 dBm)
                        * 5240 MHz [48] (20.0 dBm)
                        * 5260 MHz [52] (20.0 dBm) (radar detection)
                        * 5280 MHz [56] (20.0 dBm) (radar detection)
                        * 5300 MHz [60] (20.0 dBm) (radar detection)
                        * 5320 MHz [64] (20.0 dBm) (radar detection)
                        * 5500 MHz [100] (26.0 dBm) (radar detection)
                        * 5520 MHz [104] (26.0 dBm) (radar detection)
                        * 5540 MHz [108] (26.0 dBm) (radar detection)
                        * 5560 MHz [112] (26.0 dBm) (radar detection)
                        * 5580 MHz [116] (26.0 dBm) (radar detection)
                        * 5600 MHz [120] (26.0 dBm) (radar detection)
                        * 5620 MHz [124] (26.0 dBm) (radar detection)
                        * 5640 MHz [128] (26.0 dBm) (radar detection)
                        * 5660 MHz [132] (26.0 dBm) (radar detection)
                        * 5680 MHz [136] (26.0 dBm) (radar detection)
                        * 5700 MHz [140] (26.0 dBm) (radar detection)
                        * 5745 MHz [149] (13.0 dBm)
                        * 5765 MHz [153] (13.0 dBm)
                        * 5785 MHz [157] (13.0 dBm)
                        * 5805 MHz [161] (13.0 dBm)
                        * 5825 MHz [165] (13.0 dBm)
        valid interface combinations:
                 * #{ IBSS } <= 1, #{ managed, AP, mesh point } <= 8,
                   total <= 8, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

        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
        Supported extended features:
                * [ VHT_IBSS ]: VHT-IBSS
                * [ RRM ]: RRM
                * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
root@RepeaterWrt:~#

This seems like I could use either of my combinations to make it work - is this correct?
As I can see both bands have the ability to provide 8 interfaces (?!), but only on one channel - I have configured it to be on one channel whatsoever, but still wasn't able to bridge with the 5GHz band and bring up another AP on the same band on the EX3800.

Thank you very much!

Regards,
Steffen

7

Something does not add here... if you cannot use the 5GHz band for WDS, then you could not create a loop when you used both at the same time... see what I mean?

I am not an expert at interpreting the output of "iw list", most of that output is just blurry to me, sorry.

I would try again to use WDS on the 5GHz channel, double-check the config files, and try to see if the logs give any meaningful information.

8

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.