No issue here. This is normal. The config is generated by OpenWRT itself.
And here is an example that looks similar to our config: https://openwrt.org/docs/guide-user/base-system/basic-networking. Look for config switch_vlan.
So far so good.
I got QMI working fine (except for the "killall uqmi"-bug).
Edit:
New speed record, not bad considering its about 70km to the nearest proper town.
1 Like
Interesting issue.
Tried to install kmod-tun as a separate package. Built the image like last time, extracted the ipk file and tried to install it.
Collected errors:
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.60-1-3c4be1ed974cca1cfacae30716648d75) for kmod-tun
* pkg_hash_fetch_best_installation_candidate: Packages for kmod-tun found, but incompatible with the architectures configured
* opkg_install_cmd: Cannot install package kmod-tun.
Only way I know around that is to re-flash the entire image 
kmod packages (kernel modules) and kernel version must be compatible. You can not mix versions, not possible. They must always be in sync. So, if you update a kernel then you must also update kmods. And the other way around.
I always just build the whole thing again and sysupgrade. Less painful.
Got new links.
openwrt-alpine-generic-netgear_r9000-squashfs-factory.img
openwrt-alpine-generic-netgear_r9000-squashfs-sysupgrade.bin
They contain the following packages and their dependencies:
MWAN3 & Luci version
OpenVPN-SSL & Luci version
QoS over Nftables & Luci version
UQMI & Luci version
Luci
All of the above are working fine for me. If anyone wants additional packages please say so and ill make a new build.
2 Likes
hurrian
309
I've set up some basic CI for Openwrt R9000 (see: https://github.com/hurrian/openwrt/tree/gh-actions).
Takes a few hours to make a build, but it works.
The only issue is that I'm not sure where we can host our own repository for alpine.
Thank you Kindly for the new links 
So I would like the following if possible
- Dark matter theme
- packages for Samba4 / Network Shares
- irqbalance
- VPN Policing Routing
- VPN Bypass
Just my little request. Thanks for reading and trying to make this possible
If you have the package names I'll make it for you.
Found something interesting.
Not sure if its related to this specific build or if its a general OpenWRT issue. Negative rate is interesting.
I'll make it later on today and post the link here.
1 Like
Done. I have not tested this build.
custom build
So I flashed the sysupgrade file unto of the other previous file you had uploaded and I was not able to access the GUI. So I TFTP the R9000 stock fw and proceeded to use the factory file and I got a message that the file is incorrect. This was all done hardwired to the device.
Edit: So after installing the stock R9000 fw I installed the last new link that was previously been worked on which worked fine then tried to do the sys upgrade to the custom fw and ran into the same issue where I was not able to access the Web GUI to access the routers admin page
No worries, we'll get it sorted out. As long as your u-boot is in working state, nothing can happen.
And OpenWRT doesn't touch it.
So, multiple problems can be involved here.
- We had a bug with FW type where XR700 and R9000 weren't correctly differentiated. This is already fixed on my branch. If you tried to update from an older FW to a recent one, then this problem would appear. sysupgrade will tell that the FW you uploaded is not of the right type. Just force it. Next time it won't happen.
2. Recently we changed switch configuration which is somewhat incompatible with the old one. I mentioned in one of my recent posts here and how to solve it. The problem is the switch configuration is saved and then restored after an update but the new FW uses a different config. Therefore, the switch config must be regenerated.
One solution i would suggest is, just use factory flash via u-boot with IMG OpenWRT file.
This is the easiest way for you probably.
Another solution is to get SSH access to your device AFTER upgrading to the recent FW, remove the old switch config (described in one of my previous posts), and restart.
And third solution would be, flashing stock FW first, and then the latest FW which already has the right switch config. This will override any old OpenWRT configs.
I think there is another solution and easier than previous ones. When you do sysupgrade, you can tell it that the current configuration should not be restored. That would help as well.
-
this works 100%: And third solution would be, flashing stock FW first, and then the latest FW which already has the right switch config. This will override any old OpenWRT configs.
-
I think there is another solution and easier than previous ones. When you do sysupgrade, you can tell it that the current configuration should not be restored. That would help as well.: As far as this by default this option was checked and I left it as is so I will test with it unchecked and report back ...
UPDATE: After unchecking the option to retain current configuration this resulted in the same issue where I was not able to bring up the routers default IP address of 192.168.1.1
1 Like
good to know, thanks for testing, maybe sysupgrade doesn‘t remove everything and keeps some files. need to investigate myself.
One more question. Did you try all LAN ports ? I had the same issue and i managed to restore it with SSH because some ports were still working.
I will say that all the previous sysupgrade files that @NotANewNick uploaded to dropbox worked ... not sure why the custom one he has Kindly made for me does not
As i mentioned, recent FW is incompatible with old switch config and this happens after sysupgrade from an older FW to a recent one.
1 Like
