Asuswrt-Merlin on Netgear R7000

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

  1. qamartheone

    qamartheone Serious Server Member

    can someone tell/guide me in going back to stock netgear firmware from latest ng build of xvortex..heard few ppl were brickin their r7000 in doin so?
     
  2. Alex Ng

    Alex Ng New Member Member

    Hi there. Complete noobie here. Just wanted to check whether I can flash to the latest build of xvortex directly from any version of netgear stock firmware (i'm currently running V1.0.9.34_10.2.36).
    Also, if I'm going directly to the NG builds, do I have to flash 380.70 first or can I flash from stock to the latest as per the instructions?
    I'm wanting to try xvortex mainly because of the option for usb modem which stock firmware doesn't offer. Can anyone comment about the usability of this function?
    Thanks in advance.
     
  3. thernus

    thernus New Member Member

    I have found there are some issues with USB modems and XWRT (on both r7000 and r8000 routers where the modems worked fine on my old RT-88U) or at least XWRT doesn't like the USB modems I have for some reason (Netgear ac320u/ac790s/ac800s)

    If any of the above modems are set to the primary WAN (and only WAN) most of the time when the router reboots, it resets the router to factory defaults which is pretty crazy, I found a post on page 46 with a person with the same issue but different modem.

    A work around I have found is to just turn on Dual-WAN and have wired WAN the primary and USB modem as secondary and let it fail over to the secondary (only one plugged in) it just delays the bootup/wan connection a extra 30 seconds or so.
     
  4. Daniel Cronan

    Daniel Cronan New Member Member

    Greetings! Using the newest 384.8_2 build. Routing rules and a few other things on the VPN Client page have to be re-entered every time I upload a new server, and also DNS servers in WAN have to be re-entered every time I upload a new server. Is this the new going thing? All of that information stuck on the 380 versions. Noticed it by doing a leak test shortly after upgrading; it showed DNS leaks. Corrected it by again entering my VPN DNS server information, which I had already entered in the boxes the day before and saved.

    EDIT: Fixed. Went back to last 380 build. Everything is great again. Not having to re-add DNS servers, re-do routing rules, and re-check the blocked clients option every time I change VPN servers.
     
    Last edited: Dec 22, 2018
  5. OldSkulRide

    OldSkulRide Serious Server Member

    Guys, does Huawei E3372 work on r7000 and xvortex firmware as fallback device for internet in case cable goes down? I have option to get it cheap.
     
  6. Stimpy88

    Stimpy88 Reformed Router Member

    Have a great Christmas everyone
     
    phalkon30, Makaveli, KingP1n and 2 others like this.
  7. KingP1n

    KingP1n Connected Client Member

    2019 will bring many great fw updates for our beloved R7000..thanks to XVortex and RMerlin. Merry Christmas to all and the community here.
     
    XVortex, Stimpy88 and Ubimoo like this.
  8. buggage

    buggage Network Guru Member

    Hi,

    Just picked up an R7000 the other day due to seeing the compatibility list with other firmware, however none of the .chk files are being accepted to upgrade to.

    Initial R7000 firmware: V1.0.9.34_10.2.36

    File: R7000_384.8_2.chk (and others).

    Error: Goes to the flashing page for about 2 sec and then "The firmware is not compatible with your router. Error code -2." I had seen in this thread talk about. Have never tried upgrading prior on this device. Did see there have been some issues trying to go back to stock, but I can't even get out of stock...Did Netgear change something where this no longer works? Thanks.
     
  9. Frank2

    Frank2 Networkin' Nut Member

    Page 1 of this forum shows you how to do it.
    It appears you are trying to install a 384NG FW build before you install 380.

    When coming from 380 to 384/NG You MUST flash the 380.70 build first.

    It's all explained on page 1, 1st post.
     
  10. buggage

    buggage Network Guru Member

    Thanks, but that does not work either. The R7000_380.70_0.chk also give the same incompatible error and will not upload. That's why I'm thinking something else is going on.
     
  11. slidermike

    slidermike Addicted to LI Member

    I dont "know" this but Asus started locking down the stock firmware after a certain revision so you have to back-rev the stock to the last unlocked ver. Then do whatever you needed to. Could be that Netgear is following suit though I have no knowledge of this. Just a possibility.
     
  12. Frank2

    Frank2 Networkin' Nut Member

    Hmmmmm, not sure then. Will have to wait for one of the gurus to chime in. I've reached the limits of my technical expertise. Sorry.
     
  13. buggage

    buggage Network Guru Member

    I guess I might be somewhat screwed. Did a few other searches and found a couple of other references to the same where it looks like the only way some others were able to change the firmware was with a serial connection and access to the CFE... Hoping that's not exactly the case, but not looking like there's much I can do in the meantime. I can't even revert to previous Netgear firmware versions.
     
  14. ollimö

    ollimö Serious Server Member

    Did you alkso try the .trx files or just the .chk? .chk does not work for me either since some time but .trx has done the trick past releases. Good luck!
     
  15. buggage

    buggage Network Guru Member

    Thanks for the replies. I was able to successfully flash it this morning (with the .chk file), but found another suggestion to try the nmrpflash utility here: https://github.com/jclehner/nmrpflash

    I had tried a few other TFTP methods that did not work, this one did. Had a minor scare when the device just went into a boot loop after the firmware was loaded, but I just had to factory reset it and it's all good now!
     
    Last edited: Dec 27, 2018
    Stimpy88 likes this.
  16. chert1024

    chert1024 New Member Member

    Does adaptive QOS work with this latest firmware? I went back to stock since the 3 previous firmware I tried didn't have it functioning. I have 15 to 20 devices in my network with a 100/100 fiber connection and that's why having a good functioning auto QOS is important to me.
     
  17. Daedelus

    Daedelus Network Guru Member

    I'm pretty sure the definition of the WiFi 5GHz MAC on my unit is wrong but not sure why or how to cure it.

    On my unit 5GHz MAC = 2.4GHz MAC + 1 this results in the same (conflicting) MAC for 2.4GHz Guest1 and 5GHz (E6:F4:C6:XX:XX:82)

    This results in being unable to use the 5GHz band if the 2.4GHz Guest1 is enabled.

    I expected 2.4GHz to be E4:F4:C6:XX:XX:81 & 5GHz to be E4:F4:C6:XX:XX:85.
    i.e. 5GHz MAC = 2.4GHz MAC + 4

    I think the firmware automatically calculates the 5GHz MAC so I'm unsure how to correct this - any ideas?

    Some (hopefully useful info)

    The R7000 It has the original unmodified cfe
    On base the MAC printed is E4:F4:C6:XX:XX:81

    Some info from putty etc.

    br0 Link encap:Ethernet HWaddr E4:F4:C6:XX:XX:81
    eth0 Link encap:Ethernet HWaddr E4:F4:C6:XX:XX:81
    eth1 Link encap:Ethernet HWaddr E4:F4:C6:XX:XX:81 <- 2.4GHz
    eth2 Link encap:Ethernet HWaddr E4:F4:C6:XX:XX:82 <- 5GHz
    vlan1 Link encap:Ethernet HWaddr E4:F4:C6:XX:XX:81
    wl0.1 Link encap:Ethernet HWaddr E6:F4:C6:XX:XX:82 <- 2.4GHz guest 1

    nvram values:

    et0macaddr=E4:F4:C6:XX:XX:81
    lan1_hwaddr=
    lan_hwaddr=E4:F4:C6:XX:XX:81
    wan0_hwaddr=E4:F4:C6:XX:XX:81
    wan0_hwaddr_x=
    wan1_hwaddr=
    wan1_hwaddr_x=
    wan_hwaddr=E4:F4:C6:XX:XX:81
    wan_hwaddr_x=

    wl_hwaddr=E4:F4:C6:XX:XX:81

    wl0_hwaddr=E4:F4:C6:XX:XX:81 <- 2.4GHz
    wl0.1_hwaddr=E6:F4:C6:XX:XX:82 <- 2.4GHz guest 1
    . . .
    wl0.13_hwaddr=E6:F4:C6:XX:XX:8E
    wl0.14_hwaddr=E6:F4:C6:XX:XX:8F
    wl0.15_hwaddr=E6:F4:C6:XX:XX:80

    wl1_hwaddr=E4:F4:C6:XX:XX:82 <- 5GHz
    wl1.1_hwaddr=E6:F4:C6:XX:XX:83 <- 5GHz guest 1
    wl1.2_hwaddr=E6:F4:C6:XX:XX:84
    . . .
    wl1.13_hwaddr=E6:F4:C6:XX:XX:8F
    wl1.14_hwaddr=E6:F4:C6:XX:XX:80
    wl1.15_hwaddr=E6:F4:C6:XX:XX:81
     
  18. Makaveli

    Makaveli Networkin' Nut Member

    Use the search function the information you are looking for is probably like 10-15 pages back in this thread.
     
  19. Daedelus

    Daedelus Network Guru Member

    Yes I looked there & tried

    nvram set et0macaddr=E4:F4:C6:XX:XX:81
    nvram set 0:macaddr=E4:F4:C6:XX:XX:81
    nvram set 1:macaddr=E4:F4:C6:XX:XX:85
    nvram commit
    reboot

    However after the reboot 1:macaddr is reset to E4:F4:C6:XX:XX:82

    The pages seem to discuss that there is an issue but but offers no clear solution or explanation of the mechansism of the generation of the 5GHz MAC and how to affect that generation or change the resultant MAC.

    i.e. are the CFE values of pci/1/1/macaddr pci/2/1/macaddr used by the firmware to generate MACs or totally ignored & would a custom CFE provide a solution.
     
    Danie1San and Stimpy88 like this.
  20. Danie1San

    Danie1San New Member Member

    @Daedelus
    Having just updated to the NG build this weekend (from a much older build), I found that I have the same issue as you.
    I had tried the same commands as above but my 1:macaddr also resets back to the device MAC address +1.
     
  21. David1

    David1 Serious Server Member

    ░█░█░█▀█░█▀█░█▀█░█░█░░█▀▄░█▀▀░█░█░█░░█░█░█▀▀░█▀█░█▀█░█░
    ░█▀█░█▀█░█▀▀░█▀▀░▀█▀░░█░█░█▀▀░█░█░█░░▀█▀░█▀▀░█▀█░█▀▄░▀░
    ░▀░▀░▀░▀░▀░░░▀░░░░▀░░░▀░▀░▀▀▀░░▀░▀░░░░▀░░▀▀▀░▀░▀░▀░▀░▀░
     
  22. David1

    David1 Serious Server Member


    if i am understanding correctly you are saying your 2.4Ghz guest 1 has the same mac as ur 5Ghz, but in your post they are not the same , one is E6 and the other is E4, therefore not the same,

    i have the latest firmware and i enabled my 2.4ghz guest and i have no problem connecting to both guest and 5ghz
    my mac are

    wl0.1_hwaddr=6A:FD:3A:XX:XX:86
    wl1_hwaddr=68:FD:3A:XX:XX:86

    its switching the 6th bit in the mac causing it to increase by 2
     
  23. Daedelus

    Daedelus Network Guru Member

    Thanks David1 - aaaah yes you are correct regarding the macs. I did miss that (mea culpa). So it should work for me - but sadly it doesn't with 2.4GHz Guest1.

    Over the last few days I've been using 2.4GHz Guest2 (wl0.2_hwaddr=E6:F4:C6:XX:XX:83) with no errors in the System Log & able to connect to 5GHz etc.

    However if I disable 2.4GHz Guest2 and enable Guest1 (wl0.1_hwaddr=E6:F4:C6:XX:XX:82) the System Log produces a constant stream of:

    Jan 1 09:38:13 kernel: br0: received packet on eth2 with own address as source address​

    and I'm unable to connect to the 5GHz channel. All very annoying.

    The pragmatic side of me says just use Guest2 but my perfectionist side is nagging me to sort it out.
     
  24. David1

    David1 Serious Server Member

    so i have had a look at it a bit more looks like eth2(5Ghz)(1:macaddr) and Guest 2.4(wl0.1) is conflicting, so you were right

    what i did was turn off guest network

    nvram set 1:macaddr=68:FD:3A:XX:XX:98
    nvram commit

    and then turn on the guest network, you will see the 5ghz mac change and if you dont reboot it seems to work
    but like you said after reboot the settings are not saving
     
  25. qamartheone

    qamartheone Serious Server Member

    which chk file u used?
     
  26. buggage

    buggage Network Guru Member

    The one included along with the .trx in the firmware download.
     
  27. juched

    juched Serious Server Member

    Create your guest network using the second guest network slot and it will not conflict. I found this out and shared here months ago.
     
    Stimpy88 and slidermike like this.
  28. elRadix

    elRadix Reformed Router Member

    Makaveli, Stimpy88 and slidermike like this.
  29. tripfish

    tripfish New Member Member

    Hello,

    I'm on 384.8. I tried to change the wifi Tx power adjustment for 2.4 and 5 GHz, but I can't see any difference.
    Used the slider and the nvram settings (wl*_txpower) via ssh. After a reboot the values are correct, but I don't see any difference in signal strength. Checked it with WifiInfoView for Windows and Wifi Analyzer on my smartphone.

    I previously had a RT-N56U with the padavan FW. There I could see a difference.
     
  30. Stimpy88

    Stimpy88 Reformed Router Member

    I doesn't work, hasn't for as long as I can remember. And yep, I've done tests with an analyser, no power or s/n increases at all.

    Sit back and wait for the usual "why do you want to increase power?", "why do you want more radiation?", "I don't know why people want to mess with that!" and "you have to improve your receiver before you mess with power", and the golden oldie... "I wish it was removed from the firmware, you should not have the right to break the law" rants to start...
     
    tripfish likes this.
  31. slidermike

    slidermike Addicted to LI Member

    lol, if it doesn't work via the command line argument then it has likely been pulled into the proprietary blobs/kernel for whatever reason Asus decided to.
    I am pretty sure Merlin would know and might have even mentioned it in the past. I believe he has said Asus is pulling more and more into the closed source material so it cannot be override.
    If you want to use this firmware then you just have to deal with that as a limitation. Other opensource firmware such as dd-wrt still allow you complete control over the tx.
     
    Stimpy88 likes this.
  32. Stimpy88

    Stimpy88 Reformed Router Member

    Yep, I expect you are right, the driver is a black box. I can't remember the last firmware this option worked in, unfortunately, not that it is much of a viable option to run old firmwares these days!
     
  33. KingP1n

    KingP1n Connected Client Member

    Question for anyone here...I read a few forums and mix reactions on overclocking the R7000. I'm currently running my R7000 to 1.4 (1400/800) for over 6 months without any issue. Do you know or read of anyone overclocking to 1.6? I would to try but I've read successful attempts and some not so successful with bricking their routers. What's your take on this? Should I even attempt this going from 1.4 to 1.6? Any info is greatly appreciated.
     
  34. slidermike

    slidermike Addicted to LI Member

    1200/800 works for all, 1400/800 works for most, 1600/800 works for a few.
    It's up to you if you want to try it.
    The safest way is to apply it but don't save the OC to nvram.
    So if it becomes unstable a reboot will restore you to a lower rate.
    You won't gain any performance from any OC unless your running cpu intensive functions like ip filters, qos or VPN.
     
  35. KingP1n

    KingP1n Connected Client Member

    How do I apply without saving to nvram? Thanks for the reply
     
  36. slidermike

    slidermike Addicted to LI Member

    At the command prompt you just make the change.
    That is an instant "apply" and as long as you don't "save" it is just in the current running session.
    I forget the exact syntax but it should look something like this.
    "nvram show | grep clk"
    that should give you the current command structure & clock freq.
    Then you type something like
    "set clkfrq=1400/800"
    May not be the exact syntax since I have not done it in a long time but should be very close.
    to save a config its like
    "nvram save"
    Of course none of the "", those are just to show you the command lay between.
     
    Stimpy88 likes this.
  37. Sl4fko

    Sl4fko Network Newbie Member

    What is a correct way to upgrade a router if I have Diversion, Skynet and AMTM installed? Just run over with install?

    What if I upgrade AND erase nvram?

    1.) It is clear, that it is best to config the router from scratch... Also JFFS partition or can I export it?
    2.) SWAP file can stay on USB or also format with EXT file system?

    So basicaly, do I have to do everything from scratch if I upgrade or can something stay from before?

    Hopefuly I was clear with what I want to say...


    Thanks!
     
  38. Makaveli

    Makaveli Networkin' Nut Member

    All you need to do is use the .trx for the upgrade.

    I also unmount the usb drive diversion is running on before I flash.

    After flash is complete and everything comes up all the scripts start up and everything should be how it was on previous firmware.

    if you start erasing Nvram and the JFFS partition you will have to reinstall everything from scratch. I only find this necessary if i'm troubleshooting an issue.
     
    thelonelycoder likes this.
  39. Sl4fko

    Sl4fko Network Newbie Member

    Do I have to stop/disable Diversion (or any program that uses SWAP...) first and then remove USB stick or is it all the same?
     
  40. Makaveli

    Makaveli Networkin' Nut Member

    You can but I didn't and it was fine.
     
  41. KingP1n

    KingP1n Connected Client Member

    Thought I was overclocking but bogomips shows:

    cat /proc/cpuinfo
    Processor : ARMv7 Processor rev 0 (v7l)
    processor : 0
    BogoMIPS : 1998.84

    processor : 1
    BogoMIPS : 1998.84

    This are the default settings...does this mean we're prevented from Oc?
     
    Last edited: Jan 18, 2019
  42. slidermike

    slidermike Addicted to LI Member

    KP, I brought that up a while back myself.
    I believe that Asus locked down the clocking by pulling it into a closed portion.
    Though at the time someone else came back and said they were OC. So maybe it reports as OC but in reality it isnt.

    If thats the case, you can still OC but you would have to go the route of editing the CFE. Which is less preferred, especially for testing or pushing the limit.
    I have never heard of an R7000 unable to OC to 1200/800 so if I were OC'ing mine and wanted to hard code it into the CFE then thats what I would do. Anything over that is questionable.
    The other option would be to abandon this fork and go to dd-wrt or tomato where (last I heard) OC was still command line easy peasy.
     
    Stimpy88 and KingP1n like this.
  43. clweb

    clweb Network Guru Member

    I think the bogoMIPS are calculated at boot.
     
  44. Makaveli

    Makaveli Networkin' Nut Member


    cat /proc/cpuinfo
    I'm at 1.2Ghz

    Processor : ARMv7 Processor rev 0 (v7l)
    processor : 0
    BogoMIPS : 2398.61

    processor : 1
    BogoMIPS : 2398.61


    To check clocks
    nvram get clkfreq

    run this to set it
    nvram set clkfreq=1200,800

    If you want to save changes
    nvram commit

    Reboot
     
    Last edited: Jan 19, 2019
    Stimpy88 likes this.
  45. thelonelycoder

    thelonelycoder Reformed Router Member

    The upcoming Diversion 4.0.7 will have an auto unmount script that does all the necessary tasks for a smooth upgrade or if you remove the disk through the WebUI.
    I never unplug it myself, just because I want to test if firmware upgrades work with my scripts installed. But that might not be the best advice for others.

    It all depends how much memory is left for the new firmware file to be uploaded to the router. Sometimes a reboot before the upgrade helps.
    But to be on the save side, remove all attached storage devices before a firmware upgrade.
     
    Makaveli likes this.
  46. KingP1n

    KingP1n Connected Client Member

    I tried these steps with no luck. I also tried the below commands:

    nvram set asuscfeclkfreq=1400,800 && nvram set asuscfecommit=1
    nvram set clkfreq=1400,800 && nvram commit && reboot

    I even edited the CFE, rebooted the router but bogomips still shows 1998.84. The GUI however, shows 1400ghz. Something is definitely blocking it.
     
  47. David1

    David1 Serious Server Member

    all i did on mine was

    nvram set clkfreq=1200,800
    nvram commit

    and then rebooted the router,

    cat /proc/cpuinfo
    Processor : ARMv7 Processor rev 0 (v7l)
    processor : 0
    BogoMIPS : 2398.61

    processor : 1
    BogoMIPS : 2398.61

    I dont know if there is a problem with saving the settings, but about a month ago i couldnt save the mac settings i was trying to change in the nvram, everytime i rebooted the router it changed back, i then went back to original firmware and tested that for like an hour but didnt like it and then installed the latest asuswrt firmware back (384.8_2) , i didnt use the legacy 380.70, and then the nvram commit seemed like it was working as i could save the mac address values
    Be carefull going back to original firmware though
     
    Makaveli likes this.
  48. J Arceg

    J Arceg Serious Server Member

    Hi,

    I have been using the Merlin firmware for the last 3-4 years and upgraded to the latest NG build (384.8_2) two months ago. Everything was working well until last night when most of the devices disconnected from my 2.4Ghz WiFi. I have close to 50 devices connecting to either 2.4 or 5Ghz.

    I had issues a few years ago with the legacy firmware where the 2.4Ghz disappears, but this time the 2.4 SSID is still visible but the devices just couldn't connect. And the other weird thing is 2-3 devices remain connected to 5Ghz but when I try connecting manually on my phone, it wouldn't let me. It says "Failed to obtain IP address". Both SSIDs are visible and I have done multiple reboots already. Last night I rebooted one last time and this morning when I woke up both bands are working but it stopped working again after an hour or so.

    What should I do? I also have an AC68u repeater on the first floor (R700 is on the third).
     
  49. phalkon30

    phalkon30 Serious Server Member

    Do you have manually assigned channels selected?

    Find what wifi channels are supported by your country, do a site survey to see what other channels are in use, and assign something in an unused range. It's possible a neighbor stepped on your channel, or your other router.

    Sent from my Nexus 6P using Tapatalk
     
  50. clweb

    clweb Network Guru Member

    When strange problems occur, the best to do is reset the router.
     
  51. Sl4fko

    Sl4fko Network Newbie Member

    Can I update the firmware also via wifi or only using LAN cable?
     
  52. slidermike

    slidermike Addicted to LI Member

    You can update from wifi but if for any reason the wifi signal flakes out during the code upgrade it might brick the router.
    Its not required but suggested to do wire upgrades.
     
    Sl4fko, Makaveli and phalkon30 like this.
  53. imafish

    imafish Serious Server Member

    Hi, suddenly my router reboots at random times. Can someone please take a look? Thanks.

    Jan 31 18:46:03 kernel: nvram: consolidating space!
    Jan 31 20:26:30 kernel: nvram: consolidating space!
    May 4 22:05:00 syslogd started: BusyBox v1.25.1
    May 4 22:05:00 kernel: klogd started: BusyBox v1.25.1 (2018-10-08 11:42:24 MSK)
    May 4 22:05:00 kernel: Linux version 2.6.36.4brcmarm (root@ubuntu) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Mon Oct 8 11:46:49 MSK 2018
    May 4 22:05:00 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f
    May 4 22:05:00 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
    May 4 22:05:00 kernel: Machine: Northstar Prototype
    May 4 22:05:00 kernel: Ignoring unrecognised tag 0x00000000
    May 4 22:05:00 kernel: bootconsole [earlycon0] enabled
    May 4 22:05:00 kernel: Memory policy: ECC disabled, Data cache writealloc
    May 4 22:05:00 kernel: MPCORE found at 19020000
    May 4 22:05:00 kernel: PERCPU: Embedded 7 pages/cpu @c8215000 s5472 r8192 d15008 u65536
    May 4 22:05:00 kernel: pcpu-alloc: s5472 r8192 d15008 u65536 alloc=16*4096
    May 4 22:05:00 kernel: pcpu-alloc: [0] 0 [0] 1
    May 4 22:05:00 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60416
    May 4 22:05:00 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
    May 4 22:05:00 kernel: PID hash table entries: 1024 (order: 0, 4096 bytes)
    May 4 22:05:00 kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    May 4 22:05:00 kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    May 4 22:05:00 kernel: Memory: 128MB 128MB = 256MB total
    May 4 22:05:00 kernel: Memory: 255504k/255504k available, 6640k reserved, 0K highmem
    May 4 22:05:00 kernel: Virtual kernel memory layout:
    May 4 22:05:00 kernel: vector : 0xffff0000 - 0xffff1000 ( 4 kB)
    May 4 22:05:00 kernel: fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
    May 4 22:05:00 kernel: DMA : 0xf7e00000 - 0xffe00000 ( 128 MB)
    May 4 22:05:00 kernel: vmalloc : 0xd0800000 - 0xf0000000 ( 504 MB)
    May 4 22:05:00 kernel: lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
    May 4 22:05:00 kernel: modules : 0xbf000000 - 0xc0000000 ( 16 MB)
    May 4 22:05:00 kernel: .init : 0xc0008000 - 0xc003d000 ( 212 kB)
    May 4 22:05:00 kernel: .text : 0xc003d000 - 0xc03aa000 (3508 kB)
    May 4 22:05:00 kernel: .data : 0xc03c2000 - 0xc03e52a0 ( 141 kB)
    May 4 22:05:00 kernel: SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    May 4 22:05:00 kernel: Hierarchical RCU implementation.
    May 4 22:05:00 kernel: RCU-based detection of stalled CPUs is disabled.
    May 4 22:05:00 kernel: Verbose stalled-CPUs detection is disabled.
    May 4 22:05:00 kernel: NR_IRQS:256
    May 4 22:05:00 kernel: MPCORE GIC init
    May 4 22:05:00 kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06 ignored.
    May 4 22:05:00 kernel: MPCORE Global Timer Clock 500000000Hz
    May 4 22:05:00 kernel: Calibrating delay loop... 1998.84 BogoMIPS (lpj=9994240)
    May 4 22:05:00 kernel: pid_max: default: 32768 minimum: 301
    May 4 22:05:00 kernel: Mount-cache hash table entries: 512
    May 4 22:05:00 kernel: CPU: Testing write buffer coherency: ok
    May 4 22:05:00 kernel: MPCORE Private timer setup CPU0
    May 4 22:05:00 kernel: Calibrating local timer... 499.910MHz.
    May 4 22:05:00 kernel: L310: cache controller enabled 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x7a130000
    May 4 22:05:00 kernel: CPU1: Booted secondary processor
    May 4 22:05:00 kernel: MPCORE Private timer setup CPU1
    May 4 22:05:00 kernel: Brought up 2 CPUs
    May 4 22:05:00 kernel: SMP: Total of 2 processors activated (3997.69 BogoMIPS).
    May 4 22:05:00 kernel: devtmpfs: initialized
    May 4 22:05:00 kernel: atomic64 test passed
    May 4 22:05:00 kernel: NET: Registered protocol family 16
    May 4 22:05:00 kernel: Found a Samsung NAND flash:
    May 4 22:05:00 kernel: Total size: 128MB
    May 4 22:05:00 kernel: Block size: 128KB
    May 4 22:05:00 kernel: Page Size: 2048B
    May 4 22:05:00 kernel: OOB Size: 64B
    May 4 22:05:00 kernel: Sector size: 512B
    May 4 22:05:00 kernel: Spare size: 16B
    May 4 22:05:00 kernel: ECC level: 8 (8-bit)
    May 4 22:05:00 kernel: Device ID: 0xec 0xf1 0x 0 0x95 0x40 0xec
    May 4 22:05:00 kernel: CCA UART Clock Config: Sel=1 Ovr=1 Div=48
    May 4 22:05:00 kernel: CCA UART Clock rate 125000000Hz
    May 4 22:05:00 kernel: bio: create slab <bio-0> at 0
    May 4 22:05:00 kernel: Switching to clocksource mpcore_gtimer
    May 4 22:05:00 kernel: NET: Registered protocol family 2
    May 4 22:05:00 kernel: IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    May 4 22:05:00 kernel: TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    May 4 22:05:00 kernel: TCP bind hash table entries: 8192 (order: 4, 98304 bytes)
    May 4 22:05:00 kernel: TCP: Hash tables configured (established 8192 bind 8192)
    May 4 22:05:00 kernel: TCP reno registered
    May 4 22:05:00 kernel: UDP hash table entries: 128 (order: 0, 4096 bytes)
    May 4 22:05:00 kernel: UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
    May 4 22:05:00 kernel: NET: Registered protocol family 1
    May 4 22:05:00 kernel: PCI: no core
    May 4 22:05:00 kernel: PCI: no core
    May 4 22:05:00 kernel: PCI: scanning bus 0
    May 4 22:05:00 kernel: PCI: Fixing up bus 0
    May 4 22:05:00 kernel: PCIE1 link=1
    May 4 22:05:00 kernel: PCIE1 switching to GEN2
    May 4 22:05:00 kernel: PCIE1 link=1
    May 4 22:05:00 kernel: PCI: Fixing up bus 0
    May 4 22:05:00 kernel: PCI: bus0: Fast back to back transfers disabled
    May 4 22:05:00 kernel: PCI: Fixing up bus 1
    May 4 22:05:00 kernel: PCI: bus1: Fast back to back transfers disabled
    May 4 22:05:00 kernel: pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
    May 4 22:05:00 kernel: pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
    May 4 22:05:00 kernel: pci 0001:01:00.0: BAR 0: set to [mem 0x08000000-0x08007fff 64bit] (PCI address [0x8000000-0x8007fff]
    May 4 22:05:00 kernel: pci 0001:00:00.0: PCI bridge to [bus 01-01]
    May 4 22:05:00 kernel: pci 0001:00:00.0: bridge window [io disabled]
    May 4 22:05:00 kernel: pci 0001:00:00.0: bridge window [mem 0x08000000-0x080fffff]
    May 4 22:05:00 kernel: pci 0001:00:00.0: bridge window [mem pref disabled]
    May 4 22:05:00 kernel: PCIE2 link=1
    May 4 22:05:00 kernel: PCIE2 switching to GEN2
    May 4 22:05:00 kernel: PCIE2 link=1
    May 4 22:05:00 kernel: PCI: Fixing up bus 0
    May 4 22:05:00 kernel: PCI: bus0: Fast back to back transfers disabled
    May 4 22:05:00 kernel: PCI: Fixing up bus 2
    May 4 22:05:00 kernel: PCI: bus2: Fast back to back transfers disabled
    May 4 22:05:00 kernel: pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
    May 4 22:05:00 kernel: pci 0002:02:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit]
    May 4 22:05:00 kernel: pci 0002:02:00.0: BAR 0: set to [mem 0x40000000-0x40007fff 64bit] (PCI address [0x40000000-0x40007fff]
    May 4 22:05:00 kernel: pci 0002:00:00.0: PCI bridge to [bus 02-02]
    May 4 22:05:00 kernel: pci 0002:00:00.0: bridge window [io disabled]
    May 4 22:05:00 kernel: pci 0002:00:00.0: bridge window [mem 0x40000000-0x400fffff]
    May 4 22:05:00 kernel: pci 0002:00:00.0: bridge window [mem pref disabled]
    May 4 22:05:00 kernel: PCIE3 link=0
    May 4 22:05:00 kernel: VFS: Disk quotas dquot_6.5.2
    May 4 22:05:00 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    May 4 22:05:00 kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
    May 4 22:05:00 kernel: fuse init (API version 7.15)
    May 4 22:05:00 kernel: msgmni has been set to 499
    May 4 22:05:00 kernel: et0: et_mvlan_netdev_event: event 16 for vlan1 mvlan_en 0
    May 4 22:05:00 kernel: et0: et_mvlan_netdev_event: event 5 for vlan1 mvlan_en 0
    May 4 22:05:01 kernel: et0: et_mvlan_netdev_event: event 16 for vlan2 mvlan_en 0
    May 4 22:05:01 kernel: et0: et_mvlan_netdev_event: event 5 for vlan2 mvlan_en 0
    May 4 22:05:01 kernel: et0: et_mvlan_netdev_event: event 13 for vlan1 mvlan_en 0
    May 4 22:05:01 kernel: et0: et_mvlan_netdev_event: event 1 for vlan1 mvlan_en 0
    May 4 22:05:01 kernel: device vlan1 entered promiscuous mode
    May 4 22:05:01 kernel: device eth0 entered promiscuous mode
    May 4 22:05:01 kernel: device eth1 entered promiscuous mode
    May 4 22:05:01 kernel: device eth2 entered promiscuous mode
    May 4 22:05:01 kernel: br0: topology change detected, propagating
    May 4 22:05:01 kernel: br0: port 3(eth2) entering forwarding state
    May 4 22:05:01 kernel: br0: port 3(eth2) entering forwarding state
    May 4 22:05:01 kernel: br0: topology change detected, propagating
    May 4 22:05:01 kernel: br0: port 2(eth1) entering forwarding state
    May 4 22:05:01 kernel: br0: port 2(eth1) entering forwarding state
    May 4 22:05:01 kernel: br0: topology change detected, propagating
    May 4 22:05:01 kernel: br0: port 1(vlan1) entering forwarding state
    May 4 22:05:01 kernel: br0: port 1(vlan1) entering forwarding state
    May 4 22:05:01 nat: apply redirect rules
    May 4 22:05:06 dnsmasq[244]: started, version 2.80test7 cachesize 1500
    May 4 22:05:06 dnsmasq[244]: DNSSEC validation enabled
    May 4 22:05:06 dnsmasq[244]: DNSSEC signature timestamps not checked until receipt of SIGINT
    May 4 22:05:06 dnsmasq[244]: configured with trust anchor for <root> keytag 20326
    May 4 22:05:06 dnsmasq[244]: configured with trust anchor for <root> keytag 19036
    May 4 22:05:06 dnsmasq[244]: asynchronous logging enabled, queue limit is 5 messages
    May 4 22:05:06 dnsmasq-dhcp[244]: DHCP, IP range 192.168.1.1 -- 192.168.1.99, lease time 1d
    May 4 22:05:06 dnsmasq[244]: read /etc/hosts - 5 addresses
    May 4 22:05:06 R7000: start httpd:80
    May 4 22:05:06 NAT_Tunnel: AAE Service is stopped
    May 4 22:05:06 AAE: AAE Service is started
    May 4 22:05:06 httpd: Generating SSL certificate...
    May 4 22:05:06 jffs2: valid logs(1)
    May 4 22:05:06 disk_monitor: be idle
    May 4 22:05:06 hour_monitor: daemon is starting
    May 4 22:05:06 hour_monitor: daemon terminates
    May 4 22:05:06 WAN_Connection: ISP's DHCP did not function properly.
    May 4 22:05:07 Mastiff: init
    May 4 22:05:07 lldpd[310]: could not open either /etc/os-release or /usr/lib/os-release
    May 4 22:05:07 lldpd[310]: lsb_release information not available
    May 4 22:05:07 lldpd[313]: created chroot directory /var/run/lldpd
    May 4 22:05:07 lldpd[313]: protocol LLDP enabled
    May 4 22:05:07 lldpd[313]: protocol CDPv1 disabled
    May 4 22:05:07 lldpd[313]: protocol CDPv2 disabled
    May 4 22:05:07 lldpd[313]: protocol SONMP disabled
    May 4 22:05:07 lldpd[313]: protocol EDP disabled
    May 4 22:05:07 lldpd[313]: protocol FDP disabled
    May 4 22:05:07 lldpd[313]: libevent 2.0.21-stable initialized with epoll method
    May 4 22:05:07 lldpd[313]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
    May 4 22:05:07 lldpd[313]: cannot get ethtool link information with GSET (requires 2.6.19+): Operation not permitted
    May 4 22:05:07 lldpcli[311]: lldpd should resume operations
    May 4 22:05:08 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 3
    May 4 22:05:08 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 3
    May 4 22:05:08 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 3
    May 4 22:05:08 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 3
    May 4 22:05:08 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 2
    May 4 22:05:08 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 2
    May 4 22:05:08 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 2
    May 4 22:05:08 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 2
    May 4 22:05:08 kernel: usbcore: registered new interface driver cdc_acm
    May 4 22:05:08 kernel: cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
    May 4 22:05:09 kernel: usbcore: registered new interface driver asix
    May 4 22:05:09 kernel: usbcore: registered new interface driver cdc_ether
    May 4 22:05:09 kernel: usbcore: registered new interface driver rndis_host
    May 4 22:05:09 kernel: cdc_ncm: 14-Mar-2012
    May 4 22:05:09 kernel: usbcore: registered new interface driver cdc_ncm
    May 4 22:05:09 kernel: usbcore: registered new interface driver cdc_wdm
    May 4 22:05:09 kernel: usbcore: registered new interface driver qmi_wwan
    May 4 22:05:09 kernel: cdc_mbim: loaded
    May 4 22:05:09 kernel: usbcore: registered new interface driver cdc_mbim
    May 4 22:05:09 kernel: et0: et_mvlan_netdev_event: event 8 for vlan2 mvlan_en 0
    May 4 22:05:09 kernel: et0: et_mvlan_netdev_event: event 13 for vlan2 mvlan_en 0
    May 4 22:05:09 kernel: et0: et_mvlan_netdev_event: event 1 for vlan2 mvlan_en 0
    May 4 22:05:09 dnsmasq[244]: read /etc/hosts - 5 addresses
    May 4 22:05:09 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 3
    May 4 22:05:09 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 3
    May 4 22:05:09 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 3
    May 4 22:05:09 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 3
    May 4 22:05:09 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 2
    May 4 22:05:09 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 2
    May 4 22:05:09 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 2
    May 4 22:05:09 lldpd[313]: custom TLV op replace oui f8:32:e4 subtype 2
    May 4 22:05:10 kernel: SCSI subsystem initialized
    May 4 22:05:10 kernel: csw_retry 100
    May 4 22:05:10 kernel: Initializing USB Mass Storage driver...
    May 4 22:05:10 kernel: usbcore: registered new interface driver usb-storage
    May 4 22:05:10 kernel: USB Mass Storage support registered.
    May 4 22:05:11 kernel: Tuxera FAT 12/16/32 driver version 3015.1.29.5_1 [Flags: R/W MODULE].
    May 4 22:05:11 kernel: Built against headers 2.6.36.4brcmarm #1 SMP PREEMPT Wed Dec 2 11:17:39 CST 2015 arm
    May 4 22:05:11 kernel: Running on kernel 2.6.36.4brcmarm #1 SMP PREEMPT Mon Oct 8 11:46:49 MSK 2018 armv7l
    May 4 22:05:11 kernel: Tuxera NTFS driver 3015.1.29.8_1 [Flags: R/W MODULE].
    May 4 22:05:11 kernel: Tuxera HFS+ driver 3014.7.28
    May 4 22:05:11 kernel: usbcore: registered new interface driver usblp
    May 4 22:05:13 rc_service: udhcpc 483:notify_rc start_firewall
    May 4 22:05:13 lldpd[313]: removal request for address of 173.72.15.48%10, but no knowledge of it
    May 4 22:05:13 dnsmasq[244]: read /etc/hosts - 5 addresses
    May 4 22:05:13 dnsmasq[244]: using nameserver 173.70.220.61#53
    May 4 22:05:13 dnsmasq[244]: using nameserver 173.70.220.62#53
    May 4 22:05:14 nat: apply nat rules (/tmp/nat_rules_vlan2_vlan2)
    May 4 22:05:14 wan: finish adding multi routes
    May 4 22:05:14 rc_service: udhcpc 483:notify_rc stop_upnp
    May 4 22:05:14 rc_service: waitting "start_firewall" via udhcpc ...
    May 4 22:05:15 kernel: nf_conntrack_rtsp v0.6.21 loading
    May 4 22:05:15 kernel: nf_nat_rtsp v0.6.21 loading
    May 4 22:05:15 rc_service: udhcpc 483:notify_rc start_upnp
    May 4 22:05:15 rc_service: waitting "stop_upnp" via udhcpc ...
    May 4 22:05:17 WAN_Connection: WAN was restored.
    May 4 22:05:17 dnsmasq[244]: read /etc/hosts - 5 addresses
    May 4 22:05:17 dnsmasq[244]: using nameserver 173.70.220.61#53
    May 4 22:05:17 dnsmasq[244]: using nameserver 173.70.220.62#53
    May 4 22:05:17 miniupnpd[539]: HTTP listening on port 45069
    May 4 22:05:17 miniupnpd[539]: Listening for NAT-PMP/PCP traffic on port 5351
    May 4 22:05:17 dhcp_client: bound 173.72.15.48 via 173.72.15.1 during 86400 seconds.
    May 4 22:05:18 ntp: start NTP update
    Jan 31 22:15:23 rc_service: ntp 509:notify_rc restart_diskmon
    Jan 31 22:15:23 dnsmasq[244]: now checking DNSSEC signature timestamps
    Jan 31 22:15:23 dnsmasq[244]: read /etc/hosts - 5 addresses
    Jan 31 22:15:23 disk_monitor: Finish
    Jan 31 22:15:24 disk_monitor: be idle
    Jan 31 22:16:05 crond[251]: time disparity of 391750 minutes detected
     
  54. KingP1n

    KingP1n Connected Client Member

    I'm currently using custom CFE and on latest FW...what are steps to try ddwrt kong or tomato? Do simply just upload the trx file from those fws and flash? Thanks. I simply trying to ovecrclov using those fws and come back to xvortex. Thanks for input.
     
  55. KingP1n

    KingP1n Connected Client Member

    I think I found my answer :)
     
  56. KingP1n

    KingP1n Connected Client Member

    Good news all...Merlin 384.9 is finalized.
     
    Ubimoo, mickyarams``` and phalkon30 like this.
  57. mickyarams```

    mickyarams``` New Member Member

    You can flash the trx files from tomato directly on xvortex, kong and any other ddwrt variants are in bin files and so you have to flash ofw firmware first. All of these has been explained in detail on the first post.
     
  58. KingP1n

    KingP1n Connected Client Member

    @XVortex ...thanks for everything you do. I made a small donation for all the hard work you do. It's really appreciated.
     
  59. XVortex

    XVortex Networkin' Nut Member

    XWRT based on Merlin's 384.9 is WIP now.
    I hesitated a bit and did not have time to make changes to the release. sry.

    @KingP1n, much appreciated. thanks.
     
    peyton, Stimpy88, Makaveli and 3 others like this.
  60. Sl4fko

    Sl4fko Network Newbie Member

    XVortex,

    just for info, how much work do you actually have? I mean, the hardware is pretty much the same as AC68U... Is XWRT port difficult to compile?

    Really appreciate all your work, I am really happy with it...
     
  61. Makaveli

    Makaveli Networkin' Nut Member

    Based on this in the change log

    Networkmap listing may be unreliable. (Bug in Asus's code)

    i'm going to hold off on it as I have 55 days of uptime on 384.8_2 and will wait abit but thanks for your efforts.
     
    Sl4fko and Stimpy88 like this.
  62. XVortex

    XVortex Networkin' Nut Member

    XWRT v384.9 is on-stage now!
    But since some people report some issues (I personally do not), I recommend flashing with caution.
     
    GDT78, Makaveli, edusodanos and 4 others like this.
  63. David1

    David1 Serious Server Member

    thx for the firmware update, QOS seems to be working or at least doing something, need to do more testing
     
    KingP1n likes this.
  64. philsocal

    philsocal New Member Member

    Router reboots after most changes?
    R7000, running 384.8.2. About 80% of the time when I make a change (enable guest wireless ,etc), the router reboots and kills my incoming connections. Is this expected behavior?
     
  65. David1

    David1 Serious Server Member

    did you do a factory reset after upgrade, otherwise try another factory reset and check again

    also dont enable guest 1 wireless, has a mac conflict with 5Ghz, enable Guest 2
     
  66. moonweasel

    moonweasel New Member Member

    Hello! I have an R7000P router — mostly the same as R7000, I think, but with MU-MIMO and AC2300 instead of AC1900.

    Will the XWRT-VORTEX firmware work on this router?

    I am paying for 1Gig fiber speeds but currently unable to get more than ~200Mbps even with a wired connection, and it sounds like it is due to PPPOE offloading being broken in the stock firmware. :/
     
  67. Stimpy88

    Stimpy88 Reformed Router Member

    This has been an issue in this firmware for years. It's a bug of some kind, and has never been fixed.

    It usually starts after setting up the wifi settings, then after any settings change, the router does a full restart. My feeling is that the firmware corrupts something in its own settings.

    There is another related bug, where suddenly after changing wifi settings, the router will full reboot as usual, but then it will have reverted to default settings, and you have to start over from scratch.
     
  68. Sl4fko

    Sl4fko Network Newbie Member


    No, it will not.

    Try ddwrt builds from Kong.
     
    Last edited: Feb 9, 2019
    Makaveli likes this.
  69. Makaveli

    Makaveli Networkin' Nut Member

    Traditional QOS has been working fine now for the last few firmware's unless i'm missing something.

    True this has been like this since day 1. However its not really a problem for me I find the settings that work which I did maybe 2 years ago and never had to change it since. If you are someone that is constantly messing with it then ya this is going to get annoying for you.
     
    Stimpy88 likes this.
  70. Tequila

    Tequila New Member Member

    Hi there, in v384.9 the "clients list" on the Network Map page is broken. It only shows 2 devices instead of 8 that are connected.

    -Edit: nevermind, just saw this post :)

     
    Last edited: Feb 9, 2019
    Makaveli likes this.
  71. clweb

    clweb Network Guru Member

    This problem is not new to 384.9. I noticed it since the beginning.
     
  72. Tequila

    Tequila New Member Member

    I didn't had problems with it while using previous versions
     
    Sl4fko likes this.
  73. Sl4fko

    Sl4fko Network Newbie Member

    Agree, same in my case.


    Rolling back to 384.8-2...
     
  74. clweb

    clweb Network Guru Member

    I had always connected devices appearing in the liest and disappear a few seconds later.
    Not all devices, but some of them. Sometimes WiFi conneted sometimes wired.
    No real logic.
    I did'nt try 384.9 yet.
     
  75. PinkFMercury

    PinkFMercury New Member Member

    What are the steps for installing XWRT-Vortex on R7000 from DD-WRT?
    I am currently on DD-WRT v3.0-r36070M kongac (05/31/18).
    Do I need to go back to stock firmware and then install XWRT-Vortex to prevent bricking my router? Or can I go straight to vortex?
    Is a 30 30 30 reset required?
     
  76. longin1

    longin1 Network Newbie Member

    Hi All,

    There is a problem with my R7000.
    Now I use 384.9 firmware but the problem was existing on the previous versions, too.
    The problem is that I can't use 2.4GHz and 5GHz wireless together. I mean, when I use the defaults settings where the both frequencies are enabled and when I connect 2-3 wireless devices - the router is cutting off the access to wireless network. This time I can use ethernet switch. Wireless is not coming back just like that, I must restart the router manually. I observed, when both frequencies are enabled and devices "strongly" use 2.4GHz only - the router is doing the same - cut the connections. But when I turn off the 5GHz manualy and leave 2.4GHz only - the router is working perfectly all the time.
    Have you met this kind of problem?
    What are the best setting for coexistance for this both frequencies?

    Regards.
     
  77. longin1

    longin1 Network Newbie Member

    Hi,

    Have you seen this:

    link
     
  78. longin1

    longin1 Network Newbie Member

    This: :)

    https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1041469 ?

    ?
     
  79. PinkFMercury

    PinkFMercury New Member Member

    Thanks but I no longer need it. I took a gamble and straight flashed FreshTomato and it worked fine. Now I'm wondering which is better out of the two: FreshTomato or XWRT-Vortex.
     
  80. Sl4fko

    Sl4fko Network Newbie Member

    Any problems with AC/5 GHz signal on FreshTomato? I tried AdvancedTomato few months ago and could not get AC/5GHz signal to work (could not choose a channel, no 80 MHz signal etc...)
     
  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