Asuswrt-Merlin on Netgear R7000

Discussion in 'Other Firmware Projects' started by XVortex, Mar 27, 2015.

  1. Frank2

    Frank2 Serious Server Member

    Mak,
    are you running it vanilla and it uses more RAM and CPU? What services are you running?
     
  2. Makaveli

    Makaveli Networkin' Nut Member

    Using Custom scripts.

    AB-Solution
    Pixelserv tls
    Skynet
    AMTM

    Not using
    QOS
    AI Protection
    VPN
     
  3. juched

    juched Reformed Router Member

    Upgraded to 384.5 today. Did an NVRAM reset and manually set everything up again.

    I started noticing "br0: received packet on eth2 with own address as source address" over and over again in the syslog.

    I used nvram set to change the eth0macaddr and others but it still appeared.

    Then I realized that my guest network setup is using the same MAC as my 5ghz network. I disabled the guest wifi and the messages stopped.

    So, I enabled the second guest network (second column, not first) and it uses a number 1 higher than my 5Ghz one.

    Seems there is a bug here... maybe with Merlin build, or maybe here only. Seems Guest network just adds 1 to the MAC for each guest network. This means it will conflict with the 5ghz network which does the same.
     
    phalkon30 likes this.
  4. Terijan01

    Terijan01 Network Newbie Member

    I have to admit this FW version 384.5 is useless. Busybox is completely riped off. Only a few applets left.
    I am a linux guy - I don't need fancy Web GUI.
    You guys make FW useless and then expect some donations...
    I am sorry, but it don't works that way.
    Its time to move to other custom FW that offers serious functionality and flexibility: I don't need this kindergarden ...
     
    Last edited: May 15, 2018 at 9:36 AM
  5. SignedAdam

    SignedAdam Reformed Router Member

    Doesn’t look like you’ve been here long, so I don’t see how you can complain, SSH is much better than telnet, you can do everything you did with telnet, with SSH unless you use some outdated program that uses it, what if telnet can be accessed from the wan, or some random user connecting to your network, I would prefer my router is secure rather than some extra outdated feature
     
  6. Makaveli

    Makaveli Networkin' Nut Member

    This response leads me to believe you don't understand how this process works.

    "You guys make FW useless and then expect some donations..."

    This is a port of merlin's firmware he decides whats features to add and pull from it.

    No one is forcing you to use this.

    To me it sounds like you need build a Linux Firewall/Router from a spare PC then you can customize it to your own liking.
     
    Last edited: May 15, 2018 at 8:03 PM
    SignedAdam and slidermike like this.
  7. miroco

    miroco Reformed Router Member

    A follow up on my findings concerning activation of AiMesh

    Still no groundbreaking news.

    I've probably used and/or tested every 3rd party firmware out there at one time or another on these routers. Adding AiMesh to the mix I came to the conclusion that it was about time to make an nvram erase "mtd-erase2 nvram". As a Mac user, nvram needs (at least needed) to be erased from time to time. After the reset and subsequent fresh reboot, I decided to dump the nvram content "nvram show > nvram.txt" and have look at it.

    These are the things that first attracted my attention.

    There are a couple of mac address oddities going on. First off there is the mac address ranges derived from the addresses on the stickers on the bottom of the routers themselves, E4:F4:C6:XX:YY:ZZ and DC:EF:09:XX:YY:ZZ. Then there are these very similar ranges, E6:F4:C6:XX:YY:ZZ and DE:EF:09:XX:YY:ZZ. The E4:F4:C6:XX:YY:ZZ and DC:EF:09:XX:YY:ZZ ranges occur 9 times, the E6:F4:C6:XX:YY:ZZ and DE:EF:09:XX:YY:ZZ ranges occur 30 times. Except for the second character (4 -> 6) and (C -> E) in the first pair they then follow the same structure. The vendor id of ranges E4:F4:C6:XX:YY:ZZ and DC:EF:09:XX:YY:ZZ is Netgear. The vendor id of ranges E6:F4:C6:XX:YY:ZZ and DE:EF:09:XX:YY:ZZ drew a blank - No Vendor.

    The "wan0_gw_mac=0C:A4:02:XX:YY:ZZ" address is another oddity, since it's a completely different range and identical to both routers and the vendor id show up as "Alcatel Lucient IPD".

    There are also a number of Asus references in nvram, like RT-AC68U (2) and Asus (9). Why that is I don't know, other than the obvious origin of the FW.

    I'm on XVortex custom CFE 1.0.2.2 with Asus mac address scheme.

    http://www.linksysinfo.org/index.ph...lin-on-netgear-r7000.71108/page-6#post-261543

    https://www.snbforums.com/threads/b...ta-is-now-available.46352/page-12#post-403882
     

    Attached Files:

    Last edited: May 16, 2018 at 10:34 AM
  8. jerrm

    jerrm Network Guru Member

    deleted. error.
     
  9. SignedAdam

    SignedAdam Reformed Router Member

    Success! GT-AC5300 and R7000 in AiMesh

    :D:D:D:D:D:D:D
     
    Last edited: May 16, 2018 at 4:12 PM
    Almighty1, kalpik and slidermike like this.
  10. miroco

    miroco Reformed Router Member

    SignedAdam likes this.
  11. SignedAdam

    SignedAdam Reformed Router Member

    AiMesh Beta Guide 1.0

    * Some images in this guide may not show up till you login

    GT-AC5300 Firmware Version : 3.0.0.4.384_20648
    R7000 Firmware Version : 384.5
    R7000 Bootloader (CFE) 1.0.2.1 HW acceleration - Enabled (CTF only)

    1st of all we need to make sure the R7000 is at 100% stock settings
    I like to do this by holding the reset button at the back for 15 seconds, letting go and after the lights go out press and hold the last button on the R7000 (WPS button) then let go

    tell windows to forget the NETGEAR_5G and or NETGEAR network, so it doesnt reconnect,
    next connect to your Asus router by ethernet or wifi, ethernet is highly recommended as the AiMesh is highly unstable too begin with

    [​IMG]

    go to the asus router login page :
    192.168.1.1
    or router.asus.com
    or whatever yours is

    go to Advanced - Wireless - General

    * Make sure Smart connect is disabled/OFF

    * Make sure all 3 bands / SSID's have their own name, "Example_60_2G Example_60_5G Example_60_5G_Gaming"

    - Where Example is, replace with SSID name

    * Use WPA2-Personal as Authentication Method

    * go to WPS and make sure this is enabled (I don't like that you have to have this enabled as it's a security risk, but this is how asus has made it) - 100% required

    ALL * are required
    ALL - are Optional

    [​IMG]


    [​IMG]

    next go to the networking map, and press the AiMesh Node button
    next press scan

    [​IMG]

    press the R7000 that should appear!

    [​IMG]

    next press apply

    [​IMG]

    then r7000 should receive the WPS code and reboot at 2 to 5%

    [​IMG]

    then r7000 will reboot again 35% (I believe it receives what the network SSID names are plus what channel they are on and so on)

    45reboot.PNG

    then on the second start up, the R7000 should stay on, no more reboots!
    press the ok button on successfully added R7000 (if you now go to Wireless - WPS) you should see a success message and 192.168.1.96 should redirect you to your routers logon page

    added.PNG

    Like I said near the beginning, to start with the connection to your network, will be unsable for the 1st few minutes

    addedbutwait.PNG

    if your R7000 is rebooting again and again this means your wifi settings are wrong on the AiMesh ASUS Router, (DO NOT USE SMART CONNECT)
    if your R7000 is rebooting repeatedly turn it off, press and hold the last button on the r7000 (WPS button, till the power light flashs orange, then let go) remove the R7000 from the AiMesh ASUS Router and try again

    192.168.1.96/Main_Login.asp is the same login as the asus router but redirects every time you login... joy, so no logs

    redrirect.PNG

    Heres the logs on the ASUS Router :

    Code:
    May 16 15:26:37 rc_service: cfg_server 1021:notify_rc start_wps_method
    May 16 15:27:41 kernel: wfd_registerdevice Successfully registered dev wds0.0.12 ifidx 1 wfd_idx 0
    May 16 15:27:41 kernel: Register interface [wds0.0.12]  MAC: b1:XX:XX:XX:XX:XX
    May 16 15:27:42 roamast: eth6: add client [C1:XX:XX:XX:XX:XX] to monitor list
    May 16 15:28:04 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
    May 16 15:28:47 kernel: wfd_registerdevice Successfully registered dev wds0.0.12 ifidx 1 wfd_idx 0
    May 16 15:28:47 kernel: Register interface [wds0.0.12]  MAC: b1:XX:XX:XX:XX:XX
    May 16 15:28:47 roamast: eth6: add client [C1:XX:XX:XX:XX:XX] to monitor list
    May 16 15:28:49 kernel: wfd_registerdevice Successfully registered dev wds2.0.1 ifidx 1 wfd_idx 2
    May 16 15:28:49 kernel: Register interface [wds2.0.1]  MAC: b0:xx:xx:xx:xx:xx
    May 16 15:28:53 roamast: eth8: add client [c4:xx:xx:xx:xx:xx] to monitor list
    May 16 15:29:56 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -50dbm) for weak signal strength client [7A:XX:XX:XX:XX:XX](rssi: -56dbm)
    May 16 15:29:56 roamast: eth6: disconnect weak signal strength station [7A:XX:XX:XX:XX:XX]
    May 16 15:29:56 roamast: eth6: remove client [7A:XX:XX:XX:XX:XX] from monitor list
    May 16 15:30:06 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -49dbm) for weak signal strength client [DC:XX:XX:XX:XX:XX](rssi: -62dbm)
    May 16 15:30:06 roamast: eth6: disconnect weak signal strength station [dc:xx:xx:xx:xx:xx]
    May 16 15:30:06 roamast: eth6: remove client [dc:xx:xx:xx:xx:xx] from monitor list
    May 16 15:40:46 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -56dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -60dbm)
    May 16 15:40:46 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:42:26 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -56dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -63dbm)
    May 16 15:42:26 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:42:36 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -55dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -62dbm)
    May 16 15:42:36 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:43:21 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -60dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -64dbm)
    May 16 15:43:21 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:43:46 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -56dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -60dbm)
    May 16 15:43:46 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:44:11 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -55dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -61dbm)
    May 16 15:44:11 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:45:36 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -55dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -60dbm)
    May 16 15:45:36 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:46:46 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -60dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -68dbm)
    May 16 15:46:46 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:46:51 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -62dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -67dbm)
    May 16 15:46:51 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:55:51 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -60dbm) for weak signal strength client [09:XX:XX:XX:XX:XX](rssi: -64dbm)
    May 16 15:55:51 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:56:21 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -55dbm) for weak signal strength client [09:XX:XX:XX:XX:XX](rssi: -65dbm)
    May 16 15:56:21 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:58:26 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -58dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -68dbm)
    May 16 15:58:26 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
    May 16 15:58:36 roamast: discover candidate node [C1:XX:XX:XX:XX:XX](rssi: -59dbm) for weak signal strength client [A9:XX:XX:XX:XX:XX](rssi: -65dbm)
    May 16 15:58:36 roamast: roaming reject!!! candidate rssi over threshold(-55dbm)
     
    Last edited: May 18, 2018 at 6:42 PM
  12. SignedAdam

    SignedAdam Reformed Router Member

    Errr! also later today :cool:

    IMG_0617.JPG IMG_0619.JPG IMG_0620.JPG IMG_0621.JPG burnin.PNG

    Just because! well! I can :cool:
    if you guys think your b@lls are as big as mine, follow this guide :
    https://www.dd-wrt.com/phpBB2/viewtopic.php?t=278827
    I used Xr-m from http://www.osco.uk.com/products/thermal-materialon on my R7000, free sample of 1mm and 2mm, very kind of them even though they have stopped giving out free samples now
    I'm sure it gos without saying
    AT YOUR OWN RISK!
    but I did see temps drop by 12c

    As you can see I ran the R7000 up to 100% with some Linux commands in BASH, after and even did a little 400mhz OC, which I will be dropping back to stock, you can see I ran it so hard in to the ground, the main page couldn't load, maha! its alive
     
    Last edited: May 19, 2018 at 6:32 PM
    slidermike and Makaveli like this.
  13. Makaveli

    Makaveli Networkin' Nut Member

    That is a nice drop in temps.

    I however prefer a laptop cooling pad less work and I get lower temps :)

    Clocked at 1.2Ghz 24/7

    I may still consider doing that on a day I'm bored.

    [​IMG]

    Stock Temps @ 1Ghz


    [​IMG]

    Cooling Pad @ 1.2Ghz

    [​IMG]
     
    Last edited: May 17, 2018 at 1:11 AM
    Onee-chan, slidermike and SignedAdam like this.
  14. Onee-chan

    Onee-chan Network Newbie Member

    [​IMG]
     
    SignedAdam likes this.
  15. SignedAdam

    SignedAdam Reformed Router Member

    if im honest, the firmware @XVortex and his friend has made (xwrt firmware), for the R7000 seems to be less glitchy than the ASUS router firmware! on the GT-AC5300 :eek: THAT ASUS THEM SELFS MADE!
     
    Last edited: May 17, 2018 at 9:42 PM
  16. pege63

    pege63 Reformed Router Member

    I have tried 10 times now to update the router with the latest 384.5_0, but without any luck.
    I have restet the router before update, i have get back to stock, Tried 5 different browsers, have tried 4 live CD and Linux live CD, but no luck. I have manage do upload the file but after reboot i says the same firmware as before flash. And yes i have Cleared the browser cache, i need suggestions to mange it and to make it happend!?
     
  17. Terijan01

    Terijan01 Network Newbie Member

    I assume you have corrupted settings that do not allows you to upgrade.
    Try this: install XWRT 384.5_0 from stock FW (V1.0.9.26_10.2.31).

    *after you install stock FW (V1.0.9.26_10.2.31) - you will bump into this issue directly and you will be forced to fix it.
     
  18. pege63

    pege63 Reformed Router Member

    I manage it now i went back to 380.66 after that i update to 380.70 then to 384.5_0 and success.
     
  19. Makaveli

    Makaveli Networkin' Nut Member

    Merlin's firmware is better than stock asus so I 100% agree with you here.
     
    SignedAdam likes this.
  20. GDT78

    GDT78 Serious Server Member

    I overclocked @1.2Ghz too but I haven't so high temperature, I got around 64°C without doing anything like cooling pads or replacing thermal compound.
     
  21. Makaveli

    Makaveli Networkin' Nut Member

    Remember with temps location and ambient temps are important.

    When I took the stock screenshot the router was in a room with no AC and it was Summer.

    Comparing temps can be apple vs oranges without the rest of the information.
     
    Last edited: May 17, 2018 at 7:29 PM
    SignedAdam likes this.
  22. SignedAdam

    SignedAdam Reformed Router Member

    Right i've pretty much tried everything but "Factory defaulting" the GT-AC5300, I've tried disabling the "Example_60_5G_Gaming" and then adding the R7000 AiMesh Node, however after adding the R7000 AiMesh Node I see a "Example_60_5G_Gaming" appear, which is the Node, ive tried it all again but hiding the "Example_60_5G_Gaming" but the same thing happens time and time again, why would anyone want the SSID for their "Example_60_5G_Gaming" broadcasted by their Node, ping times are higher as its got A-MAN-IN-THE-MIDDLE :rolleyes:

    So I need help guys, how do I just have "Example_60_2G and Example_60_5G" rebroadcasted instead of "Example_60_2G and Example_60_5G_Gaming" :mad: Their doesn't seem to be any options offering what SSID's to rebroadcast,

    * The reason why i'm going on about Factory defaulting the GT-AC5300 is because when I 1st added the R7000 AiMesh Node, it did do just that, it rebroadcasted "Example_60_2G and Example_60_5G", now either im going cr@zy and it didn't happen or ASUS buggy firmware on the GT-AC5300 is driving me Cr@zy

    This is how buggy the GT-AC5300 is :

    devices not showing on whos connected to the GT-AC5300 and just showing a few, if you enable game boost (QOS) and choose what devices are prioritised the log files show lots of errors and the GT-AC5300 LOCKS UP, you press the reboot button and nothing happens, you even hold the reset button AT the back of it, the light flashs, then gos out but the router stays on! I love the hardware of the GT-AC5300 along with the pretty red UI, but its not fit for purpose from what ive seen, I'm thinking about pulling the R7000 down from the roof, and sending it back lol, that's how bad it is, its been out for 6 months... :mad: and has bugs like this in it
    Here's the error message from the RT-AC5300 when QOS is on in game boost mode and you prioritise one device, (even pressing apply after dragging the red on to a device, has a problem, after pressing apple, the UI stops, nothing loads, then after 20 seconds things come back to life) the logs just go on forever, never ending like this, try finding a log in endless this
    Code:
    May 17 21:17:21 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
    May 17 21:17:21 kernel: ioctl_iqos_op_config() fail!
    May 17 21:17:21 kernel: ERR[qos_start:3350] qos_conf is not already!
    May 17 21:17:21 kernel: ioctl_iqos_op_switch(1) fail!
    May 17 21:17:24 kernel: ERR[__parse_app_rule:575] Failed to parse app rule catid value
    May 17 21:17:24 kernel: ERR[parse_qos_conf:1038] Invalid config syntax at line 22.
    May 17 21:17:24 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
    May 17 21:17:24 kernel: ioctl_iqos_op_config() fail!
    May 17 21:17:24 kernel: ERR[qos_start:3350] qos_conf is not already!
    May 17 21:17:24 kernel: ioctl_iqos_op_switch(1) fail!
    May 17 21:17:27 kernel: ERR[__parse_app_rule:575] Failed to parse app rule catid value
    May 17 21:17:27 kernel: ERR[parse_qos_conf:1038] Invalid config syntax at line 22.
    May 17 21:17:27 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
    May 17 21:17:27 kernel: ioctl_iqos_op_config() fail!
    May 17 21:17:27 kernel: ERR[qos_start:3350] qos_conf is not already!
    May 17 21:17:27 kernel: ioctl_iqos_op_switch(1) fail!
    May 17 21:17:30 kernel: ERR[__parse_app_rule:575] Failed to parse app rule catid value
    May 17 21:17:30 kernel: ERR[parse_qos_conf:1038] Invalid config syntax at line 22.
    May 17 21:17:30 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
    May 17 21:17:30 kernel: ioctl_iqos_op_config() fail!
    May 17 21:17:30 kernel: ERR[qos_start:3350] qos_conf is not already!
    May 17 21:17:30 kernel: ioctl_iqos_op_switch(1) fail!
     
    Last edited: May 17, 2018 at 9:47 PM
  23. SignedAdam

    SignedAdam Reformed Router Member

    Update AiMesh Beta Guide 2.0 didn't work so the Guilde is back to 1.0

    my solution, didn't work :

    Once WPS is turned off, a special connection between the AiMesh Asus router and the AiMesh R7000 node is lost, and not even turning it back on will fix the issues that come with turning it off, for some reason, the AiMesh ASUS Router can not update the AiMesh R7000 Node with what channel it need to work on, it also doesnt help that the R7000 AiMesh Node, keeps dropping the connection for all devices on it, my guess is, this is what it does when it thinks your in range of the AiMesh ASUS router, :rolleyes: however after turning off the WPS it seems to want to disconnect all devices permanently, like i said not even turning it back on can bring back the connection it had, you have to remove it from your network, and then add it back again!!

    hopefully ASUS will update the AiMesh system with the ability to choose what band you want to rebroadcast
     
    Last edited: May 18, 2018 at 6:57 PM
  24. slidermike

    slidermike Addicted to LI Member

    I wish you luck SA.
    We have seen in the past that features you might expect to work dont and getting a timely fix from Asus is hit/miss. Take traditional QoS as an example.
    It has been broken and known to be broken for at least a year if not longer. It was just fixed or at least reported as fixed in the latest release.

    Would be nice to have all or at least the big features working.
     
    SignedAdam and Makaveli like this.
  25. miroco

    miroco Reformed Router Member

    The functionality "Smart Connect" probably plays an important role in combination with AiMesh, but there is no mentioning of it in the Asus AiMesh setup guide. A test of AiMesh carried out by Singapore Hardware Zone involved "Smart Connect". They activated "Smart Connect" at the outset of their test, letting the routers manage themselves. The complexity of a dynamic environment like wireless, has everything to gain from an autonomous management. Wireless is unpredictable as it is. With AiMesh the complexity takes an exponential leap. Wireless is like the weather, the difference with wireless is that it sometimes also "rain" indoors. Maybe "Smart Connect" is the secret sauce to AiMesh (or WDS take 2).

    Asuswrt-Merlin unfortunately lack the "Smart Connect" feature on the RT-AC68U and consequently so does Xwrt-Vortex. With the R7000, it seems unlikely that it should assume the central managing role of the AiMesh router without "Smart Connect". A node, yes, but pair it with what? "Just like it's not advised going back and forth between Asuswrt-Merlin and Asuswrt without a factory default reset, having an Asuswrt-Merlin router trying to access and modify settings to a non-Asuswrt-Merlin firmware will lead to problems."* There's a request over at SNB petitioning "Smart Connect" for the Asus AC1900 range routers. Maybe XVortex could backport "Smart Connect" to Xwrt-Vortex?

    https://images-na.ssl-images-amazon.com/images/I/A1kBHyTa5TL.pdf
    https://www.hardwarezone.com.sg/fea...networking-feature/performance-final-thoughts
    https://www.snbforums.com/threads/smart-connect.44733/
    https://www.snbforums.com/threads/rt-ac68u-rt-ac68p-rt-ac1900-rt-ac1900p.35759/
    * https://www.snbforums.com/threads/b...ta-is-now-available.46352/page-12#post-403882
     
    SignedAdam likes this.
  26. SignedAdam

    SignedAdam Reformed Router Member

    @miroco - AiMesh works fine as long as you keep WDS on, as soon as you switch it off, problems come, like it wanting to kick devices off the node all the time

    Agreed, smart connect on the R7000 might give better compatibility with AiMesh, the problem is, that smart connect is a extra feature, meaning not only does it need to be integrated in to the router mode of R7000 but the AiMesh mode as well, I should think the AiMesh mode would need more work than the router side, because it’s so different

    Did you get it to work between two R7000 ?
     
  27. SignedAdam

    SignedAdam Reformed Router Member

    :D Just been on the phone with Netgear, doesn't look like mesh networking support will be coming to the R7000 which should make this firmware famous, it's obvious that the R7000 can do it, it's just the matter of netgear letting it do that, which would lose them money as they want you to buy their new mesh routers, so looks like my stay on XWRT is going to be a long one after all @XVortex :cool: and ASUS,
     
    Last edited: May 19, 2018 at 5:34 PM
    Makaveli likes this.
  28. miroco

    miroco Reformed Router Member

    @SignedAdam

    No, unfortunately not.

    Presently I've run out of ideas.

    In the beginning of the process the WPS-led flashes rapidly on both router for a few seconds. The at 7 % the node reboots. At about 26 % the node is back up again and the process seems to continue. When the progress indicator reaches 60 %, the process fails. It completes 100 % very quickly and a splashscreen appear: "Unable to add AiMesh node R7000 (DC:EF:09:XX:YY:ZZ) to your AiMesh system because of following situations. Please check and try it again." Att the same time the node reboots.
     
    SignedAdam likes this.
  29. SignedAdam

    SignedAdam Reformed Router Member

    @miroco - I would try changing some of the wifi settings, turning things on and off like i did with smart connect
     
  30. miroco

    miroco Reformed Router Member

    @SignedAdam

    The setup fail even the bare minimum settings. After a reset I leave the node as it is, on without any configuration what so ever. I do the same thing with router, with the following exceptions: choosing router as the operation mode, configuring the WiFi settings, entering a username and password. Just to satisfy the setup guide basically and finally I enable AiMesh (Tools -> Other Settings). As far as I can tell, all is then set to initiate the AiMesh configuration.

    I forgot to mention that I tried the setup with the 5 GHz radio disabled. I also increased the distance between the units, to about 4 times the recommended distance. They all failed and as far as I can tell, they failed for the same reason as with all the other attempts.

    I found this list of observations compiled by a user over at the SNB-forum. I thought it might give you some ideas as his hardware setup is similar to yours.

    https://www.snbforums.com/threads/my-bucket-list-suggestions-observations-for-aimesh.45438/

    XVortex mentioned two ways of enabling AiMesh. One is through the settings (Tools -> Other Settings) and the other is via nvram directly. My thought was that that nvram setting could perhaps work even on Asuswrt-Merlin. If so, your GT-AC5300 and your R7000 could potentially be running Merlin firmware with AiMesh enabled. Anyway, it's just a thought.
     

    Attached Files:

    SignedAdam likes this.
  31. SignedAdam

    SignedAdam Reformed Router Member

    @miroco - I don't believe enabling AiMesh in (Tools -> Other Settings) Asus features, ever worked for me, just restore the R7000 to default settings, dont connect to it, dont do anything to it, leave it as is, then on the other device seach for AiMesh devices and it should find it

    * Ill do some more testing my end but I think, if you press enable in (Tools -> Other Settings) Asus features, it will fail everytime, it failed for me when testing that route, i might be wrong so ill do some more testing taking that route, from my experience you just need to restore the thing to default settings and it 100% works from that point on wards
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice