Building an OpenWrt product? Don't overlook board-level support.
The Wallys DR5018S, based on Qualcomm IPQ5018, is now supported upstream in OpenWrt.
GitHub: github.com/openwrt/openwrt/commit/0dd6f3b28353f71…
#OpenWrt #EmbeddedLinux
DR5018S (IPQ5018): OpenWrt mainline support
• Tri-band Wi-Fi 6E: 2.4/5/6 GHz
• Review the upstream change: openwrt#24910
• Datasheet: wallystech.com
linda@wallystech.com
#OpenWrt #IPQ5018 t.co
8 views
tp-linkのは、mediatekのこれとか
openwrt/target/linux/mediatek/filogic/base-files/lib/preinit/09_mount_cfg_part at main · openwrt/openwrt github.com/openwrt/openwrt/blob/main/target/linux…
2 likes · 110 views
DR5018S support is now in OpenWrt main
DR5018S support has been merged into OpenWrt main. PR #24910 documents an IPQ5018 tri-band Wi-Fi 6E board and tests across boot, NAND upgrade, Ethernet and 2.4/5/6 GHz AP interfaces. openwrt#24910 #OpenWrt #WiFi6E t.co
9 views
openwrt#19142
hs20_oper_friendly_name って hostapd から消えてたのか・・・
2 likes · 67 views
Huawei HG658c V2 Router's PCB code "AMOHG658V2M VER. B" UART points
Huawei HG658c V2 ; S/N: 3KH7S17105008884 20 ; motherboard PCB code "AMOHG658V2M VER. B,“ purchased from Vodafone ; HiSilicon SD5116 (HiSilicon Hi5610 family) Dual-Core ARM Cortex-A9 MPCore ARMv7-A (32-bit) 800 MHz – 1.0 GHz range (with dynamic frequency scaling support) MCU/SoC ; Router.
Details: openwrt#25771
I'm sharing this in case it might be useful to someone else.
6 points
OpenWrtマージチャレンジ、最難関だった11k shared driverのPR通った！あとはLN6001のath11k, 12kのコンフィグ登録できたら完成！
openwrt#25595
1 like · 21 views
Posting because OpenWRT, possibly others as well, assign .lan names to devices on the LAN by default. People who make use of this might want to follow the application, and, if it goes through, either change the name or make sure queries can't get incorrectly get sent to upstream resolvers.
Regarding that last point, I've had issues with dnsmasq in the past where it was remotely resolving domains even when they were configured to resolve locally. For .lan domains, this could be disastrous because I often send plaintext traffic to them. I did submit a fix/workaround[0], but it's still something to look out for. If anyone knows more about this issue or other ways queries could leak, please share!
[0]: openwrt#18610
Mentions
Building an OpenWrt product? Don't overlook board-level support. The Wallys DR5018S, based on Qualcomm IPQ5018, is now supported upstream in OpenWrt. GitHub: github.com/openwrt/openwrt/commit/0dd6f3b28353f71… #OpenWrt #EmbeddedLinux
DR5018S (IPQ5018): OpenWrt mainline support • Tri-band Wi-Fi 6E: 2.4/5/6 GHz • Review the upstream change: openwrt#24910 • Datasheet: wallystech.com linda@wallystech.com #OpenWrt #IPQ5018 t.co
tp-linkのは、mediatekのこれとか openwrt/target/linux/mediatek/filogic/base-files/lib/preinit/09_mount_cfg_part at main · openwrt/openwrt github.com/openwrt/openwrt/blob/main/target/linux…
DR5018S support is now in OpenWrt main DR5018S support has been merged into OpenWrt main. PR #24910 documents an IPQ5018 tri-band Wi-Fi 6E board and tests across boot, NAND upgrade, Ethernet and 2.4/5/6 GHz AP interfaces. openwrt#24910 #OpenWrt #WiFi6E t.co
openwrt#19142 hs20_oper_friendly_name って hostapd から消えてたのか・・・
Huawei HG658c V2 Router's PCB code "AMOHG658V2M VER. B" UART points Huawei HG658c V2 ; S/N: 3KH7S17105008884 20 ; motherboard PCB code "AMOHG658V2M VER. B,“ purchased from Vodafone ; HiSilicon SD5116 (HiSilicon Hi5610 family) Dual-Core ARM Cortex-A9 MPCore ARMv7-A (32-bit) 800 MHz – 1.0 GHz range (with dynamic frequency scaling support) MCU/SoC ; Router. Details: openwrt#25771 I'm sharing this in case it might be useful to someone else.
OpenWrtマージチャレンジ、最難関だった11k shared driverのPR通った！あとはLN6001のath11k, 12kのコンフィグ登録できたら完成！ openwrt#25595
Posting because OpenWRT, possibly others as well, assign .lan names to devices on the LAN by default. People who make use of this might want to follow the application, and, if it goes through, either change the name or make sure queries can't get incorrectly get sent to upstream resolvers. Regarding that last point, I've had issues with dnsmasq in the past where it was remotely resolving domains even when they were configured to resolve locally. For .lan domains, this could be disastrous because I often send plaintext traffic to them. I did submit a fix/workaround[0], but it's still something to look out for. If anyone knows more about this issue or other ways queries could leak, please share! [0]: openwrt#18610