Recent content by pro_info

We come back to the initial problem ^^ because I had launched the command after having compiled the firmware :/

Ok so, I looked at the makefiles, especially the one in the linux-4.1 directory, to see the available options and indeed I have a modules_prepare argument. The problem of this one is that it doesn't reload the .config file so it asks me to redefine a whole bunch of global.

It's possible, but as I compile the firmware just before, I suppose that the "make modules" is done before, no? And in the cross compilation command I have: SUBDIRS=`pwd` modules I wanted to try again, but no way to recompile it tonight... As for the toolchains, I go through the docker image...

:D The goal is to have a second 2.5/5Gbe port connected to USB to have one on the WAN side (Internet) and one on the LAN side (NAS). Like what was done on this post but without installing the drivers which caused stability problems: Added 2.5gb WAN port to AX86U loaded with RMerlin’s FW |...

Hello all, I am trying to compile two drivers for my XT8 which are the aqc111 at first and then the r815. After a day of hard work, I manage to compile the rt-ax95q firmware without any problem on docker, but I get errors when I try to compile the driver (on docker or not). I was inspired by...

I received an email yesterday from the support team that seems to be responsible for the development, relayed by a member of the technical support team, asking me for some confirmations. I hope it will be successful, they seem to have understood the problem, it is already good news.

@ASUSWRT_2020 Thanks for this update. Too bad that on XT8, static routing on the node always poses a problem in wireless :( The report of the bug to Asus seems to progress :) https://www.snbforums.com/threads/firmware-bug-static-route-no-working-on-node-xt8-wireless-backhaul-only.67795/#post-634206

I received a response from technical support who fully understood the problem. I send them the syslog and cfg. I will keep you informed.

I will make a report to Asus and find an alternative operation, in the meantime, through another wifi router to receive the backhault and thus, define my node with an ethernet backhaul. Yes, me too it puts me addresses in .188 for the node. It is enough to assign in the DHCP of the Router XT8 a...

Am I the only one to have a static routing problem on the mesh node when the backhaul is wifi? When the backhaul is wired, the static routing is fine. Here is a post detailing the tests performed. @ASUSWRT_2020 https://www.snbforums.com/threads/static-route-xt8-node-problem.67795/ I'm thinking...

When the backhaul is in ethernet, everything works perfectly with PC2 (wired or wireless) whether I'm on the XT8 router or the node. I come to the conclusion that it's a bug in the firmware. I tried with firmware 3.0.0.4.386.25524, 3.0.0.4.386.25790, 9.0.0.4.386_40947. The problem is the same...

When I connect a PC2 to the Node XT8 with cable, I have all the accesses, it's obviously only in wifi on the Node XT8 that it doesn't work apparently...

Hi guys, I have just acquired a pack of 2 Asus XT8. I have a big problem with a network configuration like this one: PC1 can access in SSH, to the web interface of Router 2 (with address 10.0.0.20 or 10.0.1.1) and VMs on the server. But PC2 can only access at address 10.0.0.20 (web only!) but...