ASUS DSL-AX82U IPv6 Issue

[Black Bird]

Current FW Version : 3.0.0.4.388_22048-gf313579

When I activate IPv6, the device does not detect the Internet presence and blocks the internet access of other devices (DHCP passive access point).
The settings that worked before were adjusted again in the same way, but they failed.

IPv6
Basic Config > WAN Selection >WAN
Connection type > Passthrough
Interface > PPP

WAN > Dual WAN > Auto Network Detection > Detect Interval Every 8 seconds

Share the knowledge

Attachments:

1. 

   0001.jpg
   

2. 

   0002.jpg
   

3. 

   0003.jpg
   

You need to login in order to vote

[vitt13]

Black Bird wrote:

I set it up again by taking it to the factory settings, there is a problem.

 

Do you really need “Dual WAN” ?

here is my settings:

 

 

Share the knowledge

Attachments:

1. 

   Screenshot.png
   

Liked by:

You need to login in order to vote

[vitt13]

I’ve just activated IPv6, all is working fine, connection shows as connected no issues,

by the way, I have a direct DSL connection (VDSL),

my advice is keep IPv6 deactivated, it brings more problems in my view

Share the knowledge

Attachments:

1. 

   IPv6.png
   

Liked by:

You need to login in order to vote

[UK Sentinel]

If IPv6 is enabled on your DSL-AX82U – if you use a windows PC, go to CMD and type IPCONFIG

What are the results ? (block out first two octets)  etc.

Share the knowledge

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Black Bird]

I barely got this print out because of the constant presence and absence.

Share the knowledge

Attachments:

1. 

   IPCONFIG.jpg
   

You need to login in order to vote

[UK Sentinel]

All you IPv6 screen dumps look good, do you need DUAL WAN, if not as @Vitt13 said, disable it to see if the bug is the DUAL WAN setting ?

Share the knowledge

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Black Bird]

UK Sentinel wrote:

All you IPv6 screen dumps look good, do you need DUAL WAN, if not as @Vitt13 said, disable it to see if the bug is the DUAL WAN setting ?

No, I don’t normally use it, the last time I reset it I turned on to set up WAN (because this is a modem, DSL is the default). This issue persists when Dual WAN is off. It’s constantly taking IP and releasing it.

last night modem log

Dec 31 00:39:49 pppd[9546]: Connect: ppp0 <–> wan0
Dec 31 00:39:50 pppd[9546]: PAP authentication succeeded

Dec 31 00:40:31 WAN(0) Connection: WAN(0) link down.

Dec 31 00:40:38 pppd[11074]: Connect: ppp0 <–> wan0
Dec 31 00:40:39 pppd[11074]: PAP authentication succeeded

Dec 31 00:41:19 WAN(0) Connection: WAN(0) link down.

Dec 31 00:41:28 pppd[12502]: Connect: ppp0 <–> wan0
Dec 31 00:41:29 pppd[12502]: PAP authentication succeeded

 

 

current modem log

 

Dec 31 18:19:38 WAN Connection: WAN was restored.

Dec 31 18:20:05 WAN Connection: Fail to connect with some issues.

Dec 31 18:24:13 WAN Connection: WAN was restored.

Dec 31 18:24:41 WAN Connection: Fail to connect with some issues.
Dec 31 18:27:00 WAN Connection: WAN was restored.

Dec 31 18:27:27 WAN Connection: Fail to connect with some issues.
Dec 31 18:28:06 WAN Connection: WAN was restored.

Dec 31 18:28:34 WAN Connection: Fail to connect with some issues.
Dec 31 18:29:01 WAN Connection: WAN was restored.

 

Share the knowledge

Attachments:

1. 

   dwoff.jpg
   

2. 

   Internet.LED.jpg
   

You need to login in order to vote

[UK Sentinel]

After disabling Dual WAN, reboot rooter and see if that helps.

Is there any logs that suggest a problem ?

Share the knowledge

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Black Bird]

