BTW, I was using Raspbian Buster.
I think the key point to use RPi 4 as Router is to find out if both 2.4 and 5 Ghz radios can support a certain number of connected devices. As it was designed to be used as a client it's necessary to make some tests to find out how many associated devices it is able to support.
Another limiting factor are the antennas which are normally present on most traditional routers.
Perhaps it may be used at cabled Wifi Extenders for example. It would be a easy and cheap usage.
What a pity RPI Foundation didn't license the AES Acceleration. Not sure if it would be possible to purchase it separately somehow if you wish to use it for a different use like VPN Concentrator or other.
1 Like
Hello, does any one know that Pi4 can support enable both Wifi AP and client at the same time ? I try to enable AP on channel 36 (success) and then use client to scan for another Wifi AP and try to connect , then seems both AP and client down on PI4.
Anyone have any tests of the pi 4 wired SQM performance? The fact that this is a widely available device with plenty of cores and gigE capable interfaces would seem to point towards using it for wired routing for those fortunate enough to have a 300Mbps or better FTTH or DOCSIS connection. I'd consider it myself if it could handle gigabit FTTH with SQM as my j1900 box sucks much more power. I suspect it's not quite there though. Still for anything less than probably 500Mbps i would expect it to work. Tests anyone?
How does this router stack compared to a R7800? I'm talking about VPN encryption as with my R7800 i can get roughly 7-8mb/s throughput.
Using Pi4, the OpenVPN maximum bandwidth I can see is ~100 Mbps (CPU is unable to handle more, and unfortunately, OpenVPN is single threaded... would have been really cool to have 400 Mbps of VPN throughput)
Without VPN, 1000 Mbps of fiber connection is handled without problem (981 Mbps according to Gnome System Monitor), using AX88179 USB3 for having a second Gigabit Ethernet port
Any idea on which USB-Wifi adaptor are working with OpenWrt/Rpi4 ?
are you running SQM on that fiber link?
Hello, I have RPi 4 and installed OpenWrt tomorrow. Everything is working now (I learned a lot of new things) but is there any way how to upgrade OpenWrt (snapshot) if I want to save all the settings I already made? I used OpenWrt on different device but I have no experience with “snapshot” and how to upgrade it to the latest version. Is it possible to do it via web interface as I did it before on my previous device? And what about the situation when the final release (19.07.0) will be available? Thank you and Happy New Year.
you can grab a backup of your settings from Luci. then you upgrade openwrt, and upload your settings.
if you use the ext4 images you have to do it this way, if there are squashfs images it works just like any other router, you can upgrade in place with the keep settings checked.
I'm having trouble setting the wifi to ap mode on my raspberry pi 4. Client works fine but when I set it to AP Luci just says disabled / no signal ,iwinfo gives this:
root@OpenWrt:~# iwinfo
wlan0 ESSID: "KNW19W"
Access Point: DC:A6:32:6C:E9:6D
Mode: Master Channel: 36 (5.180 GHz)
Tx-Power: 31 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11bgnac
Hardware: 02D0:A9A6 0000:0000 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: no PHY name: phy0
Any ideas?
I wouldn't expect you to get anything much out of the RPi wifi as an AP... It looks like in 5Ghz it can support 20Mhz mode on channels 36,40,44,48 and that's it
iw list
Wiphy phy0
max # scan SSIDs: 10
max scan IEs length: 2048 bytes
max # sched scan SSIDs: 16
max # match sets: 16
max # scan plans: 1
max scan plan interval: 508
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports roaming.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x1022
HT20/HT40
Static SM Power Save
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
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)
Band 2:
Capabilities: 0x1062
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT TX/RX MCS rate indexes supported: 0-7
VHT Capabilities (0x00001020):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
short GI (80 MHz)
SU Beamformee
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: not supported
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: not supported
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
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5170 MHz [34] (disabled)
* 5180 MHz [36] (20.0 dBm)
* 5190 MHz [38] (disabled)
* 5200 MHz [40] (20.0 dBm)
* 5210 MHz [42] (disabled)
* 5220 MHz [44] (20.0 dBm)
* 5230 MHz [46] (disabled)
* 5240 MHz [48] (20.0 dBm)
* 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
* 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
* 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
* 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
* 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
* 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
* 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
* 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
* 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
* 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
* 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
* 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
* 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
* 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
* 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
* 5720 MHz [144] (disabled)
* 5745 MHz [149] (disabled)
* 5765 MHz [153] (disabled)
* 5785 MHz [157] (disabled)
* 5805 MHz [161] (disabled)
* 5825 MHz [165] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* join_ibss
* set_pmksa
* del_pmksa
* flush_pmksa
* remain_on_channel
* frame
* set_wiphy_netns
* set_channel
* tdls_oper
* start_sched_scan
* start_p2p_device
* connect
* disconnect
* crit_protocol_start
* crit_protocol_stop
* update_connect_params
Supported TX frame types:
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
valid interface combinations:
* #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
total <= 3, #channels <= 2
* #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
total <= 4, #channels <= 1
Device supports scan flush.
Device supports randomizing MAC-addr in sched scans.
Supported extended features:
* [ 4WAY_HANDSHAKE_STA_PSK ]: 4-way handshake with PSK in station mode
* [ 4WAY_HANDSHAKE_STA_1X ]: 4-way handshake with 802.1X in station mode
1 Like
Also it's only single stream wifi: 1x1. Could be enough for a wifi station with client needs but not the best choice for an access point.
I've aware of the capabilites but It's mainly for testing. I've used the settings, 5g/36/20 but it still does not work. Client mode works so should not be the country code issue.
Ideas?
wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.path='platform/soc/fe300000.mmcnr/mmc_host/mmc1/mmc1:0001/mmc1:0001:1'
wireless.radio0.country='SE'
wireless.radio0.legacy_rates='0'
wireless.radio0.htmode='HT20'
wireless.radio0.hwmode='11a'
wireless.radio0.channel='36'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.key='xxx'
wireless.default_radio0.mode='ap'
wireless.default_radio0.ssid='KNW19W'
wireless.default_radio0.network='lan'
wireless.default_radio0.encryption='none'
Log files, error codes? I think you should analyze what does not work.
That would make for a fine emergency channel into the device in the double VLAN plus managed switch scenario.
I am getting so tempted to buy one of those and turn it into my primary router. It seems that the A72 cores finally (over-)deliver the promise that "switching from legacy MIPS to present-day ARM" always carried. Need to think a rationale why I need two APs so I can relegate my current routers to APs and justify the rp4b purchase in respect to my own frugality.
In order to be nice to your neighbors, turn the power down and the min modulation rate up, then you'll need a second AP to get full coverage. 
also don't you currently shape your line down to around half it's full speed? This device will double your internet speed at no extra monthly cost 
1 Like
This is normal. What LuCI is saying there is that there is no client connected to your Pi access point. "disabled" is misleading indeed, but no signal here really means there is nothing emitting a signal (that is, nothing that would be considered a connected client).
My travel router with OpenWRT also displays "disabled" when nothing is connected, and the iwinfo is very similar to what you showed; still, clients can connect, and as soon as they do the display changes.
I'm sure you could purchase the license, but it wouldn't help you. The silicon on the Pi 4 still does not contain what you then bought the license for, which means still no hardware acceleration. You could, however, donate the license to the Raspberry Pi Foundation, so that the Pi 5 will have hardware accelerated AES. 
That part of LuCI is wrong. I don't know why they changed to "Disabled".