[Release] Asuswrt-Merlin 380.68 is available

[raduzl74]

Use fq_codel I know pppoe has an overhead of 8 bytes

Thanks!

And what about WAN packet overhead? Any recommendation?

 

[Vexira]

Thanks!

And what about WAN packet overhead? Any recommendation?

I was going to suggest 8 since I'm not sure of your exact setup, as in pppoe mtu, etc, give 18 a go, or 8, but I'm sure there is no overhead, on fiber as in fiber direct o the house. so at worst you most likely don't need to set it to anything and leave it at 0. have a read of what I linked it might help.
https://forum.lede-project.org/t/pppoe-over-fiber-overhead-question/3343/34

 

[RMerlin]

The overhead value is really for extreme tweaking, do not sweat too much over it. It's only intended to ensure higher accuracy when calculating the max bandwidth to allocate for each classes.

Had I known it would cause so much confusion, I wouldn't have exposed the parameter to the webui.

 

[mocchii2000]

In version 380.68, it disappears when selecting the setting value "merlin" of the Nat loopback function.
It has not been fixed in 380.68_2.
It worked normally at 380.67.

 

[Lightfeather]

Hey there, I'm not sure where to post this so here's hoping I guessed correctly. I just installed the newest build 380.68_2 as I had to reset my router to factory default because in my infinite wisdom, I changed my router password and entrusted it to LastPass password manager. LastPass ate my password and I was locked out of my router. I found the password hash in my registry and deciphered it and realized that the router software allowed me to actually create a password that was TOO LONG to be accepted in the login page. The password turned out to be correct, but I couldn't actually use it because the login field wouldn't accept a 25 character password. It stopped accepting input at like 16 or something. (Not sure if you can do anything about that, but there it is.)

Anyhow, I thought when I factory reset I'd have to start with a fresh, outdated Asus software, requiring me to upgrade it to the current Asus software build, then flash it to Merlin. I was surprised to find Merlin was still the default software after everything got reset and I was able to set a new router password quickly. Which was nice.

Long story short. I go through all my settings and when I got to the VPN page, I set it up so that everything has to go through the VPN except some random things like the Ooma, Roku devices as well as handheld and console gaming devices.

Everything was going fine... until I set 'Redirect Internet Policy' to 'Policy Rules' and started entering rulesets.

