Kong pro firmware for IPQ806x (R7500, R7800, EA8500, ...)

Community Builds, Projects & Packages
595

I built kmod-usb--serial-ch341 from the main branch but it is not compatible with Kong builds. In retrospect, it is not a surprise as the kernel version is different from the main branch. I saw that Kong had released a new version on Jul 24th, but this kernel module is still not in his repository. I don't know what else to do :worried:

596

Compile his build from source and include the kernel-module.

I just checked you can simply enable it under: kernel modules/USB

I am compiling now, next time I can include building that module :slight_smile:

597

Ah, I need a link to his source. Can you please post a link to it?

Thanks

598

Kongs repo: https://github.com/ricsc/openwrt.git

1 Like
599

A few minutes ago I updated my R7800 from the release 23.05/ipq806x-nss from May 2nd to the release from August 5th.

I would like to use my DDNS alias and the port shares internally as well. To do this, I wrote ifconfig br-lan promisc in rc.local a few years ago.

This no longer seems to be sufficient since the update. Do you have an idea why it doesn't work?

600

I'm having the same issue.

601

I finally got around to compiling the kernel module but I don't know which branch to target. git branch -a output:

  • master
    remotes/origin/HEAD -> origin/master
    remotes/origin/armor-g5
    remotes/origin/kernel5.10-nss-qsdk11.0
    remotes/origin/kernel5.4-nss-qsdk10.0
    remotes/origin/lede-17.01
    remotes/origin/master
    remotes/origin/openwrt-18.06
    remotes/origin/openwrt-19.07
    remotes/origin/openwrt-21.02
    remotes/origin/openwrt-23.05-nss-qsdk11

I am on the 23.05 non-NSS build from Kong. I don't see the non-NSS build here.

602

I have the same problem. Homeserver is not reachable from inside the network with url.

603

@KONG Am I able to install 23.05 NSS build on top of non-NSS build I have currently installed (latest one on your website) and retain all configuration please? Is there a way how to do this properly?

I installed 23.05 non-NSS build from scratch few months back (reset and clean flash) and configured it - nothing complex, all fine but took 2 days for me. Guest network and wireguard/pbr one and few bits and pieces here and there (extender network), works wonderfully, thank you for the n-th time. I would like to retain all my current config on NSS build - but unsure if I have to start from scratch, or if some crucial firewall rules (few custom) or wireguard routing / pbr will 100% work as it is working now. Is reset recommended when going from non-NSS to NSS?

Please advise.

604

You should be able to flash it without a reset and use your existing config.

2 Likes
605

@KONG any solution for @bernipi @boldow and me?

606

I am trying to use NUT to monitor my UPS on latest Kong NSS for R7800. I can install luci-app-nut, but the driver packages like nut-driver-usbhid-ups and key executables like nut-server and nut-monitor are missing. Is it possible to have those packages added?

607

Also nextdns is also not found in the package repo

608

The repo is from Kong's repo....

609

Yes, nextdns and the rest of the nut-driver packages are missing from Kong's repo, so I was wondering if he can add it.

610

If the dependency is not on a missing kernel module/package, you can download the missing ones from OpenWRT 23.05.5 link for your router.

1 Like
611

Running the 2024-10-13 r7800 build, but run into a small but annoying issue:
I do have a port forward (web 80) to an internal server on my network.

entry in the /etc/config/firewall looks like this:

config redirect
        option dest 'lan'
        option target 'DNAT'
        option name 'web'
        option src 'wan'
        option src_dport '80'
        option dest_ip '10.42.43.38'
        list proto 'tcp'
        option family 'ipv4'

My server is visible from the outside world at my dns or external ipv4 address, but when I want to visit my server from my own network with my external ipv4 address or my dns it doesn't work.
I also enabled "promiscuous mode" on my br-lan device. Something I am missing or need to do else?

edit: running
tcpdump -i br-lan
doesn't seem to show anything about enabling promiscuous mode? Does it work in the current build?

Edit2: I did upgrade from another ( ACwifidude) nss build without defaulting my settings. Is it something I should consider?

Edit 3: found that this issue is called "nat loopback" or hairpinning. Didn't find a solution yet.
ip -d link show br-lan gives me promiscuity 1

612

Did you enable Nat Loopback on the Advanced settings tab of the port forward?

Otherwise you van use dnsmasq as a workaround:

address=/my-server-name/internal-ip-address

for OpenWRT:

list address '/my-server-name/internal-ip-address'
1 Like
613

Yes I did enable NAT loopback on the forward. but it doesn't work... The dnsmasq workaround is a bit messy as I have multiple services on different IP's. I might want to try to do a full default of the router and set everything again to see if that helps as the config is pretty old and updated from several openwrt versions.

edit: I did a full factory reset. Setup my internet connection (vlan300 on wan) and made a port forward with "nat loopback". I tried promisc mode on br-lan as well, but also with the default router config it doesn't work.
my (almost default) config backup with forwarding:
https://file.io/hsN805M86gie

Looks like something is broken in the current firmware or I miss something...?

edit 2:

see link above: it looks like it's not generating iptables DNAT configuration:

root@OpenWrtMain:~# iptables -S -t nat
-P PREROUTING ACCEPT
-P INPUT ACCEPT
-P OUTPUT ACCEPT
-P POSTROUTING ACCEPT

614

Unless you are using an outdated build your router is using nft.

nft list ruleset

reflection is both dnat and snat

nft list chain inet fw4 dstnat_lan
nft list chain inet fw4 srcnat_lan
1 Like