What's new

[DSL-AC68U] AsusWrt Merlin builds for DSL routers

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I'm using an DSL-AC68u with the GNUton firmware version 384.12_gnuton1.

I'm new to this, and have had a few issues, although I'm not sure if they're self inflicted. I'm currently using the router as an access point through a borrowed router I'm using as a modem, but these problems seem to be quite persistent and occur whether or not I'm using the AC68u stand-alone or as an access point.

Specifically, I seem to be getting an occasional kernel panic:
May 5 05:05:01 kernel: <1>Unable to handle kernel paging request at virï¾Uª000
May 5 05:05:01 kernel: <1>[e2800018] *pgd=00000000
May 5 05:05:01 kernel: /sys/class/net/vlan1/brport/port_no
May 5 05:05:01 kernel: <4>module: tdts_udbfw bf4fdts bf776000 417017
May 5 05:05:01 kernel: <4>module:module: nf_conntrack_ftp bf769000 4909
May 5 05:05:01 kernel: <4>module: ebt_mark bf763000 814
May 5 05:05:01 kernel: <4>module: ip6table_mangle bf75d000 934
May 5 05:05:01 kernel: <4>modu
May 5 05:05:01 kernel: <4>module: xt_hl bf751000 89 10321
May 5 05:05:01 kernel: <4>module: thfsplus bf7bf69e000 498773
May 5 05:05:01 kernel: <4>module: tfat bf665000 189154
May 5 05:05:01 kernel: <4>module: ext2 bf651000 52776
May 5 05:05:01 kernel: <4>module: ext4 bf610000 221674
May 5 05:05:01 kernel: <4>module: crc16 bf60a000 1007
May 5 05:05:01 kernel: <4>mo
May 5 05:05:01 kernel: <4>module: mbcache bf5bd000 4599
May 5 05:05:01 kernel: <4>module: usb_storage bf5ae000 34290
May 5 05:05:01 kernel: <4>module: sg bfodule: scsi_mod bf56c000 1087hcd bf541000 51132
May 5 05:05:01 kernel: <4>module: 4>module: cdc_wdm bf52d000 7252
May 5 05:05:01 kernel: <4>module: cdc_ncm bf525000 cdc_acm bf507000 12614
May 5 05:05:01 kernel: <4>mo4>module: usbcore bf4da000 102572
May 5 05:05:01 kernel: <4>module: mii bf4d4000 3367
May 5 05:05:01 kernel: <4>module: ebt_ip bf4ce000 1322
May 5 05:05:01 kernel: <4>module: ebtable_broute bf4c8000 873
May 5 05:05:01 kernel: <4>module: ebtable_filter bf4c2000 1061
May 5 05:05:01 kernel: <4>0 4494
May 5 05:05:01 kernel: <4>module: ip6table_filffs2 bf48e000 91274
May 5 05:05:01 kernel: <4>module: zlib_deflate bf484000 19489
May 5 05:05:01 kernel: <4>module: nf_nat_pptp bf47e000 1602
May 5 05:05:01 kernel: <4>module: nf_conntrack_pptp bf478000 3355
May 5 05:05:01 kernel: <4>module: nf_nat_proto_gre bf472000 88: dpsta bf028000 5912
May 5 05:05:01 kernel: <4>module: et bf011000 64930
May 5 05:05:01 kernel: <4>module: igs bf009000 11887
May 5 05:05:01 kernel: <4>mod_udb(P) tdts(P) nf_nat_ftp nf_conntrack_ftp ebt_mark ip6table_macd xhci_hcd cdc_mbim qmi_wwan cdii ebt_ip ebtable_broute ebtable
May 5 05:05:01 kernel: <4>sp : cf39dbd0 ip : 0000002d fp : 00000000
May 5 05:05:01 kernel: <4>r10: c042329 r5 : cf3bdb60 r4 : e2800018
May 5 05:05:01 kernel: <4lags: nzCv IRQs on FIQs on Mobd0 to 0xcf39e000)
May 5 05:05:01 kernel: <0>dbc0: 00000001 cf3bdb60 00000000 cfbb96e8
May 5 05:05:01 kernel: <0>dbe0: 00000000 c037f344 0 00000000 00000000 00000000 bf1c1600 00000000 bf1b866c
May 5 05:05:01 kernel: <0>dc40: cfbd3700 cfb47000 00000000 0000030 00000004 bf180094 cde45400 400ea000 cfbd3700 00000000
May 5 05:05:01 kernel: <0>dc808000 cfb47000 00000003 00000000 c0: 00000000 cfbb99c0 c02e1578 cffffff cf39dd10 cf39dd58 00000020 00000850 ff0a0210 ffffffff
May 5 05:05:01 kernel: <0>c0164f28 00000000 cf091c00 bea3f4c4 cf39dd54 bf36b7e0 bea3f4c4
May 5 05:05:01 kernel: <0>dd40: 000000c4 00000000 bf36b70 00000000 00000000 00000000 0003931 00000029 00000000 00000000 000 00000000 00000000 00000000 000000
May 5 05:05:01 kernel: <0>de20: 00000000 cfbb99c0 00000000 bf160a39dec8
May 5 05:05:01 kernel: <0>de40: cf0b2600 cfbd3700 cf39c000 00000000 00000000 bf1 00000003 00000000 00000004 bea30423abc cf39dec8 c01fc04c
May 5 05:05:01 kernel: <0>dea0: c005a02c 00000084 c81ae760 00000000 ca488000 cde49160 cdf3d160 40046000
May 5 05:05:01 kernel: <0>dec0: c0411598 cfae3d40 31687465 00000000 00000000 00000000 bea3f5a8 4003aa44
May 5 05:05:01 kernel: <0>d588 bea3f588
May 5 05:05:01 kernel: <0>df00: 00000003 c003dc68 cf39c000 00000000 00000000 c00d86e8 00000020 cb295e58
May 5 05:05:01 kernel: <0>df20: cf39df58 00000003 00000000000 c0363894 cf8073c0 00000003
May 5 05:05:01 kernel: a3f3f4 40191730 00000003 000000091730 00000003 00000003 000089f000000000 00000000 bea3f588 00000c)
May 5 05:05:01 kernel: <4>[<c037bca4>] (put_page+0x8kb+0x28/0x1dc)
May 5 05:05:01 kernel: <4>[<c037f038>] (ec)
May 5 05:05:01 kernel: <4>[<c038e91c>] (osl_pktfree+0x1c4/0x1ec) from [<bf1c1600>] ])
May 5 05:05:01 kernel: <4>[<bf1c1600>] (wlc_bsscfg_d80094>] (wlc_down+0x27c/0x318 [wl])
May 5 05:05:01 kernel: <4>[<bf180094>] (wlc_down+0x27c/0x318 [wl]) from [<bf15abfc>] (wl_down+0x88/0x198 [wl])
May 5 05:05:01 kernel: <4>[<bf15abfc>] (wl_down+0x88/0x198 ctl+0x1034/0x3210 [wl])
May 5 05:05:01 kernel: <4>[<bf1octl+0x140/0x1b4 [wl])
May 5 05:05:01 kernel: <4>[<bf160x21c/0x288 [wl])
May 5 05:05:01 kernel: c/0x3cc)
May 5 05:05:01 kernel: <4>[<c01fba38>] (dev_if<c01fc04c>] (dev_ioctl+0x5d4/0x7ctl+0x80/0x5d0)
May 5 05:05:01 kernel: <4>[<c00d86e8>] 8/0x60) from [<c003dac0>] (ret_f00 (e5903000)
May 5 05:05:01 kernel: <4>---[ end trace panic - not syncing: Fatal exception in interrupt
May 5 05:05:01 kernel: <4>[<c0043ff8>] (unwind_backtrace+0x0/0xf8) fa8)
May 5 05:05:01 kernel: <4>[<c02cff5c>] (panic+0x7c/0x6c/0x8c) from [<c0045448>] (do_translation_fault+0x70/0xa8)
May 5 05:05:01 kernel: <4>[<c0045448>] (do_translation_fault+0x70/0xa8) from [<c003d3a4>] (do_DataAbort+0x30/0x9c)
May 5 05:05:01 kernel: <4>[<
May 5 05:05:01 kernel: ____________________________________________________________________________

For reference I am attaching the rest of the logs for the past two days (hopefully with the MACs removed (as hidden Mac).

I've been using this firmware since release, but seem to have been having similar issues since I installed it. I've re-flashed it a couple of times (after resetting to factory and clearing the NVRAM, and also installed the stock firmware, updated, and then moved back to this, but the issue persists.

I'm only a beginner, so I might have picked a ridiculous internal IP or just done something a bit dumb. I've got about a month's worth of logs that I can search through if it would help.


I've had a closer look and found something that doesn't look right. Do you think this is related?


Sep 7 15:03:39 rc_service: httpds 226:notify_rc stop_ddns;start_asusddns_unregister

Sep 7 15:03:40 inadyn[2080]: In-a-dyn version 2.5 -- Dynamic DNS update client.

Sep 7 15:03:40 inadyn[2080]: /etc/inadyn.conf:4: unexpected token '='

Sep 7 15:03:40 inadyn[2080]: Parse error in /etc/inadyn.conf

Sep 7 15:03:40 syslog: Error code 74: Missing .conf file



Kind Regards


Rob
 
Last edited:
unfortunately I don't have any other aimesh devices so I can not test the functionality.
Everything else is working fine so far.
 
has anyone connect the router in aimesh node mode using the latest image?
I just installed the alpha5 firmware, and haven't had any success setting it up as an AINode.
Flashed, factory reset and rebooted it while sitting out next to my AIMesh router (rt-ac86u). The router just doesn't find any new mesh nodes. (I have an existing rt-ac68u acting as a node already)
 
I just installed the alpha5 firmware, and haven't had any success setting it up as an AINode.
Flashed, factory reset and rebooted it while sitting out next to my AIMesh router (rt-ac86u). The router just doesn't find any new mesh nodes. (I have an existing rt-ac68u acting as a node already)
thanks for the confirmation, I have the same arrangement the RTAC68U is connected as a node to RT-AC86U however the DSL-AC68U can not be detected via the Aimesh search.

Looking at the Asus website (might be old info), it does state that DSL model can only act as master in Aimesh network...

the AC86U is better router and I want to use this as master
 
Looking at the Asus website (might be old info), it does state that DSL model can only act as master in Aimesh network...
That would only refer to the stock firmware.
I have no idea why it would technically not be able to become a node given that the software were written as such.

Perhaps Asus thought it wouldn't be a good idea since the DSL model lacks a dedicated WAN port and can't use Ethernet backhaul.
 
try stock beta - should support DSL as Aimesh-node/child: https://www.snbforums.com/threads/d...eleased-with-aimesh-node-child-support.57737/
There is no need for Merlin on nodes.
Well, I didn't even know that beta existed! Thanks for the pointer.
Totally agreed that Merlin is not required on nodes, but at the time that appeared to be my only option for adding node support to the spare DSL router.

That being said, I can now add the dsl-ac68u to as a node, but it then fails to actually function as a node once added. Probably a beta problem though and I will take that problem elsewhere than this thread :).
 
Just a heads up that the official update 3.0.0.4.384_81140 was just released and this one supports operation as a AIMesh Node (and it actually works!).
 
anyone try this new stock firmware yet? Any DSL modem driver updates included?

I was thinking about giving it a shot until 384.13-gnuton is released.
 
anyone try this new stock firmware yet? Any DSL modem driver updates included?
I'm using it and it is running perfectly as a AIMesh Node with WiFi backhaul.
The release notes don't make any mention of any DSL firmware updates.
 
I'm using it and it is running perfectly as a AIMesh Node with WiFi backhaul.
The release notes don't make any mention of any DSL firmware updates.

if you take a look under System log, then DSL log, you will see the version information. Well, under Merlin, that’s how you do it


DSL Firmware Version. 1.0.4.7
DSL Driver Version FwVer:5.5.2.10_A_A60901 HwVer:T14.F7_0.2

Could you post that info from the latest stock firmware that you’re running?

thanks...
 
if you take a look under System log, then DSL log, you will see the version information. Well, under Merlin, that’s how you do it


DSL Firmware Version. 1.0.4.7
DSL Driver Version FwVer:5.5.2.10_A_A60901 HwVer:T14.F7_0.2

Could you post that info from the latest stock firmware that you’re running?

thanks...

From my (stock) modem firmware logs;

Current Version : 3.0.0.4.384_81140-g9f3e378
DSL Firmware Version 1.0.4.9
DSL Driver Version FwVer:5.5.2.11_A_A60901 HwVer:T14.F7_0.2
 
Would it be possible to get it running on the ASUS DSL-AC68VG VOIP model?
unfortunately, it doesn't run AsusWRT firmware so let merlin run there is not that easy..

But on the (german) ASUS Homepage they tell about AsusWRT for this DSL-AC68VG VOIP model... This is the reason why i ordered this model yesterday.
PLEAS tell my, that MERLIN would be possible there *damn*
I would LOVE to have MERLIN on this model !!!!
 

Attachments

  • Unbenannt.jpg
    Unbenannt.jpg
    45.9 KB · Views: 434
But on the (german) ASUS Homepage they tell about AsusWRT for this DSL-AC68VG VOIP model... This is the reason why i ordered this model yesterday.
PLEAS tell my, that MERLIN would be possible there *damn*
I would LOVE to have MERLIN on this model !!!!
you can write your own fork, nobody would do many days/weeks of work for you, if possible at all.
 
you can write your own fork, nobody would do many days/weeks of work for you, if possible at all.
Okay :) Many thanks for the answer.
But unfortunately I am not that experienced :(

But I still have an AC-R68U with merlin at home.
Due to ISP change, I have to use a DSL with VOIP as a modem.

I could put this one behind, but then I would have double NAT and loss of speed I think ??

Ai ai ai ... :(

Anyway: Thanks for the answer and the work. I'm happy for everyone else who can use merlin here as well ...
 
But unfortunately I am not that experienced :(
no one is ..
I could put this one behind, but then I would have double NAT and loss of speed I think ??
Not really loss of speed, maybe 1ms on ping and more work with port forwarding if neccessary.
You can use DSL in modem-only mode (bridge mode), so it does no routing and you have to setup your router to make connection to ISP. So you avoid double NAT.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top