Tomato for ARM routers

Discussion in 'Tomato Firmware' started by kthaddock, Feb 28, 2014.

  1. zatoom

    zatoom LI Guru Member

    thank you.
     
  2. MrDoh

    MrDoh Addicted to LI Member

    I'm not sure exactly which release this improvement started with, but reboots seem a lot faster with v130 than before to me. As well as a thorough nvram erase, both of these are faster than they were. Reboots in particular used to take longer than the countdown on the screen, and now they're shorter than that.

    Thanks Shibby, v130 is working well for me on the R7000.
     
  3. blackmack

    blackmack LI Guru Member

    Boot with 130 1/2 faster on AC68U. Can someone look into USB 3.0 led for this router, I think its gpio 14?
    And also speed up USB 3.0 port.
     
  4. MrDoh

    MrDoh Addicted to LI Member

    There is one bug that I've encountered, though. For IPv6, the following setting:

    Advanced -> DHCP/DNS -> Announce IPv6 on LAN (DHCP)

    does not seem to be saved in the settings, or isn't restored if it is saved. If this isn't set and IPv6 is enabled, my router log is overrun with weird messages.

    I've found that I have to turn this on every time I restore backed up settings, even though I'm restoring backed up settings that had it turned on in it. So it seems that this isn't included in the settings that are saved when I use the firmware "Backup Configuration" functionality (or it isn't restored, can't tell which).

    Thanks!
     
  5. darksky

    darksky Addicted to LI Member

    Toastman - Are you using an ARM router in your physical possession now? Which one and is it your primary router? Thanks!
     
  6. cistehovado

    cistehovado Network Newbie Member

    Hello, I would like to ask if the strange PING behavior (noticed on 1.28fw) on Netgear R7000 is solved? So I can finally move from Netgear FW to tomato shibby :)
     
  7. 0007Rraegten

    0007Rraegten Reformed Router Member

    deleted
     
    Last edited: Jun 16, 2015
  8. Toastman

    Toastman Super Moderator Staff Member Member

    @darksky - yes, I am using an R7000 online in one apartment block with about 130 users active currently. I'm using my build 9002 without the updated miniupnp package. It's stable and has not rebooted at all since I flashed it. You'll appreciate that all my installations are still ADSL with maximum speeds 16Mbps/1Mbps so I have no real need to upgrade anything until we get faster speeds here. I only have one installation with faster speed of 50Mbps and the R7000 also performed well there. It uses the new QOS ingress from KyleS using IFB instead of IMQ, which is functioning fine.

    @Cistehovado -The ping issue has been fixed.
     
  9. darksky

    darksky Addicted to LI Member

    Thanks for the info and for all you invest in Tomato! Can you field a few questions for me?

    1) Do your ARM builds offer any security advantages over MIPSR2 builds?
    2) Which kernel does tomato-R7000-9002Toastman-ARM-VPN-64k run?
    3) I remember reading on a thread in here that the reason hy the MIPSR2 builds are stuck with the EOL kernel version 2.6.22.19 is because the drivers for the radios are not opensource, but binary blobs only compatible with that specific kernel. Is this the case ith the ARM builds?
     
  10. MrDoh

    MrDoh Addicted to LI Member

    Yes, the random ping issue was fixed back in v127 (I think), and hasn't been an issue for some time. You're safe to come back into the water *smile*.
     
  11. MrDoh

    MrDoh Addicted to LI Member

    I can answer one of those...yes, the wireless drivers are bound to particular version of the kernel for tomato ARM as well as regular tomato. The dd-wrt folks apparently have the Broadcom SDK license, so they can use the latest kernel, but not tomato. Tomato would have to the whole driver/kernel piece forward to move either forward, and I'm not sure what that would cost to do that. I believe that at least some later kernel fixes have been patched back into the old kernel that tomato and tomato ARM are bound to. This is also the case for RMerlin/Asus firmware, they're still on a 2.6 kernel as well.
     
  12. eangulus

    eangulus Network Guru Member

    Is there any official word yet on whether Shibby Tomato will work on the RT-AC68P?

    Don't want to buy one only to find out it won't yet...
     
  13. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "Yes, the random ping issue was fixed back in v127 (I think), and hasn't been an issue for some time."

    I still have it.
     
  14. MrDoh

    MrDoh Addicted to LI Member

    I'm sorry...but...it was fixed for most people then, including me. Working great on my R7000.
     
  15. MrDoh

    MrDoh Addicted to LI Member

    According to Shibby, it's fixed. I haven't had a chance to try it on my RT-AC68P yet.
     
  16. Edrikk

    Edrikk Network Guru Member

    Just go look at the change log on Shibbys page to see when it was fixed.
     
  17. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "it was fixed for most people then"

    Well it didn't show up for "most people" either. It as a symptom did not manifest itself for everyone. So to say it is fixed for most people misrepresents the nature of the thing. It wasn't a "most people" thing from the get go.

    With Shibby's I get intermittent stalls, lags, pages not loading. When I do I check pings and they are high or long depending on your point of view. Despite it being random and difficult to predict it is clearly present.

    Boot and it clears for awhile but will eventually have the symptom again.

    Which is exactly how it was before.

    I do not have this symptom with XVORTEX's RMERLIN's port, DD-WRT or Netgear's OEM FW. Always install the same way for all of them by clearing NVRAM and doing settings from scratch.

    Wish I didn't have them. Would very much like to and prefer to use a Tomato variant. Can not at this juncture. I guess I could if I wanted to periodically listen to complaints about the web getting stuck.

    When I have the symptom as it always has looks to me like the CPU is busy doing something else and the stalls are due to the CPU being all tied up on some other task.

    Glad others aren't having the issue. But it as an issue can not be classified by a blanket statement that it is 100% "fixed".
     
  18. Grimson

    Grimson Networkin' Nut Member

    EOL or not doesn't really matter with Tomato here, have a look at the source repositories and you'll find that the last time something from upstream has been added was around 2011 when Teddy was still an active developer. Since then all changes where done by the different Tomato developers, and they don't care whether it's officially EOL or not.
     
  19. Toastman

    Toastman Super Moderator Staff Member Member

    @jsmiddleton4 - The issues you describe were exactly what I experienced too. However, we believed this was fixed a while back, as mentioned above. Did you try flashing either my build or KyleS's build ... just to check? I can ping all day and still get an average <1mS response from the LAN port, or <20mS response from the ISP gateway. Before, some pings would go out to several seconds.

    I still see faster page opening times from my RT-N16's, which doesn't make much sense to me.
     
    MrDoh likes this.
  20. KyleS

    KyleS LI Guru Member

    Ensure your nvram is clean and factory reset with Tomato. I know you said you do a clear, but make sure it's actually taking place. Did you try to clear the problematic nvram variables by hand?
     
  21. MrDoh

    MrDoh Addicted to LI Member

    I already said that I was sorry that I said that the problem was fixed. I'm really really sorry that you're having this issue, and that I said that it was fixed. I'll try to be more careful in the future and not say that it was fixed for most people, or fixed for everyone that had the problem except jsmiddleton4.

    Sorry.
     
    Last edited: Jun 17, 2015
  22. Edrikk

    Edrikk Network Guru Member

    The problem HAS been fixed. If the user hasn't reset NVRAM and manually reconfigured, then the issue will still be there for them.

    Some people either don't reset, OR they reset and then just load the backup config right back in. I'm not sure in this case if the NVRAM backup scripts some people use would put the "problematic" value back into NVRAM or not.
     
  23. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Sorry Edrikk, have done all that and still have the problem. Noted that I have reset and reconfigure. I do so with every FW change. So the problem has not been 100% fixed.

    Again glad it is for some. It is not 100% resolved.
     
  24. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Mr. Doh, no problem.
     
    MrDoh likes this.
  25. cr00kedview

    cr00kedview Network Guru Member

    As a happy new owner of an R7000, I immediately flashed Shibby's 130 build. Unfortunately, the wireless performance is extremely poor for me (worse than my e4200). I reset nvram after updating, but are there any settings I'm missing that would make a difference?

    I flashed the latest DD-WRT kong firmware and the wireless speed is much faster than Tomato, but I prefer the TomatoUSB interface.
     
  26. illiac4

    illiac4 Reformed Router Member

    http://linksysinfo.org/index.php?threads/r7000-super-weak-wireless.70701/
     
  27. Tony Arnold

    Tony Arnold Serious Server Member

    Sadly switching to Anguilla seems to restrict the 5Ghz channel to 40MHz width. Is DD-WRT's better performance due to having newer/different drivers than what we have in Tomato? They seem to support VHT 80+80 and a bunch of other things that are "missing" (?) from Tomato.
     
  28. slidermike

    slidermike Addicted to LI Member

    Technically the R7000 only supports (reporting bug in DDWRT that shows 80+80) 80 wide but that's all the hardware will do anyway.
    DDWRT does have/use newer drivers too.
     
  29. cr00kedview

    cr00kedview Network Guru Member

  30. Tony Arnold

    Tony Arnold Serious Server Member

    Is there something preventing us from using DD-WRT's newer drivers? I'm sorry — questions like these are probably covered in an FAQ somewhere, but I haven't been able to get a handle on why things are the way they are.
     
  31. The Master

    The Master Network Guru Member

    Broadcom Drivers are not open Source and the are linked with the kernel.

    DDWRT has a SDK so they could compile there own driver. Tomat has no SDK (a few Tousend Dollars).

    That is why tomat has kernel 2.6xx, and ddwrt has 3.x kernel.
     
  32. Tony Arnold

    Tony Arnold Serious Server Member

    So how are we able to use the Broadcom drivers that we do have? Is it worth "passing the plate around" for a donation to pay for access to the SDK?
     
    visceralpsyche likes this.
  33. darksky

    darksky Addicted to LI Member

    Seems like crowd sourcing it would be pretty easy given the user base... +1 and I would be very happy to donate. Guess we need details, cost, limitation, etc.
     
    visceralpsyche likes this.
  34. MrShimpy

    MrShimpy Connected Client Member

    In my opinion it would be a very bad idea to relay on dd-wrt, because dd-wrt looks like a big mess to me.

    The Broadcom SDK is very expensive, and you can not just pay the money and get it, you have to sign a non disclosure agreement as well, and I don't think that they give everybody access to the SDK who is willing to pay the money.
     
    jsmiddleton4 likes this.
  35. darksky

    darksky Addicted to LI Member

    I know nothing of the process, but it doesn't sit well with me to have an EOL kernel at the heart of the project. I love TomatoUSB but that aspect of the firmware has always bugged me.
     
  36. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "dd-wrt looks like a big mess to me."

    Amen Mr. Shimp.....

    I want to tell those folks to pick a router, address it, get it stable, and then move on to the next. Trying to do way too much for too many different platforms.
     
  37. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "DDWRT has a SDK so they could compile there own driver."

    My understanding is that's not quite accurate. They can tweak some stuff here and there but in terms of full access to the driver that is not what DDWRT developers have. They have more than Tomato guys have. But "full" access to be able to compile their own driver is not the case either. Could be wrong but that's my understanding.
     
  38. AndreDVJ

    AndreDVJ LI Guru Member

    I'll give my two cents as an IT worker. We need remember that DD-WRT is a company working for profit, so someone is paid to maintain core functionality while TomatoUSB is a project which is right now maintained in form of mods (Shibby, Toastman, etc) by ordinary people working on it for free.

    That also means that even if we manage to fund few thousands of dollars for getting Broadcom SDK, the vendor would probably refuse as there's no company behind TomatoUSB and its "mods" to sign an NDA, contracts and all the legalese involved.
     
    Toastman and MrShimpy like this.
  39. RMerlin

    RMerlin Network Guru Member

    Also, it's not as simple as just "copy the source code and compile it". You need some solid low-level knowledge on wireless technology to be able to configure and compile that driver. See how even companies like Netgear or Asus are occasionally struggling with their own releases.
     
    Toastman and MrShimpy like this.
  40. charettepa

    charettepa New Member Member

    hi RMerlin

    long time tomato user
    decided to try asus merlin

    im trying to figure out how to append to
    resolve.dnsmasq

    it dosent seem to be one of the .add functions
    and amytime i change it
    it changes again after reboot

    what i want is my 2 provided upstream dns servers
    + the 3 i have added
    for a total of 5

    and i use the all-servers to "probe" all 5

    this just 1 check mark in tomato to
    Use received DNS with user-entered DNS
    i have spent 3 hours now and just dont know what to do

    can you please help
     
  41. jerrm

    jerrm Network Guru Member

    @shibby20 , @Toastman :

    nvram show "bug"

    Under ARM, the final "size: xxxxx bytes (yyyyy left)" stats line in the ARM "nvram show" command writes to stderr instead of stdout.

    If all output is redirected ("nvram show &> settings.txt") the stats line will be mixed in randomly with the settings. This also "breaks" nvram show from the GUI Tools->System Commands page.

    Probably need a flush around line 277 of nvram_arm/main.c.
     
    Last edited: Jul 2, 2015
  42. redsandvb

    redsandvb Network Guru Member

    Sorry for the stupid question, but...

    So with these ARM routers we use 'nvram show' instead of 'nvram export --set' to see the settings, and still 'nvram commit' to save them?

    I was looking to get an Asus RT-AC68P sometime...

    Thanks!
     
  43. slidermike

    slidermike Addicted to LI Member

    Yep
     
  44. redsandvb

    redsandvb Network Guru Member

    Thank you!
     
  45. jerrm

    jerrm Network Guru Member

    It's not quite that simple.

    ARM's nvram is very limited compared to MIPS. There are only the most basic versions of show, get, set, unset, commit, erase, restore and save.

    There is nothing analogous to any flavor of the MIPS find, export, import, setfile, setfb64, etc commands.

    ARM's show command is a cruder, unsorted version of the MIPS show command. It gives a readable version of all of nvram, but there is no out of the box automated way to take that output and restore it.

    A script like the one here http://www.linksysinfo.org/index.ph...t-can-not-handle-wrap-text.68478/#post-228672 can be used to create the equivalent of "nvram export --set" output.
     
  46. slidermike

    slidermike Addicted to LI Member

    jerrm,
    you should be able to use
    nvram show | sort
    to show the output of the config in a "sorted" fashion in telnet.
    If you want to copy the config to a file you can do something like this
    nvram show | sort > :/tmp/home/root/r7000_config_7_2_2015.sh
    Of course where your storing the file will decide what path you have to use in the above command.
    Here is the output of the command line command. As you see, it completes and the file is sorted.
    @R7000:/tmp/home/root# nvram show | sort > /tmp/home/root/r7000_config_7_
    2_2015.sh
    size: 47760 bytes (17776 left)
     
  47. jerrm

    jerrm Network Guru Member

    Not really. Doing so will break any multi-line entries. I like my scripts and config files in one piece.

    Just saving to a ".sh" file doesn't mean you can do anything with that file. It still requires some additional scripting to be useful. Again, multi-line entries present a problem. MIPS "nvram get" returns an error code, that can be used to determine if a variable exists or not. ARM doesn't.
     
  48. slidermike

    slidermike Addicted to LI Member

    saving to .sh was just an example to show it does function. You don't have to save to that extension at all.

    The OP question was not about advanced nvram commands. He asked if he could/should use "nvram show" & "nvram set" commands in ARM based routers to view and modify his router via command line.
    I think your diluting his original/simple question.
     
  49. jerrm

    jerrm Network Guru Member

    The OP question was about the absence of "nvram export --set" on ARM. I assume he is using "export --set" for more than just "seeing" the values. MIPS "export --set" provides an easy, cut and paste, no fiddling necessary method for saving/restoring nvram values.

    ARM's "nvram show" does not provide any of that simplicity. I provided an option to achieve the essentially the same functionality with explanation why the extra work is needed under ARM.
     
  50. slidermike

    slidermike Addicted to LI Member

    By adding the rest of the OP text, his question seems fairly straight forward. You "assumed" he was doing more than just "seeing" and yet in his own words (quoted above) he said "to see the settings."
    Anyway, were way off topic for this thread. He now has his simple answer and a more in depth answer.
     
  51. fubdap

    fubdap LI Guru Member

    On the r7000 GUI I did:
    nvram show | grep dhcpd

    what command do I need to restore it on the GUI?

    Thanks
     
  52. slidermike

    slidermike Addicted to LI Member

    fub,
    kindly include a line of the output from the mentioned command and we can show you what it would look like in a "nvram set" scenario.
     
  53. jerrm

    jerrm Network Guru Member

    I saw the original text. @redsandvb has been around for a while, if he is using export instead of show, odds are there is a reason. The context of the chain of posts he was replying to was about the lack of export functionality.

    As a long time Tomato user, I can't consider show a substitute for export, it's just the only ARM option available. If someone is considering a move from MIPS to ARM, knowing how the move will impact their backup processes is good info. Better a thorough answer than an inaccurate one.

    Beyond that, the lack of ARM export has come up several times, the answer is also for @Moonshine, @asturnauta and others before and after @redsandvb.
     
  54. fubdap

    fubdap LI Guru Member

    Here is what I get: So how to restore?

    upload_2015-7-2_14-20-51.png
     
  55. slidermike

    slidermike Addicted to LI Member

    The "trick" is to use " " around the data immediately after the = sign.
    So for line 1 it would be like this:
    nvram set dhcpd_startip="192.168.1.2" Notice the " " encapsulating the string after the = sign.
    This would be your statics:
    nvram set dhcpd_static="00:23:5A:73:A7:FF<192.168.1.25<Blakeetc..."

    I hope that helps.
    I have never done command line in the MIPSL, just the ARM routers and that's how it is done in them.
    Then once you have "set" the variables as you like, you would commit them (like hitting save in gui) by
    nvram commit
    Now they persist past a reboot.
     
  56. fubdap

    fubdap LI Guru Member

    Thanks. I will give it a try later.
     
  57. Grimson

    Grimson Networkin' Nut Member

  58. jerrm

    jerrm Network Guru Member

    I'm not sure what your point is. Either form offers essentially the same functionality in this context.

    Neither can be used blindly without escaping the appropriate characters. Three characters($"`) to escape with double quotes vs one(') with single quotes, but I hate how an embedded single quote has to become '"'"' or '\'' when using single quotes.

    Quotes are not required for nvram set unless the value contains spaces or other special characters.

    For @fubdap's example, the only value that requires quoting is for dhcpd_static.
     
    MrDoh likes this.
  59. slidermike

    slidermike Addicted to LI Member

    jerrm, I agree but for the sake of simplicity I put the " " even on single entry lines as well. That way its consistent and it works.
    I spent about an hour manually creating my cheat sheet and now anytime I reset, I can have my config back in place in a matter of minutes.
     
  60. jerrm

    jerrm Network Guru Member

    I generally quote as a matter of habit. Was only using as an example of where they were actually required.
     
  61. jerrm

    jerrm Network Guru Member

    Last edited: Jul 5, 2015
  62. jerrm

    jerrm Network Guru Member

    @shibby20 --

    Nothing in ARM appears to sync the clock after boot. There is no cron job generated based on the GUI settings to sync the clock.

    ARM inherited a modified ntpclient from AsusWRT, but AsusWRT's rc has support code for ntp that Tomato doesn't.

    Would ARM Tomato be better served going back to the MIPS ntpc?.
     
  63. tornado

    tornado New Member Member

    Tomato R&D team -> Thanks for excellent FW, my wnr3500L v2 has been rock stable for years.

    Just recently bought a R7000, and immediately put Tomato v130 on it, works excellent, and it is capable to route full duplex 100/100mbps fiber line, my old wnr3500 could only manage half duplex.

    However I tried out of curiosity the CTF setting, to enable NAT acceleration, and my port forwarding disappeared. Is it possible to put in static port routes in the 128 entry TLB, and get the port forwarding to work with CTF?

    I am writing FW at work on a much larger broadcom switch device, that has a significantly larger TLB. It is possible here to inject static lines in TLB, and here the CPU does not get involved at all if source address and port number gets a match, frame gets copied by HW directly on output port... Saves power as the CPU clock speed can be put to minimum, device get significantly cooler as well.
     
  64. lancethepants

    lancethepants Network Guru Member

    Anyone want to save me some time, and compile the cp2102 arm kernel module for me?
     
  65. hvymtlhick

    hvymtlhick Network Newbie Member

    Hi @tornado, yesterday i received my R7000 that i recently purchased, loaded Shibby's tomato-R7000-ARM--130-AIO-64K but I cannot get higher than 65Mbps, i cannot for the life of me figure out why i cannot reach near my comcast ISP's rate of 250Mbps - I can get (and exceed) 250Mbps when i direct connect my pc to their modem (xb3 in bridged-mode). is there some special setting i have to set to reach the full-speed potential of this router ?
    I am testing with only a hard-wired connection directly from my desktop PC nic to my R7000.
    I have read in a previous thread where Shibby said something about usb feature degrading the performance, so i have disabled that. Turning CTF on/off has no impact good or bad in this case. also tried with and without Enable DSCP Fix (Fixes Comcast incorrect DSCP)
    @shibby20 Can anyone give me some advice. I have now purchased two new routers, an ASUS RT-AC66U and now a Netgear R7000 both flashed with Shibby's latest versions I upgraded from the ole Linksys WRT, I bought these in hopes that i can get what i am paying for from Comcast, neither one of them reaches my speed package. Asus maxes out around 105Mbps, Netgear maxes out around 65-70Mbps. What am I doing wrong ? I am so frustrated. I am in at nearly $400 and neither router seems to be hitting the mark. Seems as if in other posts i have not seen anyone else with similar problems.
     
    Last edited: Jul 23, 2015
  66. segacorpceo

    segacorpceo Network Newbie Member

    I seemed to have fixed the 2.4ghz network not showing up on my
    Asus rt-ac56u by changing the region in my case going from singapore to united states. Will there be a fix in the future for the led status lights that don't work?
     
  67. shibby20

    shibby20 Network Guru Member

  68. Samuelheng

    Samuelheng Addicted to LI Member



    i had this problem on my r7000 also. it is related hardware problem or firmware problem??. for now temporary solution using what firmware is better, prefer has good qos.. thk
     
    Last edited: Jul 25, 2015
    jsmiddleton4 likes this.
  69. lancethepants

    lancethepants Network Guru Member

    Seems like most USB to Serial converters are rs232, but for some reason this LCD display was cp210x. Got it working now with that module! Thanks! Now for some more tinkering.

    IMG_20150725_104207674.jpg
     
    compsman, shibby20, hexa1246 and 3 others like this.
  70. MrDoh

    MrDoh Addicted to LI Member

    Wow, stylin'!
     
  71. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "? it is related hardware problem or firmware problem??"

    Don't know for sure. Could be hardware revision problem as in I have one made in different place with some part different some how, I have the issue, others with hardware made somewhere else don't have it.

    All I know is I have it. Do not have it with Netgear's OEM FW nor with XVORTEX's port based on Asuswrt and RMerlin's work.
     
  72. Samuelheng

    Samuelheng Addicted to LI Member

    thk for reply. i think i will try XVORTEX's port based on Asuswrt and RMerlin's firmware for now. currently using tomato-R7000-ARM--130-AIO-64K had to reboot everyday to prevent Request timed out pings.
     
  73. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "had to reboot everyday to prevent Request timed out pings."

    Yep. Boot and it works fine for awhile.
     
  74. Samuelheng

    Samuelheng Addicted to LI Member

    strange , when r7000 had this symptom i aways check the tomato syslog log show this kind of message . but i dun know what kind error it this ... it is related FW or hardware problem or my r7000 faulty unit?? this problem only occur in 15hour-24hour router uptime. after reboot router became to normal back.
    Code:
    Jul 27 14:31:37 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 31 callbacks suppressed
    Jul 27 14:31:37 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:37 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:37 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:37 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:37 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:38 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:38 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:39 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:39 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:39 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:42 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 19 callbacks suppressed
    Jul 27 14:31:42 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:44 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:48 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 33 callbacks suppressed
    Jul 27 14:31:48 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:48 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:48 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:52 NETGEAR-R7000 daemon.info dnsmasq-dhcp[12963]: DHCPDISCOVER(br0) 30:75:12:b6:32:4e
    Jul 27 14:31:52 NETGEAR-R7000 daemon.info dnsmasq-dhcp[12963]: DHCPOFFER(br0) 192.168.1.101 30:75:12:b6:32:4e
    Jul 27 14:31:53 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 35 callbacks suppressed
    Jul 27 14:31:53 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:53 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:53 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:53 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:53 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:53 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:53 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:53 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:59 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 18 callbacks suppressed
    Jul 27 14:31:59 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:31:59 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:01 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:01 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:01 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:01 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:01 NETGEAR-R7000 daemon.info dnsmasq-dhcp[12963]: DHCPDISCOVER(br0) 30:75:12:b6:32:4e
    Jul 27 14:32:01 NETGEAR-R7000 daemon.info dnsmasq-dhcp[12963]: DHCPOFFER(br0) 192.168.1.101 30:75:12:b6:32:4e
    Jul 27 14:32:01 NETGEAR-R7000 daemon.info dnsmasq-dhcp[12963]: DHCPREQUEST(br0) 192.168.1.101 30:75:12:b6:32:4e
    Jul 27 14:32:01 NETGEAR-R7000 daemon.info dnsmasq-dhcp[12963]: DHCPACK(br0) 192.168.1.101 30:75:12:b6:32:4e Sony-T2-Ultra
    Jul 27 14:32:01 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:01 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:05 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 24 callbacks suppressed
    Jul 27 14:32:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:06 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:06 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:06 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:10 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 8 callbacks suppressed
    Jul 27 14:32:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:11 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:11 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:11 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:11 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:15 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 11 callbacks suppressed
    Jul 27 14:32:15 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:15 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:15 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:20 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:20 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:20 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:21 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:21 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:21 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:21 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:21 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:21 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:22 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:25 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 8 callbacks suppressed
    Jul 27 14:32:25 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:25 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:25 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:26 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:26 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:26 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:27 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:27 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:32 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:32 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:32 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:33 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:34 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:34 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:34 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:34 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:34 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:34 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:37 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 22 callbacks suppressed
    Jul 27 14:32:37 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:38 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:38 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:38 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:38 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:39 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:39 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:39 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:39 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:39 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:43 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 26 callbacks suppressed
    Jul 27 14:32:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:43 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:44 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:44 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:44 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 54 callbacks suppressed
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:49 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 52 callbacks suppressed
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:54 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:32:59 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 60 callbacks suppressed
    Jul 27 14:32:59 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:00 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:05 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 57 callbacks suppressed
    Jul 27 14:33:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:05 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:06 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:06 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:10 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 56 callbacks suppressed
    Jul 27 14:33:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:10 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:11 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:11 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:11 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:11 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:11 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:15 NETGEAR-R7000 kern.warn kernel: net_ratelimit: 37 callbacks suppressed
    Jul 27 14:33:15 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:15 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
    Jul 27 14:33:16 NETGEAR-R7000 kern.warn kernel: nf_conntrack: table full, dropping packet.
     
    Last edited: Jul 27, 2015
  75. xips_

    xips_ Networkin' Nut Member

    The ghost in my machine must be Casper...

    Code:
    Tomato v1.28.0000 -130 K26ARM USB AIO-64K
    Code:
     Uptime	6 days, 04:29:36
    Code:
    Ping statistics for 192.168.2.1:
        Packets: Sent = 51, Received = 51, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
     
  76. saeHG

    saeHG Serious Server Member

  77. -mtm-

    -mtm- Serious Server Member

    This is a bug in the tomato firmware. A couple of people reported this problem.
    You can restore the signal by switching to a netgear or DD-WRT firmware and then put the tomato firmware on it. Do not switch power off.
     
  78. Frenzy

    Frenzy New Member Member

    I have an Asus RT-N18U running Tomato Firmware 1.28.0000 -2.8-130 K26ARM and my router have like 75C (cpu) at 0 - 2 wireles devices ( Load (1 / 5 / 15 mins) 2.02 / 2.04 / 2.05 )
    and also it seems like changing wifi transmit power have no effect at all
     
  79. rockmacaca

    rockmacaca New Member Member

  80. Suva

    Suva LI Guru Member

    Does Shibby Tomato support RT-AC68P? Please let me know ASAP as I want to buy this router. Shibby's website doesn't mention this router.

    http://tomato.groov.pl/?page_id=69

    Thanks
     
  81. eangulus

    eangulus Network Guru Member

    Just wanted to a give a report on my experience with RT-AC68U and Shibby 131.

    I rebuilt my router using exactly the same settings as RT-AC66U Shibby 131.

    For reference, the setup is a Class B network using 10.1.0.254/16 with a PIA VPN with a custom script to direct particular traffic over it or bypass it.

    I also have a fairly decent QoS setup to control all the traffic from my server and a household of 7, so lots of devices including Desktops, Laptops, Tablets, Mobiles, Media Centers, Security Cameras etc.

    Anyway on the RT-AC66U everything is working perfectly. No glitches or anything. 100% solid and stable.

    The RT-AC68U is another story.

    First the QoS doesn't seem to show inbound traffic properly. It seems to show for some things and not others. I don't know what information is needed to help, but what I could see was that the Details list, was missing alot of the rule numbers. While downloading a torrent with the server via a VPN, then starting a download via a browser bypassing the VPN, the download should have push aside the torrents bandwidth. This didn't happen (at least not in the details I could see). Also when checking the transfer rates, the PC download was not showing up.

    To me, the QoS side is only half working. Seems there is still a way to go for a fully functional QoS setup.

    The other issue I found was with the VPN & Script. For details regarding the setup and a copy of the script I have it here: http://www.linksysinfo.org/index.ph...ecific-ports-through-vpn-openvpn.37240/page-3

    On the ARM, it wouldn't work at all unless I ticked the Redirect through VPN option under routing policy. I didn't even have to type in any rules. Then, because I already had a similar rule in my script to point certain traffic over the VPN, my guess is something was duplicated as my logs were then being flooded with this:

    daemon.err openvpn[2011]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #102806 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

    I am only listing these things here as I am finding it hard to find information on exactly how complete the ARM version is. So at this stage I am not sure if these issues are known or not. It may just be that ARM isn't quite ready yet and I have to wait some more before I can use it in my particular setup.

    If anyone needs more information etc, I still have the configuration on the RT-AC68U. I have simply unplugged it and plugged in my RT-AC66U with same config to get my network functioning again. More than happy to help out with debugging or logs etc that may be needed.

    PS: Love Tomato firmware. It's been absolutely awesome to use and I appreciate everyone's hard work.
     
  82. MrDoh

    MrDoh Addicted to LI Member

    From the Changelog:

    [RELEASE] 129
    – add ASUS RT-AC68P support the same image as for AC68U/R – thx @tvlz

    So yes, this support has been added.

    By the way, I really like my RT-AC68P, but use the fork of RMerlin's firmware on it. Works great.
     
  83. LanceMoreland

    LanceMoreland Network Guru Member

    I am happy to report that with Shibby's 131 release for ARM, I no longer need the firewall scripts to make Comcast IPv6 work.


    Edit: I do still need the neighbor table overflow script though.
     
    Last edited: Aug 9, 2015
    jsmiddleton4 and MrDoh like this.
  84. Suva

    Suva LI Guru Member

    Thanks
     
  85. Pentangle

    Pentangle Serious Server Member

    Eangulus, I spent a couple of days with my RT-AC68U tearing what's left of my hair out regarding QoS a couple of weeks ago. Here's what you may not be aware of:

    1) QoS on the RT-AC68U does NOT work if you have any setting in the DSL Overhead Value apart from 'none'.
    2) It was advised elsewhere to remove all of the layer 7 QoS rules in the classification section
    3) The test for whether or not QoS is working on the router is two-fold: a) do you get no traffic showing in the QoS graphs? and b) when you do a Speedtest do you get 100% of your internet line's capability irrespective of QoS and/or bandwidth limiter settings? Once you get proper graphed throughput data and a properly restricted internet line then I think we can say QoS is working as expected. If, however, you've tried all this and you're saying that it's still a bit dodgy despite all this then I'm all ears.

    Mike.
     
  86. eangulus

    eangulus Network Guru Member

    ThHank you for the response.

    I was not aware of the DSL overhead setting. I do usually have it set to something other then nothing.

    Will try again in a few weeks (going to Fiji in a few days for a week) and will report back my findings.
     
  87. compsman

    compsman Serious Server Member

    so i flashed back to shibby, did a proper nvram reset, still only getting a local ):
    rebooted on both native, and dhcpv6 with prefix delegation, still same old problem
     
    Last edited: Aug 9, 2015
  88. MrDoh

    MrDoh Addicted to LI Member

    I'm on Comcast as well...I have found over the years that Comcast is not one big homogeneous network. If you look at how Comcast grew, pasting in new segments that were designed by other companies, you can see that Comcast users in different areas will get different results. And I know for a fact that Comcast only invests in new infrastructure if it absolutely has to for competitive reasons. So IPv6 may work for another Comcast user, but not for you. That's pretty common. I used the scripts, myself, but I'm pretty sure that if I hadn't used the scripts when I configured v131, IPv6 wouldn't have worked for me, either.

    So it goes.
     
    Last edited: Aug 9, 2015
  89. compsman

    compsman Serious Server Member

    funny thing is, if i turn on its internal dhcp lan, its getting ipv6, i switched the modem/router to bridge mode passive changing its ip to a 192.168.100.1
    so i am sure i am hooked up, but i get what your saying, i am in portland oregon, and as i can tell, could be wrong, but i think ipv6 is out and bouncing. i was on dsl for 3-4 years till now, maybe for little longer, sorry for the bother.
     
  90. LanceMoreland

    LanceMoreland Network Guru Member

    It can sometimes takes a while to obtain an IPv6 address when you make changes like that.

    Sent from my LG-H811 using Tapatalk
     
  91. compsman

    compsman Serious Server Member

    well is it native or delegation?
     
  92. LanceMoreland

    LanceMoreland Network Guru Member

    Comcast uses prefix delegation
     
  93. ericsan256

    ericsan256 Network Guru Member

    Running v131 on R7000. Just installed a few hrs ago. The device list doesn't show all the leases. A bunch are missing, but I can ping and connect to the devices on the LAN. Strange.
     
  94. digiblur

    digiblur Networkin' Nut Member

    Reset the devices and they will renew their lease.
     
  95. ericsan256

    ericsan256 Network Guru Member

    Yup - that did it.

    Is there a way to force the election from the router? I know some of the MAC addresses of those not listed in the device list.
     
  96. compsman

    compsman Serious Server Member

    64 prefix, and I can use google's dns?
     
  97. KyleS

    KyleS LI Guru Member

    That's correct, this does not work on ARM because TC hasn't been patched.
     
  98. compsman

    compsman Serious Server Member

  99. MrDoh

    MrDoh Addicted to LI Member

    There's a handy Chrome extension that helps to verify that IPv6 is working, and which sites you're using IPv6 to connect to. The extension is called "IPvFoo", and is very handy to have installed on Chrome if you're playing with IPv6. Don't know if you're using it, but if you're not, and you're using Chrome, try it, you'll like it *smile*.
     
  100. compsman

    compsman Serious Server Member

    it dont work..


    br0 Link encap:Ethernet HWaddr7E:A3:62:98
    inet addr:192.168.0.1 Bcast:192.168.1.255 Mask:255.255.254.0
    inet6 addr: fe80::4216:7eff:fea3:6298/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:8222943 errors:0 dropped:0 overruns:0 frame:0
    TX packets:10827947 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:3498195231 (3.2 GiB) TX bytes:12998007613 (12.1 GiB)

    eth0 Link encap:Ethernet HWaddr :7E:A3:62:98
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:58472484 errors:0 dropped:0 overruns:0 frame:0
    TX packets:55471363 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2201429821 (2.0 GiB) TX bytes:2283818158 (2.1 GiB)
    Interrupt:179 Base address:0x4000

    eth1 Link encap:Ethernet HWaddr 7E:A3:62:98
    UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
    RX packets:1308469 errors:0 dropped:0 overruns:0 frame:6775734
    TX packets:2581363 errors:1 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:81781629 (77.9 MiB) TX bytes:2879569054 (2.6 GiB)
    Interrupt:163

    eth2 Link encap:Ethernet HWaddr 7E:A3:62:9C
    inet6 addr: fe80::4216:7eff:fea3:629c/64 Scope:Link
    UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
    RX packets:169616 errors:0 dropped:0 overruns:0 frame:296750
    TX packets:2274511 errors:154 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:20689669 (19.7 MiB) TX bytes:1245795888 (1.1 GiB)
    Interrupt:169

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
    RX packets:2476 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2476 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:438822 (428.5 KiB) TX bytes:438822 (428.5 KiB)

    vlan1 Link encap:Ethernet HWaddr 7E:A3:62:98
    inet6 addr: fe80::4216:7eff:fea3:6298/64 Scope:Link
    UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
    RX packets:7823699 errors:0 dropped:0 overruns:0 frame:0
    TX packets:10106263 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:3509056188 (3.2 GiB) TX bytes:11960930806 (11.1 GiB)

    vlan2 Link encap:Ethernet HWaddr 7E:A3:62:99
    inet addr:160.175.218 Bcast:67.160.175.255 Mask:255.255.252.0
    inet6 addr: fe80::4216:7eff:fea3:6299/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:10887380 errors:0 dropped:0 overruns:0 frame:0
    TX packets:7669800 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:12887957645 (12.0 GiB) TX bytes:3578978346 (3.3 GiB)

    [​IMG]

    No IPv6 address detected



    Aug 10 06:42:51 Comps-Gateway daemon.warn dnsmasq-dhcp[24061]: no address range available for DHCPv6 request via br0
    over and over
     
  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