I was able to add four exceptions that were supposed to go through WAN only. I would hit apply after each entry and test it out to make sure it worked before moving onto the next. On that fifth entry, I stupidly used an apostrophe in the description field. (Lightfeather's 3DS). After clicking APPLY that apostrophe destroyed the whole page. Just fudged it up.

* The entire header and side navigation are gone from the page.
* The ability to toggle the VPN on and off is gone.
* Various other toggles are missing.
* Various warning messages are popped up near radio buttons and text fields.
* All my 'Rules for routing client traffic through the tunnel' are missing, yet everything seems to be fine in function. I just can't see the entries.

I'll add screenshots.

So in conclusion. I'm sort of stuck about what to do right now. I am not sure how to edit whatever file I need to edit to remove that one stupid entry containing an apostrophe so my VPN settings page will become functional again.

I can either reset the router again and spend another three hours setting the GD thing back up, or hope you have a quick solution to fix the apostrophe problem so I can flash an upgrade and my page will parse correctly so I can manipulate it. =(

This is my punishment for being grammatically correct.

Halp! What do!?

 

[john9527]

Halp! What do!?

Exit the router gui, and telnet or ssh to the router and enter (assuming you are working with the first VPN client instance)

nvram unset vpn_client1_clientlist
nvram commit

You can then restart the gui, and start fresh setting up the VPN policy rules.

 

[Lightfeather]

Thanks for the quick response! I'll have to try it tomorrow because if I screw up the router again right now, and drop the internet, an angry household will be out for my blood. Since everything is working right now tinkering will have to wait, unfortunately.

I used telnet years ago and I've never used ssh, and I know just enough about networking to get myself into trouble, but I'm sure I can figure it out. I did indeed use client1 so that should work fine. I took screenshots of all my VPN settings after they were confirmed working, so redoing that page will just be "plug and play"... hopefully. Ha.

 

[Lightfeather]

I waited till everyone went to bed, then started messing with it and I managed to enable telnet client on my machine since it wasn't. Then enabled telnet on the router because that radio button wasn't set either.

I was finally able to log in to the router via cmd and ran those two commands you provided. First one line, then I hit enter. Then the next one to apply those changes I assume. I didn't get any sort of confirmation that anything happened, but I didn't get any errors either. I dumped the cmd window and logged in via the gui, but the vpn settings page was still a mess. I tried refreshing the page, then logged out, cleared the browser cache, and re-logged in.

Either I didn't perform the operation correctly, or there's something else wrong. Is there a command to wipe that whole page and redo the vpn page completely? The default button is non functional, as is the apply button. Most of the stuff on that page isn't able to be manipulated. =/

EDIT: Looking back, I'm only assuming the apostrophe is the cause of all this. It seemed the most likely culprit, because they tend to screw up a lot of stuff if not parsed correctly... but maybe the VPN page will barf when you get to the fifth entry regardless of text box content? I can't test that theory until I can put the page back to rights though. In the end, I actually have no real clue as to what caused the page to mutilate itself.

EDIT2: Uploaded a screen of evidence that the content isn't purging from the list. It seems the page may not be recognizing itself as vpn client1 or something. It lost the identifying dropdown at the top of the page so I'm not sure. I'm thinking I may have to blow the router up and try again. Omg, shoot me.

 

[SmallNetGuy]

What is the rule of thumb for doing full NVRAM resets between versions? Watch the changelog and it should say it? Or always do it? Or not needed when moving between minor versions e.g. 380.68_0 to 380.68_2?

From the README-merlin.txt file supplied with every single firmware package coming from Merlin:

Installation
------------
Simply flash it like any regular update. You should not need to
reset to factory defaults (see note below for exceptions).
You can revert back to an original Asus firmware at any time just
by flashing a firmware downloaded from Asus's website.

If the firmware upgrade fails, try rebooting your router to free
up sufficient memory, without any USB disk plugged in,
then try flashing it again.

NOTE: resetting to factory default after flashing is
strongly recommended for the following cases:

- Updating from a firmware version that is more than 3 releases older
- Switching from a Tomato/DD-WRT/OpenWRT firmware

If you run into any issue after an upgrade and you haven't done so,
try doing a factory default reset as well.

Always read the changelog, as mandatory resets will be mentionned
there when they are necessary.

In all of these cases, do NOT load a saved copy of your settings!
This would be the same thing as NOT resetting at all, as you will
simply re-enter any invalid setting you wanted to get rid of. Make
sure to create a new backup of your settings after reconfiguring.

 

[Lightfeather]

Thank you! Reflashing it fixed the broken page and all my list entries were gone, like they should be so I can enter them in this time with 100% less apostrophes, and hope that will fix the problem.

I started using asuswrt merlin just a few weeks ago with version 380.68_0. I read all the documentation during that install, paranoid I was going to brick my router.

When this update came out, I freshly recall the process was easy, so I didn't reread the documentation. I wish I had. But even so, I probably wouldn't have considered a reinstall as a potential solution to a borked page. (I seem to always do everything the hard way.)

I appreciate the help very much! =) (Even though your response was to someone else, totally helped me out too.)

 

[beboptrumpet]

Works correctly for me. Try disabling NAT acceleration, then observe if new data is correctly populated.

Someone else mentioned it is a known issue when IPv6 is enabled.
Nevertheless, I tried your suggestion
Updated to 380.68-2 on my rt-ac87
turned off NAT acceleration (IPv6 is on)
Streamed video for a while & observed
Still seeing transmission & reception flip flopped

Oddly enough, while it is erroneous on the "traffic monitor" tab,
it is correct on the "statistics" tab

 

[Pir8pete]

bug found?

Router reboots when i'm using BitTorrent

Jul 31 20:00:12 kernel: _ Reboot message ... _______________________________________________________
Jul 31 20:00:12 kernel: <1>Unable to handle kernel NULL pointer derefere�U�at virtual address 00000001
Jul 31 20:00:12 kernel: <1>p=00000000
Jul 31 20:00:12 kernel: <0>Internal error: Oops: 17 [#1] PREEMPT SMP
Jul 31 20:00:12 kernel: <0>last sysfs file: /sys/devices/pci0000:00/0000:00:0c.0/usb1/1-1/1-1:1.0ard     bf7c4000     93980
Jul 31 20:00:12 kernel: <4>module:  IDP     bf738000     529190
Jul 31 20:00:12 kernel: <4>module:  nls_cp437     bf731000     4474
Jul 31 20:00:12 kernel: <4>module:  nf_nat_ftp     bf72b000     1144
Jul 31 20:00:12 kernel: <4>module:  nf_conntrack_ftp     bf724000     4909
Jul 31 20:00:12 kernel: <4>module:  ip6table_mangle     bf71e000     934
Jul 31 20:00:12 kernel: <4>m<4>module:  cdrom     bf6fc000     30901
Jul 31 20:00:12 kernel: <4>module:  xt_length     bf6f6000     769
Jul 31 20:00:12 kernel: <4>module:  cdc_mbim     bf6e4000     3129
Jul 31 20:00:12 kernel: <4>module:  qmi_wwan     bf6dd000     5780
Jul 31 20:00:12 kernel: <4>module:  cdc_wdm     bf6d6000     7252
Jul 31 20:00:12 kernel: <4>module:  cdc_ncm     bf6ce000     8750
Jul 31 20:00:12 kernel: <4>mod
Jul 31 20:00:12 kernel: <4>module:  cdc_ether     bf6c1000b0000     11161
Jul 31 20:00:12 kernel: <4>module:  mii     bf6aa000     3367
Jul 31 20:00:12 kernel: <4>module:  usblp     bf6a2000     10321
Jul 31 20:00:12 kernel: <4>module:  ohci_hcd     bf698000     17918
Jul 31 20:00:12 kernel: <4>module:  ehci_hcd     bf68b000     31565
Jul 31 20:00:12 kernel: <4>module:  xhci_hcd     bf678000     51124
Jul 31 20:00:12 kernel: <4>module:  thfsplus     bf65c000     81793
Jul 31 20:00:12 kernel: <4>module:  tntfs     bf5e05a7000     188546
Jul 31 20:00:12 kernel: <4>module:  ext2     bf593000     52776
Jul 31 20:00:12 kernel: <4>module:  exte:  ext3     bf517000     106409
Jul 31 20:00:12 kernel: <4>moodule:  mbcache     bf4ff000     4599
Jul 31 20:00:12 kernel: <4>module:  usb_storage     bf4f0000     34290
Jul 31 20:00:12 kernel: <4>module:  sg     bf4e5000     19855
Jul 31 20:00:12 kernel: <4>module:  sd_mod     bf4>module:  usbcore     bf48b000     101810
Jul 31 20:00:12 kernel: <4>module:  ip6t_LOG     bf484000     4494
Jul 31 20:00:12 kernel: <4>module:  ip6table_fijffs2     bf460000     91274
Jul 31 20:00:12 kernel: <4>module:  zlib_deflate     bf456000     1948900     1602
Jul 31 20:00:12 kernel: <4>module:  nf_conntrac:  nf_nat_proto_gre     bf444000     8e:  igs     bf02a000     11887
Jul 31 20:00:12 kernel: <4>module:  emf     bf021000     15225
Jul 31 20:00:12 kernel: <4>module:  et     bf00a000     61445
Jul 31 20:00:12 kernel: <4>mod bw_forward(P) IDP(P) nls_cp437 t(P) ext2 ext4 crc16 jbd2 ext3 jbd mbcache usb_storage sg sd_mod ip6t_LOG ip6table_filter jffs2 zlib_deflate nf_nat_pptp nf_conned: ip6t_REJECT]
Jul 31 20:00:12 kernel: inted: P             (2.6.36.4brcmarm #2)
Jul 31 20:00:12 kernel: <4>PC is at ip_conntrack_ipct_resume+0x150/0x350
Jul 31 20:00:12 kernel: <4>LR is at 0xc66560f5
Jul 31 20:00:12 kernel: <4>pc : [<c022p : 00000010  fp : 00000001
Jul 31 20:00:12 kernel: <4>r: c7b4c12c
Jul 31 20:00:12 kernel: <4>r7 : 00000006  r6 : 00000001  r5 : c03c1c08  r4 : c97c1b40
Jul 31 20:00:12 kernel: <4>r3 : 0000000a  r2 : 00000000  r1 : c7b4c154  r0 : c03c1c1c
Jul 31 20:00:12 kernel: <4>Flags: nZcv  IRQs on  egment kernel
Jul 31 20:00:12 kernel: <4>Control: 10c53c7d  Table: 9c74004a  DAC: 000000tack limit = 0xc03c0270)
Jul 31 20:00:12 kernel: <0>Stac                             00000000 bf000ed8
Jul 31 20:00:12 kernel: <0>1800: 00000006 0000ec2f 0000e259 bf000ed8 c03c185c bf0049cc c03c1868 00000006
Jul 31 20:00:12 kernel: 888 bf000fcc 00000006 0000ec2f 0000e259 c03c1c68
Jul 31 20:00:12 kernel: <0>1840: bf00492
Jul 31 20:00:12 kernel: <0>1860: 00000001 00000000 000 00000000 8738894f
Jul 31 20:00:12 kernel: <0>1880: 000000000006 00000000 00000000 000000000000 00000000 00000000 000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul 31 20:00:12 kernel: <0>1900: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul 31 20:00:12 kernel: <0>1920: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul 31 20:00:12 kernel: <0>1940: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Jul 31 20:00:12 kernel: <0>1960: 00000000 03b9aca0 f7b70740 00000000 00000000 0000001c 87b70740 00729e87
Jul 31 20:00:12 kernel: <0>1900163a9 38074fe1 000163a9 00989680 00000000
Jul 31 20:00:12 kernel: <0>19a0: 00000000 00989680 00253d6f 00000000 c0413630 cf9d0300 00000001 cf9d0300
Jul 31 20:00:12 kernel: <0>19c0: 00000001 cf9d0300 c8225f80 00000000 00000101 cf9d0330 c03c1a04 c0059cd4
Jul 31 20:00:12 kernel: <0>19e0: 00000000 cf9d0300 c8225f80 c8225f80 cf9d0300 c8225f80 00000002 c02cfea8
Jul 31 20:00:12 kernel: <0>1a00: c003b040 c00429d0 c02cfea8 cf9d0300 c03c0000 c8225f80 00000000 00000001
Jul 31 20:00:12 kernel: <0>1a20: 00000001 c0416cbc cf9d0300 c005cfd4 c003bf80 00000003 38074ab0 a0000193
Jul 31 20:00:12 kernel: <0>1a40: 40000113 c8225240 40000113 cf815060 cf84bce8 cf84bbb4 00000008 bf017fc4
Jul 31 20:00:12 kernel: <0>1a60: bf0166bc c0074378 cf84bce8 cf815060 00000001 00000002 cf99a1c0 ce ^C00
Jul 31 20:00:12 kernel: <0>1a80: 0000001d c03896c8 c80f9d20 00000110 00000630 bf7cfaac c7b4c250 cf9f6400
Jul 31 20:00:12 kernel: <0>1aa0: cf84bb80 c03896c8 cec5a0e0 cf84b800 c041decc cf9f9c00 00000008 00000000
Jul 31 20:00:12 kernel: <0>1ac0: bf0166bc c037bab0 00000068 00000053 00000000 cecb7200 cf84b800 cecb725c
Jul 31 20:00:12 kernel: <0>1ae0: cec5a0e0 cf9f9c00 00000008 cecb7200008e
Jul 31 20:00:12 kernel: <0>1b00: c7ae715c c0379914 cecb725c cf9f9c00 79f87d83 cb83da80 00000000 000004f8
Jul 31 20:00:12 kernel: <0>1b20: 0000008e 000004f8 cb83da80 0000008e 1ec3e9c0 00000586 000004f8 c0379b30
Jul 31 20:00:12 kernel: <0>1b40: 0000055e 00000011 98bc6743 cdf73d20 00000000 c0: c0228ae0 c97c1bb4 00000003 0000003 cdf73d20 c0226994 c97c1b40 c97c1bac 0000000a c041dabc
Jul 31 20:00:12 kernel: <0>1800 c02ace90
Jul 31 20:00:12 kernel: 0 cc6e5640 00000000 cf9f9ba0 bf0<0>1c20: 16f0dfe2 fd0c57fd c66560416cbc c03c0000
Jul 31 20:00:12 kernel: <0>1c40: c003d434 00000003 c97c1b40 cec542a0 c003d434 bf7c51c8 00000000 00000000
Jul 31 20:00:12 kernel: <0>1c60: c0283a9c c03c1ce4 c041e788 fffffe71 cec542a0 000000003a9c c037c30c c0283a9c 00000000 00000000 00000000 00000000 cec5403c1ce4 00000000 c041e788 c0223c283a9c fffffe71 00000000 c03c1ce4 c03c1cf4 0000000a c0412914 c03c0000
Jul 31 20:00:12 kernel: <0>1ce0: c9bbb000 bf7d8f4c c0421f90 cec542a0 cdf73d20 ce09cf84b800 fffffe71 00000000 c02af930 00000000 c0283a9c fffffe71 00000000
Jul 31 20:00:12 kernel: <0>1d20: bdea5d59 cdf73de4 c0283a9c 00000000 00000000 ce4b800 c0283a9c c02ae828 c0283a9c1dd4 c041e788 80000000 ce097700 80: 00000000 00000000 00000000 ce097700 cf84b800 c0283a9c c03c1dd4 00000000
Jul 31 20:00:12 kernel: <0>1da0: c041e788 c0223c88 00000000 c03c1dd4 c0283a9ce097700 c03c0000 cfbb7400 c041dabc c0416cbc cf84b800 c028403c
Jul 31 20:00:12 kernel: <0>1e00: 00000000 c0283a9c 80000000 00000000 c7ae711e ce097700 c000000 c01f8140 c7ae711e c03c000077c4 c7ae711e c7ae7124 00000000 700 c82164b4 00000000 00000001 00200200 c041df98 00100100 c037afd8
Jul 31 20:00:12 kernel: <0>1e80: 00000000 00000000 ce097700 c041df6c c82164b4 0000000040 0000012c c82164a0
Jul 31 20:00:12 kernel: <0>1ee0: ce4 cf84bcac c03c0000 c006703c 0011f20 00000000 c0387108
Jul 31 20:00:12 kernel: <0>1f20: 00000000 00000000 00000003 00000009 c03c7abc c03c0000 c0416cbc c003b9d0
Jul 31 20:00:12 kernel: <0>1f40: c03c0000 0000
Jul 31 20:00:12 kernel: ____________________________________________________________________________

 

[Pir8pete]

@RMerlin - kernel: <0>Internal error: Oops:

you copy?

I have posted this error with your other "stable versions" got no reply and here it appears again in this version ;/

 

[RMerlin]

@RMerlin - kernel: <0>Internal error: Oops:

you copy?

I have posted this error with your other "stable versions" got no reply and here it appears again in this version ;/

Kernel crashes can occur for any number of reason, and I can't debug these unless they can be reproduced while someone has a serial connector hooked in.

Since I don't see any widespread report, it's possible your router might be suffering from hardware issues.

 

[PorscheT]

Great release Merlin. No issues at all with AC56U and AC88U.

 

[Pir8pete]

Kernel crashes can occur for any number of reason, and I can't debug these unless they can be reproduced while someone has a serial connector hooked in.

Since I don't see any widespread report, it's possible your router might be suffering from hardware issues.

thx for the reply, I did see another post that they had the same issue but it was only the one I ever seen

 

[ankhazam]

thx for the reply, I did see another post that they had the same issue but it was only the one I ever seen

Yeh... I'm also experiencing (sometimes) crash when my BitThief starts to resolve pasted magnets... the router reboots... and afterwards no crash till the end of the torrent... possibly TrendMicro goes panic mode

 

[JIPG]

Hi Merlin,

Although I have been following this forum for some time, it is my first trial with your firmware, and I can only say it is a very nice piece of software. I was afraid it is not the official FW, but at the end, it works flawlessly and seems much better than the official one with the new features. So, thank you for your valuable work!
I have installed 380.68_2 in an RT AC87U, without any of the problems some people report, just resetting to default values, and switching off the router for a while after the update, introducing from scratch my configuration to avoid problems with the variables (seems to be the best way).

Just for information, these are my first impressions:
I have no problems with Wifi (I use fixed channels in both 2.4 and 5 GHz bands), network map is OK with ethernet ports correctly populated in the table, I see correct signature version with date, not long log, no big memory usage (I do not use VPN), not GUI freezing, just to mention some of problems reported for other forum members, so very happy with it!
By the way, the infamous bug in WPS for the 5 GHz band (marked as OFF but really ON) it is still here (ASUS problem, not Merlin), but switching it on and off twice solves the problem up to the next reboot.
The only minor glitch I have found in the GUI is in the AiProtection Page-Parental control (see image below, marked in red). The tabs problem occurs in Firefox, IE and Safari. Anyway is only cosmetic and not affect in selecting the tab

Again, a big thanks for your great effort!

 

[RMerlin]

The only minor glitch I have found in the GUI is in the AiProtection Page-Parental control (see image below, marked in red).

This issue was introduced by the move to the new menu system (some CSS classes have changed names). It's currently fixed in the new 382 codebase.

 

[MrEprize]

Yeh... I'm also experiencing (sometimes) crash when my BitThief starts to resolve pasted magnets... the router reboots... and afterwards no crash till the end of the torrent... possibly TrendMicro goes panic mode

I also have this problem with torrents, I use Tixati though. I kinda think it is Trend Micro related. It seems to not like *.ru sites all of a sudden. Going back to 380.66_6 seems to alleviate the problem somewhat. With the latest 380.68_2 it will just constantly reboot unless I stop the torrent client.