The status has not changed, more modem logs are as follows. I replaced the special parts with ff)

 

May 5 08:05:41 pppd[1861]: PAP authentication succeeded
May 5 08:05:41 pppd[1861]: peer from calling number ff:ff:ff:ff:ff:ff authorized
May 5 08:05:41 pppd[1861]: local LL address fe80::ffff:ffff:c006:83fc
May 5 08:05:41 pppd[1861]: remote LL address fe80::ffff:ffff:fe0d:bfc0
May 5 08:05:41 pppd[1861]: local IP address 100.82.178.86
May 5 08:05:41 pppd[1861]: remote IP address 172.17.1.250
May 5 08:05:41 pppd[1861]: primary DNS address 193.192.98.8
May 5 08:05:41 pppd[1861]: secondary DNS address 212.154.100.18
May 5 08:05:41 rc_service: ipv6-up 2006:notify_rc start_rdisc6
May 5 08:05:41 rc_service: ipv6-up 2006:notify_rc start_dhcp6c
May 5 08:05:41 rc_service: waitting “start_rdisc6” via ipv6-up …
May 5 08:05:41 miniupnpd[1749]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 5 08:05:41 wan: finish adding multi routes
May 5 08:05:42 miniupnpd[1749]: shutting down MiniUPnPd
May 5 08:05:42 miniupnpd: it is advised to use network interface name instead of 10.1.1.1/255.255.255.0
May 5 08:05:42 miniupnpd[2058]: HTTP listening on port 35093
May 5 08:05:42 roamast: ROAMING Start…
May 5 08:05:42 rc_service: ip-up 2009:notify_rc start_tr
May 5 08:05:42 miniupnpd[2058]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 08:05:42 TR-069 agent: version match
May 5 08:05:43 usb: USB ntfs fs at /dev/sda mounted on /tmp/mnt/ffff.
May 5 08:05:43 asusware: umount partition /dev/sda…
May 5 08:05:43 disk monitor: unmount partition
May 5 08:05:43 hotplug: USB partition unmounted from /tmp/mnt/ffff
May 5 08:05:43 asusware: Automatically scan partition /dev/sda…
May 5 08:05:43 disk monitor: scan partition
May 5 08:05:44 asusware: re-mount partition /dev/sda…
May 5 08:05:44 disk monitor: re-mount partition
May 5 08:05:44 usb: USB ntfs fs at /dev/sda mounted on /tmp/mnt/ffff.
May 5 08:05:44 asusware: done.
May 5 08:05:44 disk monitor: done
May 5 08:05:49 kernel: [ 61.361936] SHN Release Version: 2.0.2 d2ff630
May 5 08:05:49 kernel: [ 61.366428] UDB Core Version: 0.2.20
May 5 08:05:49 kernel: [ 61.390387] sizeof forward pkt param = 192
May 5 08:05:49 BWDPI: fun bitmap = 43f
May 5 08:05:55 transmission-daemon[3520]: UDP Failed to set receive buffer: requested 4194304, got 1048576 (tr-udp.c:84)
May 5 08:05:55 transmission-daemon[3520]: UDP Failed to set receive buffer: requested 4194304, got 1048576 (tr-udp.c:84)
May 5 08:05:56 miniupnpd[2058]: shutting down MiniUPnPd
May 5 08:05:56 kernel: [ 68.823499] CPU: 1 PID: 3537 Comm: dm2_amuled Tainted: P O 4.1.52 #4
May 5 08:05:56 kernel: [ 68.831047] Hardware name: Generic DT based system
May 5 08:05:56 kernel: [ 68.835866] task: cccfc400 ti: cd8ca000 task.ti: cd8ca000
May 5 08:05:56 kernel: [ 68.841313] PC is at 0xb6baf5c8
May 5 08:05:56 kernel: [ 68.844466] LR is at 0x6
May 5 08:05:56 kernel: [ 68.847007] pc : [<b6baf5c8>] lr : [<00000006>] psr: 20000010
May 5 08:05:56 kernel: [ 68.847007] sp : b6a60840 ip : 00000dd1 fp : 00289464
May 5 08:05:56 kernel: [ 68.858506] r10: 00289464 r9 : b6a60c80 r8 : 00000000
May 5 08:05:56 kernel: [ 68.863741] r7 : 0000010c r6 : 00000001 r5 : 01d9f7c0 r4 : b6bf51dc
May 5 08:05:56 kernel: [ 68.870293] r3 : b6a69950 r2 : 00000006 r1 : 00000dd1 r0 : 00000000
May 5 08:05:56 kernel: [ 68.876873] Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
May 5 08:05:56 kernel: [ 68.884177] Control: 10c5387d Table: 0b43804a DAC: 00000015
May 5 08:05:56 kernel: [ 68.889970] CPU: 1 PID: 3537 Comm: dm2_amuled Tainted: P O 4.1.52 #4
May 5 08:05:56 kernel: [ 68.897463] Hardware name: Generic DT based system
May 5 08:05:56 kernel: [ 68.902298] [<c00270a0>] (unwind_backtrace) from [<c0022cf8>] (show_stack+0x10/0x14)
May 5 08:05:56 kernel: [ 68.910072] [<c0022cf8>] (show_stack) from [<c045551c>] (dump_stack+0x8c/0xa0)
May 5 08:05:56 kernel: [ 68.917325] [<c045551c>] (dump_stack) from [<c003acf0>] (get_signal+0x490/0x558)
May 5 08:05:56 kernel: [ 68.924750] [<c003acf0>] (get_signal) from [<c0022290>] (do_signal+0xc8/0x3ac)
May 5 08:05:56 kernel: [ 68.932004] [<c0022290>] (do_signal) from [<c0022718>] (do_work_pending+0x94/0xa4)
May 5 08:05:56 kernel: [ 68.939602] [<c0022718>] (do_work_pending) from [<c001f58c>] (work_pending+0xc/0x20)
May 5 08:05:57 miniupnpd: it is advised to use network interface name instead of 10.1.1.1/255.255.255.0
May 5 08:05:57 miniupnpd[3788]: HTTP listening on port 59836
May 5 08:05:57 kernel: [ 69.865613] Archer TCP Pure ACK Enabled
May 5 08:05:57 rc_service: ip-up 2009:notify_rc stop_samba
May 5 08:05:57 rc_service: ip-up 2009:notify_rc start_samba
May 5 08:05:57 rc_service: waitting “stop_samba” via ip-up …
May 5 08:05:57 miniupnpd[3788]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 08:05:57 Samba Server: smb daemon is stopped
May 5 08:05:58 miniupnpd[3788]: shutting down MiniUPnPd
May 5 08:05:59 Samba Server: daemon is started
May 5 08:05:59 miniupnpd: it is advised to use network interface name instead of 10.1.1.1/255.255.255.0
May 5 08:05:59 miniupnpd[4079]: HTTP listening on port 43836
May 5 08:06:00 miniupnpd[4079]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 08:06:01 zcip client: configured 169.254.97.144
May 5 08:06:03 rc_service: hotplug 2160:notify_rc restart_nasapps
May 5 08:06:03 iTunes: daemon is stoped
May 5 08:06:03 FTP Server: daemon is stopped
May 5 08:06:03 wsdd2[4046]: Terminated received.
May 5 08:06:03 Samba Server: smb daemon is stopped
May 5 08:06:04 Timemachine: daemon is stoped
May 5 08:06:04 miniupnpd[4079]: shutting down MiniUPnPd
May 5 08:06:04 avahi-daemon[4211]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 5 08:06:04 Samba Server: daemon is started
May 5 08:06:04 miniupnpd: it is advised to use network interface name instead of 10.1.1.1/255.255.255.0
May 5 08:06:04 miniupnpd[4230]: HTTP listening on port 37259
May 5 08:06:04 miniupnpd[4230]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 08:06:05 avahi-daemon[4211]: Alias name “DSL-AX82U” successfully established.
May 5 08:06:08 WAN Connection: WAN was restored.
May 5 08:06:08 rc_service: wanduck 1581:notify_rc start_apps_update
May 5 08:06:09 ntp: start NTP update
Dec 31 18:48:54 rc_service: ntp 2046:notify_rc restart_diskmon
Dec 31 18:48:54 disk_monitor: Finish
Dec 31 18:48:54 disk monitor: be idle
Dec 31 18:49:15 wlceventd: wlceventd_proc_event(530): eth5: Auth ff:ff:ff:ff:ff:ff, status: Successful (0), rssi:0
Dec 31 18:49:15 wlceventd: wlceventd_proc_event(559): eth5: Assoc ff:ff:ff:ff:ff:ff, status: Successful (0), rssi:-44
Dec 31 18:49:40 WAN Connection: Fail to connect with some issues.
Dec 31 18:49:45 crond[1683]: time disparity of 2450083 minutes detected
Dec 31 18:50:12 wlceventd: wlceventd_proc_event(530): eth6: Auth ff:ff:ff:ff:ff:ff, status: Successful (0), rssi:-57
Dec 31 18:50:12 wlceventd: wlceventd_proc_event(540): eth6: ReAssoc ff:ff:ff:ff:ff:ff, status: Successful (0), rssi:-57
Dec 31 18:50:47 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7722)]periodic_check AM 5:46
Dec 31 18:50:47 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7761)]do webs_update
Dec 31 18:51:08 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7779)]retrieve firmware information
Dec 31 18:51:08 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7782)]user in use
Dec 31 18:51:38 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7761)]do webs_update
Dec 31 18:51:41 WAN Connection: WAN was restored.
Dec 31 18:51:41 rc_service: wanduck 1581:notify_rc start_apps_update
Dec 31 18:51:44 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7779)]retrieve firmware information
Dec 31 18:51:44 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7782)]user in use
Dec 31 18:52:07 WAN Connection: Fail to connect with some issues.
Dec 31 18:52:13 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7761)]do webs_update
Dec 31 18:52:19 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7779)]retrieve firmware information
Dec 31 18:52:19 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7782)]user in use

