New OpenWRT - Owner of orphaned IQRouter V2

I have the IQRouter V3 (ZBT-we3526). It wasn't in use and I had reset it a while back. Now it hangs in their initial setup because it can't contact the Evenroute services. Does anyone know of a way to bypass their initial setup, or to flash OpenWRT without having access to their web interface?

EDIT: Answering my own question.

I sent a support question and heard back in a couple hours on a Saturday. For anyone else with this issue, they've created a support FAQ: https://evenroute.zendesk.com/hc/en-us/articles/20863428404500-Help-stuck-in-Initial-Config-post-EoL

I'm sorry to see the IQrouter go. It's been my goto recommendation for non-technical friends with router issues. They've handled a difficult situation very well.

Additional EDIT:

I followed the instructions in the FAQ I liked above, but hung getting to the Advanced menu. Support suggested I go directly to http://192.168.7.1/cgi-bin/luci/admin/system/flash. That worked and I successfully flashed openwrt-23.05.0-ramips-mt7621-zbtlink_zbt-we1326-squashfs-sysupgrade.bin

That's the version they suggested because of a wifi issue in 23.05 for the we3526.

1 Like

I too am saddened by the business being closed down. They did a lot to put the issue of bufferbloat front & center, & to question the marketing of "speed" to counter slowness, when latency under load is arguably a more important metric.

4 Likes

Dang, and I was wanting to get one of these, the IQ Pro 3.
Didn't the IQ Pro 3 have a proprietary interface/firmware that actually mitigated bufferbloat without all the fussing with manual tuning?

Sigh, late to yet another party...

1 Like

The Pro was the same general approach as the V3, except on x86 hardware with no wifi. So yes, automatic self-optimizing with a simple setup, yet all the flexibility of an official OpenWRT build underneath where one could install packages from the same opkg repo a 'normal' openWRT install pulls from.

NOTE: that does mean that packages that depend on kmods that are NOT already present can NOT be installed, as their builds kernel magic version does not match the official repos. Build-time issue, I'd guess.
I ran into this trying to install some packages. So I asked about that, and the next firmware release had a ton more kmods (mostly network and firewall-related) pre-installed.

I will miss those guys; they were my go-to recommendation for all my neighbors and friends. And best of all, excellent support, which meant my friends didn't bug me for help :wink:

I am very impressed with their integrity in shutting down a product dependent on cloud services in a way that did not brick the units but instead gave us a path to continue using the routers.

5 Likes

@jimancona Thanks for pointing this out. I'm in the same boat you were.

One question: the bin file for this is on a USB drive inserted into the router itself, correct? Any special formatting or other files needed on the drive?

There's no USB involved. Download the firmware to your PC then upload it to the router's web interface. The IQrouter upgrade screen seems to be the standard OpenWrt system upgrade.

2 Likes

Hello, another OpenWRT-noob IQRouter owner here (IQRouter Pro / IQrouter-2006 / IQRPV1).

Thank you to everyone that's shared how to upgrade the firmware and how to deal with packages.

