Hi all!
I'm new to the world of Openwrt, i read various guides and forum/reddit posts how to set up Openwrt for the first time.
My setup is 2x Netgear WAX206.
I have a fiber 1000/1000 Odido (netherlands) IPV4 ONLY provider (it's cheap)
My main router Wax206 is at the front of my house were the fiber is coming inside and directly connected without any modem. With the correct VLAN 300 configuered it is working great.
The second wired running AP mode same performance.
I have seperate 2.4/5ghz wireless interface.
With 5ghz, AX, 160hz, channel 36, my speedtest with my Pixel 9 is 940/940 Mbps this is great.
Question 1: App Wifiman reports only 80hz, but is saw a 250 Mbps speed increase when i configurerd the interface from 80->160hz so there is something changing.
Only it reports only 80 hz?
My Wifi 2.4 ghz, N, 40 hz, channel 6, country NL, (bit crowded in the area but others also)
I get only MAX 50/50 Mbps, isn't this too low? (I know Wax206 doesn't have AX)
Any advice?
brada4
October 15, 2024, 4:30pm
2
joostnl:
.4 ghz, N, 40 hz, channel 6, country NL
40mhz wide in 2.4 does not work well in presence of other transmissions.
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </>
" button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
1 Like
You may have a look here: https://forum.openwrt.org/t/buying-router-with-longest-possible-openwrt-support/211575/30?u=underworld . I had the same question, @fakemanhk confirms it is 160. I do not have access to my RT3200 to test with other than wifiman apps, however you may want to try.
Kr
K
1 Like
brada4
October 15, 2024, 4:46pm
4
Try this:
Android application to analyze WiFi signals.
can you post at least ubus call and wireless config parts?
What mode is indicated by iwinfo
?
EDIT: yes, manufacturers spec confirms it is 160MHz capable, though in EU you need DFS for it, thus preferably auto-channel to warrant escaping radar.
1 Like
In fact from this I saw the 160MHz support was removed for a while then being added back, maybe the time you see that no 160MHz was because of that? (I purchased mine and the date was after the commit date of the following)
opened 03:13PM - 13 Feb 23 UTC
closed 10:28AM - 02 Mar 23 UTC
Please revert this removals regarding MT7915, MT7915 works just fine with HE160,… been using this for over a month when I got this powerful client. Please see my tests in the comment below.
https://github.com/openwrt/mt76/commit/98aa346042bd21fe8c0b1594736edca16be436db#commitcomment-99775400
@nbd168 @MeiChia.Chiu
Well, yes I did stop tracking the 160 Mhz support at certain point, but last week I updated the router to the latest snapshot and again wifiman was showing 80 Mhz. I belive this is an app error. It may be worth to check it with another app.
Kr
K
PS: I will check that on the Belkin Rt3200 later this week.
1 Like
Thanks for you fast response, i switched from 40hz -> 20 hz on 2.4Ghz and it didn't improve.
root@OpenWrt:~#
root@OpenWrt:~# ubus call system board
{
"kernel": "5.15.150",
"hostname": "OpenWrt",
"system": "ARMv8 Processor rev 4",
"model": "Netgear WAX206",
"board_name": "netgear,wax206",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.3",
"revision": "r23809-234f1a2efa",
"target": "mediatek/mt7622",
"description": "OpenWrt 23.05.3 r23809-234f1a2efa"
}
}
root@OpenWrt:~# cat /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd52:3db5:53e3::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option device 'wan.300'
option proto 'dhcp'
option type 'bridge'
config interface 'wan6'
option device 'wan.300'
option proto 'dhcpv6'
option type 'bridge'
option reqaddress 'try'
option reqprefix 'auto'
root@OpenWrt:~# cat /etc/config/wireless
config wifi-device 'radio0'
option type 'mac80211'
option path 'platform/18000000.wmac'
option channel '6'
option band '2g'
option htmode 'HT40'
option cell_density '0'
option country 'NL'
config wifi-device 'radio1'
option type 'mac80211'
option path '1a143000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option channel '36'
option band '5g'
option htmode 'HE160'
option country 'NL'
option cell_density '0'
config wifi-iface 'wifinet2'
option device 'radio0'
option mode 'ap'
option ssid 'xx_2.4G'
option encryption 'psk2'
option key 'xx'
option network 'lan'
config wifi-iface 'wifinet4'
option device 'radio1'
option mode 'ap'
option ssid 'xxx_5Ghz'
option encryption 'psk2'
option key 'xx'
option network 'lan'
option ieee80211r '1'
option ft_over_ds '0'
option ft_psk_generate_local '1'
root@OpenWrt:~# cat /etc/config/dhcp
config dnsmasq
option domainneeded '1'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option cachesize '1000'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option localservice '1'
option ednspacket_max '1232'
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'server'
option ra 'server'
list ra_flags 'managed-config'
list ra_flags 'other-config'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
config host
option name 'Evohome'
option dns '1'
option mac 'xx'
option ip '192.168.1.6'
+Many more static DHCP
root@OpenWrt:~# cat /etc/config/firewall
config defaults
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option synflood_protect '1'
option flow_offloading '1'
option flow_offloading_hw '1'
config zone
option name 'lan'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
list network 'lan'
config zone
option name 'wan'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'
list network 'wan'
list network 'wan6'
config forwarding
option src 'lan'
option dest 'wan'
config rule
option name 'Allow-DHCP-Renew'
option src 'wan'
option proto 'udp'
option dest_port '68'
option target 'ACCEPT'
option family 'ipv4'
config rule
option name 'Allow-Ping'
option src 'wan'
option proto 'icmp'
option icmp_type 'echo-request'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-IGMP'
option src 'wan'
option proto 'igmp'
option family 'ipv4'
option target 'ACCEPT'
config rule
option name 'Allow-DHCPv6'
option src 'wan'
option proto 'udp'
option dest_port '546'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-MLD'
option src 'wan'
option proto 'icmp'
option src_ip 'fe80::/10'
list icmp_type '130/0'
list icmp_type '131/0'
list icmp_type '132/0'
list icmp_type '143/0'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Input'
option src 'wan'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
list icmp_type 'router-solicitation'
list icmp_type 'neighbour-solicitation'
list icmp_type 'router-advertisement'
list icmp_type 'neighbour-advertisement'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-ICMPv6-Forward'
option src 'wan'
option dest '*'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'
config rule
option name 'Allow-IPSec-ESP'
option src 'wan'
option dest 'lan'
option proto 'esp'
option target 'ACCEPT'
config rule
option name 'Allow-ISAKMP'
option src 'wan'
option dest 'lan'
option dest_port '500'
option proto 'udp'
option target 'ACCEPT'
root@OpenWrt:~#
Thanks for your fast answer, maybe channel change would make diffrence iets only 2.5 star in wifi analyzer, 5 star is also possible.
My 2.4 ghz is more for stability for IOT devices tasmota/esphome etc, so speed is not a huge problem.
root@OpenWrt:~# iwinfo
wl0-ap0 ESSID: "xx_2.4G"
Access Point: xx
Mode: Master Channel: 6 (2.437 GHz) HT Mode: HT20
Center Channel 1: 6 2: unknown
Tx-Power: 20 dBm Link Quality: 55/70
Signal: -55 dBm Noise: -91 dBm
Bit Rate: 70.0 MBit/s
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11b/g/n
Hardware: embedded [MediaTek MT7622]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: wl0
wl1-ap0 ESSID: "xx_5Ghz"
Access Point: xx
Mode: Master Channel: 36 (5.180 GHz) HT Mode: HE160
Center Channel 1: 50 2: unknown
Tx-Power: 23 dBm Link Quality: unknown/70
Signal: unknown Noise: unknown
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/ax/n
Hardware: xx [MediaTek MT7915E]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: wl1
I tried with android app, WIFI analyser Open source, same result 80hz.
When I initially put my setup on 5GHZ 80hz, i get +-700/700 Mbps.
When i ENABLED 160hz, it went too 940/940, so it made a diffrence.
Maybe if i upgrade too latest stable it would improve.
joostnl
October 15, 2024, 6:42pm
10
Side question, my log gets spammed with: daemon.warn odhcpd[1860]: No default route present, overriding ra_lifetime!
I found a topic about disabling IPV6 because my ISP doesn't support it yet, does it have any negative impact if I keep it enabled? (Maybe this year the ISP will allow IPV6 and too lazy too revert back then haha)
These days, thanks to the proliferation of cgNAT among new ISPs, IPv4 is indeed not 'enough' anymore.
After switching from VDSL to ftth, I only get cgNAT and a semi-static /56 IPv6 prefix - if IPv6 fails for some reason, my incoming (road-warrior) VPN connections are gone, that would be a significant problem for me. With the cgNAT IPv4 address (only), I'd also be hassled a lot more with captchas and other server side defenses against against weird usage patterns and access throttling.
Due to m…
Hmm that's interesting. That's what I was trying to point out in the comments of the other topic. Wifiman and ( as it seems) other android apps, reports 160Mhz setup on Cudy Wr3000 and Xiaomi 3000t fine, but not on Belkin rt3200 and apperantly on Netgear wax 206. However Openwrt- Luci reports 160 Mhz.
If you have a 160 Mhz wifi capable PC you can see there as well.. I do not have such.
Kr
K
joostnl
October 15, 2024, 6:54pm
12
I sadly dont have a computer capable 160hz...
1 Like
brada4
October 15, 2024, 6:57pm
13
I think reporting depends on phone's chipset.
iwinfo says it is HE160 so it is that.
You should certainly try 23.05.5 via auc or luci attendedsysupgrade.
2 Likes
On rt3200 I am running the latest snapshot - well at my parents place.
I think you are right that the reporting is differnet than the capabilities, but with switching 160 Mhz on and off in the commits... I am lost what is the current state.
Well @joostnl report improvemnts in the bandwith- so it should be 160.
joostnl
October 15, 2024, 7:08pm
15
I doubled tested switching 80hz to 160hz, speed improvement from 700 to 920 Mbps
1 Like
Ok let's compare the phones - mine Samsung s23.
I do not think both phones use the same chipset.
Kr
K
joostnl
October 15, 2024, 7:25pm
19
I can also hook up a WAX202 and compare running same openwrt version, i try this week.
hecatae
October 15, 2024, 7:29pm
20
I see 160mhz from my wax206 to my mercusys mr90x or my gl.inet mt3000 beryl ax.