Share the knowledge

You need to login in order to vote

[UK Sentinel]

Are you using the DSL-AX82U inbuilt modem ?

Share the knowledge

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Black Bird]

UK Sentinel wrote:

Are you using the DSL-AX82U inbuilt modem ?

I using VDSL and was transferred to FTTH (same ISP). I connected DSL-AX82U directly to ONT. I’ve been using it this way for a long time. There were no problems until the FW update.

 

Note: All my account and configuration information on the same ISP is the same as VDSL (username, password and VLAN ID)

Share the knowledge

You need to login in order to vote

[UK Sentinel]

That makes sense as the log was suggesting this also

Usually for a FTTH connection, no VLAN ID is needed, but as you live in Turkey, thet maybe different, when you switched from VDSL to FTTH, did you perform a factory reset and start again, your issues are with IPv6 and on a previous firmware version also as you mentioned earlier ?

Share the knowledge

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Black Bird]

If I install the 3.0.0.4.386_49608 version and install it from the factory settings, IPv6 works.

Share the knowledge

Attachments:

1. 

   fwold.jpg
   

You need to login in order to vote

[Black Bird]

I upgrade to version 9.0.0.4_388_21184-g44bd437 with the same settings, it works IPv6.

I take the modem to the factory settings and re-install it, it works again.

 

 

 

Share the knowledge

Attachments:

1. 

   fwbeta.jpg
   

Liked by:

You need to login in order to vote

[UK Sentinel]

I understand now, does ASUS DSL-AX82U Firmware version 3.0.0.4.388_22048 IPv6 work ?

Share the knowledge

In a completely sane world, madness is the only freedom (J.G.Ballard).

Liked by:

You need to login in order to vote

[Author]

Posts