Evenroute linked this URL for the Pro boxes (even though there are a few hardware variants, I assume we're all using the same one now):

https://downloads.openwrt.org/releases/22.03.5/targets/x86/64/openwrt-22.03.5-x86-64-generic-ext4-combined.img.gz

//

The IQRouter Pro actually has 273 packages (!), so it'll take some time.

All the packages on my IQRouter Pro that are not in the default firmware selector—a VERY long list

bind-dig
bind-libs
block-mount
bnx2-firmware
ca-certificates
cgi-io
coreutils
coreutils-sort
curl
ddns-scripts
ddns-scripts-cloudflare
ddns-scripts-godaddy
ddns-scripts-services
dnsmasq-full
ethtool
fdisk
fping
fwtool
getdns
getrandom
grub2
grub2-efi
htop
ip-full
iperf
ipset
iptables-mod-ipopt
iptables-nft
iptables-arping
jansson4
jshn
jsonfilter
kernel
kmod-asn1-decoder
kmod-crypto-aead
kmod-crypto-arc4
kmod-crypto-crc32c
kmod-crypto-ecb
kmod-crypto-hash
kmod-crypto-lib-chacha20
kmod-crypto-lib-chacha20poly1305
kmod-crypto-lib-curve25519
kmod-crypto-lib-poly1305
kmod-crypto-manager
kmod-crypto-null
kmod-crypto-sha1
kmod-ebtables
kmod-fs-ext4
kmod-fs-msdos
kmod-gre
kmod-gre6
kmod-hwmon-core
kmod-i2c-algo-bit
kmod-i2c-core
kmod-ifb
kmod-input-core
kmod-ip6-tunnel
kmod-ipt-core
kmod-ipt-ipopt
kmod-ipt-ipset
kmod-ipt-raw
kmod-iptunnel
kmod-iptunnel4
kmod-iptunnel6
kmod-lib-crc-ccitt
kmod-lib-crc16
kmod-lib-crc32c
kmod-lib-textsearch
kmod-libphy
kmod-mdio
kmod-mdio-devres
kmod-mii
kmod-mppe
kmod-nf-conntrack
kmod-nf-conntrack-netlink
kmod-nf-conntrack6
kmod-nf-flow
kmod-nf-ipt
kmod-nf-log
kmod-nf-log6
kmod-nf-nat
kmod-nf-nathelper-extra
kmod-nf-reject
kmod-nf-reject6
kmod-nfnetlink
kmod-nft-compat
kmod-nft-core
kmod-nft-fib
kmod-nft-nat
kmod-nls-base
kmod-nls-cp437
kmod-nls-iso8859-1
kmod-nls-utf8
kmod-phy-realtek
kmod-ppp
kmod-pppoe
kmod-pppox
kmod-pps
kmod-pptp
kmod-ptp
kmod-r8169
kmod-sched-cake
kmod-sched-core
kmod-scsi-core
kmod-sit
kmod-slhc
kmod-tun
kmod-udptunnel4
kmod-udptunnel6
kmod-usb-core
kmod-usb-ohci
kmod-usb-storage
kmod-usb-storage-extras
kmod-wireguard
libatomic1
libblkid1
libblobmsg-json20220515
libbpf20220308
libcap
libcap-ng
libcomerr0
libcurl4
libelf1
libext2fs2
libf2fs6
libfdisk1
libgcc1
libgmp10
libipset13
libiptext-nft0
libiptext0
libiptext6-0
libiwinfo-data
libiwinfo-lua
libiwinfo20210430
libjson-c5
libjson-script20220515
liblua5.1.5 5.1.5-10
liblucihttp-lua
liblucihttp0
liblzo2 2.10-4
libmbedtls12
libmnl0 1.0.5-1
libmount1
libncurses6
libnetfilter-conntrack3
libnettle8
libnfnetlink0
libnftnl11
libnghttp2-14
libnl-tiny1
libopenssl-conf
libopenssl1.1
libpthread
librt
libsmartcols1
libss2
libstdcpp6
libubox20220515
libubus-lua
libubus20220601
libuci-lua
libuci20130104
libuclient20201210
libucode20220812
libustream-wolfssl20201210
libuuid1
libuv1
libwolfssl5.5.4.ee39414e
libxtables12
libyaml 0.2.5-1
lsblk
lua
luci-app-ddns
luci-app-firewall
luci-app-openvpn
luci-app-opkg
luci-app-pbr
luci-app-sqm
luci-app-upnp
luci-app-wireguard
luci-base
luci-compat
luci-lib-base
luci-lib-ip
luci-lib-jsonc
luci-lib-nixio
luci-mod-admin-full
luci-mod-network
luci-mod-status
luci-mod-system
luci-proto-ipv6
luci-proto-ppp
luci-proto-wireguard
luci-theme-bootstrap
mdns-utils
mdnsd
mdnsresponder
miniupnpd-nftables
mtr-json
nano
netperf
openssl-util
openvpn-openssl
openwrt-keyring
pbr
ppp-mod-pptp
r8169-firmware
resolveip
rpcd
rpcd-mod-file
rpcd-mod-iwinfo
rpcd-mod-luci
rpcd-mod-rrdns
sqm-scripts
stubby
tc-tiny
terminfo
ubox
ubus
ubusd
ucode
ucode-mod-fs
ucode-mod-ubus
ucode-mod-uci
uhttpd
uhttpd-mod-ubus
unzip
usign
wireguard-tools
xtables-nft
zlib

//

One curiosity: the IQRouter Pro has replaced some default OpenWRT packages completely. So it is missing some of the default packages and instead uses:

  • dnsmasq replaced with dnsmasq-full
  • libgcc replaced with libgcc1
  • libustream-mbedtls replaced with libustream-wolfssl20201210
  • nftables replaced with nftables-json
  1. dnsmasq-full seems like a safe replacement to use, but will take some digging to see whether we need it.
  2. libgcc1 is one I can't figure out. This 1998 email is beyond my depth. Would anyone have a hint what this might do, versus the default libgcc?
  3. libustream-wolfssl20201210 seems like it was a temporary workaround, but now the mbedtls version should be OK now. I think?
  4. nftables-json again seems to only add features, so it should be safe to add into the default and remove nftables. It could help with SQM flexibility? I'll need to research more.

Apologies; these might be simple questions for the OpenWRT veterans here.

I'm leaning towards just using the firmware selector's choices for easier troubleshooting. I don't think any of the replaced packages above are specific to our hardware.

If you're replacing the OS, why are you trying to make a 1:1 copy ?

1 Like

Ah, that list above is more for posterity's sake—and reference, if anything goes south (e.g., are any of those replaced default packages required for this hardware? Surely not, I'd hope, because Evenroute didn't mention any such requirements in their EOL notice, though Evenroute also didn't mention the sqm package is not included their firmware URLs, even as sqm was the raison d'etre for buying an Evenroute IQRouter).

I will document my progress going through the packages ideally in another post, but if other IQRouter Pro users have taken the leap, I'd love for us to share our experiences here.

As my last sentence alludes to, my choice is not to re-create what Evenroute provided, as they maintained lots of packages and we won't be able to do all that, but it would be good to get a lay of the land so we can more carefully pick and choose.

In the worst case if we miss something, installing a new package onto a production system seems to be safe (though updating packages is not recommended).

The only tricky part are those replaced default packages: that seems like a choice you need to make during the flashing / installation process, so if we miss anything there, I'm thinking it may be tricky to remove & replace those in a production system, so better to make that choice early. But I could be wrong.

We're in for a long ride here of trial and error otherwise to see exactly what packages we are using.

Sometimes the same function can be done by more than 1 software package, for example those few different SSL packages, if the one coming with OpenWrt is working, why do you need to replace it?

1 Like

None of the packages mentioned are hardware-specific. The model 2006 appears to be simply a re-badged generic fanless X86 box. You should be able to completely replace the OS with official OpenWrt and its packages.

1 Like

@fakemanhk Thank you for your reply. Ah, a great point and that makes sense. It was my confusion on what Evenroute was doing, but instead of fully dissecting that (which I had a fun afternoon trying below), I 100% agree OpenWRT's defaults are the way to go.

@mk24 Thank you, as well, for your reply. I appreciate your confirmation; I'm sighing with relief here. For what it's worth, the name of the model 2006 is likely the Qotom Mini PC Q750G5 S08 (OEM link here).

@frollic Thank you, as well, for the great advice pointing me towards the simpler and better solution.

//

Just for my edification, I was curious just which packages & dependencies are in our current Evenroute build. I split it into two categories (neither are 100% accurate; I often only went 2-3 levels deep to save my time):

These account for ~65% of the 270+ packages. The remaining 35% are things I don't expect to use, e.g., mDNS, VPNs, DDNS, ipset, mounting / storage, USB, development, automation, etc. It took a fair amount of Google'ing to figure out what the remaining packages do (and a lot of CTRL+F between NotePad++ windows, haha).

Thus, for me, the current packages (except dnsmasq) listed by the firmware selector for OpenWRT 23:

base-files busybox ca-bundle dropbear e2fsprogs firewall4 fstools grub2-bios-setup kmod-amazon-ena kmod-amd-xgbe kmod-bnx2 kmod-button-hotplug kmod-e1000 kmod-e1000e kmod-forcedeth kmod-fs-vfat kmod-igb kmod-igc kmod-ixgbe kmod-nft-offload kmod-r8169 kmod-tg3 libc libgcc libustream-mbedtls logd luci mkf2fs mtd netifd nftables odhcp6c odhcpd-ipv6only opkg partx-utils ppp ppp-mod-pppoe procd procd-seccomp procd-ujail uci uclient-fetch urandom-seed urngd

plus these custom packages (listed separately purely to make it cleaner on the forum, but will actually be combined above) for the features I use today:

dnsmasq-full stubby luci-app-sqm luci-app-upnp luci-mod-network luci-mod-system luci-mod-status htop

DNS caching & authoritative, DoT, SQM, UPnP, and the current LuCI interfaces we have now, in that order.

My final task is to compare the network monitoring / measuring packages (as Evenroute had a great feature in their pre-EOL builds that had human-readable timestamps of when the WAN connection went down and ran daily speed tests—sadly, all cloud-based). I can't promise I'll find something quite the same, but it's worth a try.

And to get quite familiar with the OpenWRT restore process, just in case. :sweat_smile:

To my pleasant and grateful surprise, and anyone that used Evenroute's basic UI, stubby (DoT / DNS over TLS) can be configured in LuCI (the OpenWRT web GUI interface) as long as you're OK with Cloudflare as your only DNS provider.

Thank you sincerely to everyone in the OpenWRT community, especially those here in this thread. We couldn't have made it this far without your great efforts.

//

I will update soon (1-2 weeks) how the final install goes and maybe turn this post or a follow-up post into a step-by-step guide, for those of us Evenroute customers that might need a helping / close hand at starting from "scratch". I hope that is all right to share in this thread, even as for many OpenWRT veterans in this thread, it will seem really redundant (though OP, please let me know if you're tired of the notifications).

2 Likes