68U 2.4GHz Problem

[jogl]

I'm starting a new thread here because I noticed that my old one:

http://www.snbforums.com/threads/68u-2-4ghz-ongoing-problem.30144/

which is under ASUS Wireless does not show up in "New Posts".

When I bought the RT-AC68U it came with 3.0.0.378_6975. I immediately loaded Merlin 380.57. Then I noticed the problem with the 2.4 causing the ADSL connection to drop. I then went back to Merlin 378.56_2. Same problem.

Question is: Is this the right order to load firmware? I read in another thread that sometimes you have to load the Asus firmware and then go to Merlin.

Thanks.

 

[L&LD]

The order (usually) doesn't matter. Doing a full reset to factory defaults and then doing a manual and minimal config does.

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573


When the order matters is in very specific cases (NVRAM gets it's size adjusted, etc.) and shouldn't be a problem with the latest versions (including yours as indicated).

 

[jogl]

I have been doing a lot of searching around about this problem, and although it appears to not be an issue with all 68U's, it seems that it is common.

For you guys with more experience and knowledge than I, do you think that this will be fixed in firmware eventually?

I bought it for other features that I am happy with, but this 2.4G thing is really... disappointing.

 

[L&LD]

I have been doing a lot of searching around about this problem, and although it appears to not be an issue with all 68U's, it seems that it is common.

For you guys with more experience and knowledge than I, do you think that this will be fixed in firmware eventually?

I bought it for other features that I am happy with, but this 2.4G thing is really... disappointing.

http://www.snbforums.com/threads/ac68u-wireless-connection-issues-on-2-4ghz.30256/#post-236175

 

[Blinkyz]

I have been doing a lot of searching around about this problem, and although it appears to not be an issue with all 68U's, it seems that it is common.

For you guys with more experience and knowledge than I, do you think that this will be fixed in firmware eventually?

I bought it for other features that I am happy with, but this 2.4G thing is really... disappointing.

We dont know
Two last firmwares are buggy for AC68 with the 2.4ghz ,380.1031 and 380.1864 , cross fingers for the next one.
or follow L&LD solution, 380.57_4 Final HGGomes and use the OLD driver version .trx(work very well and without the 2.4ghz issue) or....
stick with 378.56_2 for the moment

 

[MarkyPancake]

Merlin 378.56_2 on an AC68U here and no problems with 2.4 or 5 GHz networks. I didn't have any issues on 380.57 either, but UPnP behaved oddly, which is why I rolled back. Factory hard resets and manual config with both versions of course.

 

[jogl]

Uhg!

Loaded 380.57_HGG-FINAL, old driver.

Same problem. ADSL dies instantly when a 2.4G device connects.

Here is the log of a 2.4 connection, ADSL dies, reconnect:

Feb  6 16:45:52 dnsmasq-dhcp[743]: DHCPREQUEST(br0) 192.168.1.41 1c:65:9d:55:50:70
Feb  6 16:45:52 dnsmasq-dhcp[743]: DHCPACK(br0) 192.168.1.41 1c:65:9d:55:50:70 gan
Feb  6 16:46:14 dnsmasq-dhcp[743]: DHCPREQUEST(br0) 192.168.1.41 1c:65:9d:55:50:70
Feb  6 16:46:14 dnsmasq-dhcp[743]: DHCPACK(br0) 192.168.1.41 1c:65:9d:55:50:70 gan
Feb  6 10:47:58 pppd[1273]: No response to 10 echo-requests
Feb  6 10:47:58 pppd[1273]: Serial link appears to be disconnected.
Feb  6 10:47:58 pppd[1273]: Connect time 13.9 minutes.
Feb  6 10:47:58 pppd[1273]: Sent 743299 bytes, received 7576942 bytes.
Feb  6 16:47:58 dnsmasq[743]: read /etc/hosts - 5 addresses
Feb  6 16:47:58 dnsmasq[743]: using nameserver x.x.188.77#53
Feb  6 16:47:58 dnsmasq[743]: using nameserver x.x.69.69#53
Feb  6 10:47:59 miniupnpd[1407]: Failed to get IP for interface ppp0
Feb  6 10:47:59 miniupnpd[1407]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Feb  6 16:47:59 WAN Connection: Fail to connect with some issues.
Feb  6 16:47:59 stop_nat_rules: apply the redirect_rules!
Feb  6 10:48:04 pppd[1273]: Connection terminated.
Feb  6 10:48:05 pppd[1273]: Sent PADT
Feb  6 10:48:05 pppd[1273]: Modem hangup
Feb  6 10:48:50 pppd[1273]: Timeout waiting for PADO packets
Feb  6 10:48:50 pppd[1273]: PPP session is 15232 (0x3b80)
Feb  6 10:48:50 pppd[1273]: Connected to x:x:1a:a3:85:fe via interface eth0
Feb  6 10:48:50 pppd[1273]: Using interface ppp0
Feb  6 10:48:50 pppd[1273]: Connect: ppp0 <--> eth0
Feb  6 10:48:51 pppd[1273]: PAP authentication succeeded
Feb  6 10:48:51 pppd[1273]: peer from calling number x:x:1A:A3:85:FE authorized
Feb  6 10:48:51 miniupnpd[1407]: Failed to get IP for interface ppp0
Feb  6 10:48:51 miniupnpd[1407]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Feb  6 10:48:51 miniupnpd[1407]: Failed to get IP for interface ppp0
Feb  6 10:48:51 miniupnpd[1407]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Feb  6 10:48:51 miniupnpd[1407]: Failed to get IP for interface ppp0
Feb  6 10:48:51 miniupnpd[1407]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Feb  6 10:48:51 pppd[1273]: local  IP address x.x.230.45
Feb  6 10:48:51 pppd[1273]: remote IP address x.x.239.253
Feb  6 10:48:51 pppd[1273]: primary   DNS address x.x.188.77
Feb  6 10:48:51 pppd[1273]: secondary DNS address x.x.69.69
Feb  6 10:48:51 rc_service: ip-up 1642:notify_rc start_firewall
Feb  6 16:48:51 dnsmasq[743]: read /etc/hosts - 5 addresses
Feb  6 16:48:51 dnsmasq[743]: using nameserver x.x.188.77#53
Feb  6 16:48:51 dnsmasq[743]: using nameserver x.x.69.69#53
Feb  6 10:48:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Feb  6 10:48:52 wan: finish adding multi routes
Feb  6 10:48:52 rc_service: ip-up 1642:notify_rc stop_upnp
Feb  6 10:48:52 rc_service: waitting "start_firewall" via ip-up ...
Feb  6 10:48:53 rc_service: ip-up 1642:notify_rc start_upnp
Feb  6 10:48:53 rc_service: waitting "stop_upnp" via ip-up ...
Feb  6 10:48:53 miniupnpd[1407]: shutting down MiniUPnPd
Feb  6 16:48:54 WAN Connection: WAN was restored.
Feb  6 10:48:55 miniupnpd[1678]: HTTP listening on port 48865
Feb  6 10:48:55 miniupnpd[1678]: Listening for NAT-PMP/PCP traffic on port 5351

 

[L&LD]

Uhg!

Loaded 380.57_HGG-FINAL, old driver.

Same problem. ADSL dies instantly when a 2.4G device connects.

Here is the log of a 2.4 connection, ADSL dies, reconnect:

Feb  6 16:45:52 dnsmasq-dhcp[743]: DHCPREQUEST(br0) 192.168.1.41 1c:65:9d:55:50:70
Feb  6 16:45:52 dnsmasq-dhcp[743]: DHCPACK(br0) 192.168.1.41 1c:65:9d:55:50:70 gan
Feb  6 16:46:14 dnsmasq-dhcp[743]: DHCPREQUEST(br0) 192.168.1.41 1c:65:9d:55:50:70
Feb  6 16:46:14 dnsmasq-dhcp[743]: DHCPACK(br0) 192.168.1.41 1c:65:9d:55:50:70 gan
Feb  6 10:47:58 pppd[1273]: No response to 10 echo-requests
Feb  6 10:47:58 pppd[1273]: Serial link appears to be disconnected.
Feb  6 10:47:58 pppd[1273]: Connect time 13.9 minutes.
Feb  6 10:47:58 pppd[1273]: Sent 743299 bytes, received 7576942 bytes.
Feb  6 16:47:58 dnsmasq[743]: read /etc/hosts - 5 addresses
Feb  6 16:47:58 dnsmasq[743]: using nameserver x.x.188.77#53
Feb  6 16:47:58 dnsmasq[743]: using nameserver x.x.69.69#53
Feb  6 10:47:59 miniupnpd[1407]: Failed to get IP for interface ppp0
Feb  6 10:47:59 miniupnpd[1407]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Feb  6 16:47:59 WAN Connection: Fail to connect with some issues.
Feb  6 16:47:59 stop_nat_rules: apply the redirect_rules!
Feb  6 10:48:04 pppd[1273]: Connection terminated.
Feb  6 10:48:05 pppd[1273]: Sent PADT
Feb  6 10:48:05 pppd[1273]: Modem hangup
Feb  6 10:48:50 pppd[1273]: Timeout waiting for PADO packets
Feb  6 10:48:50 pppd[1273]: PPP session is 15232 (0x3b80)
Feb  6 10:48:50 pppd[1273]: Connected to x:x:1a:a3:85:fe via interface eth0
Feb  6 10:48:50 pppd[1273]: Using interface ppp0
Feb  6 10:48:50 pppd[1273]: Connect: ppp0 <--> eth0
Feb  6 10:48:51 pppd[1273]: PAP authentication succeeded
Feb  6 10:48:51 pppd[1273]: peer from calling number x:x:1A:A3:85:FE authorized
Feb  6 10:48:51 miniupnpd[1407]: Failed to get IP for interface ppp0
Feb  6 10:48:51 miniupnpd[1407]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Feb  6 10:48:51 miniupnpd[1407]: Failed to get IP for interface ppp0
Feb  6 10:48:51 miniupnpd[1407]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Feb  6 10:48:51 miniupnpd[1407]: Failed to get IP for interface ppp0
Feb  6 10:48:51 miniupnpd[1407]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Feb  6 10:48:51 pppd[1273]: local  IP address x.x.230.45
Feb  6 10:48:51 pppd[1273]: remote IP address x.x.239.253
Feb  6 10:48:51 pppd[1273]: primary   DNS address x.x.188.77
Feb  6 10:48:51 pppd[1273]: secondary DNS address x.x.69.69
Feb  6 10:48:51 rc_service: ip-up 1642:notify_rc start_firewall
Feb  6 16:48:51 dnsmasq[743]: read /etc/hosts - 5 addresses
Feb  6 16:48:51 dnsmasq[743]: using nameserver x.x.188.77#53
Feb  6 16:48:51 dnsmasq[743]: using nameserver x.x.69.69#53
Feb  6 10:48:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Feb  6 10:48:52 wan: finish adding multi routes
Feb  6 10:48:52 rc_service: ip-up 1642:notify_rc stop_upnp
Feb  6 10:48:52 rc_service: waitting "start_firewall" via ip-up ...
Feb  6 10:48:53 rc_service: ip-up 1642:notify_rc start_upnp
Feb  6 10:48:53 rc_service: waitting "stop_upnp" via ip-up ...
Feb  6 10:48:53 miniupnpd[1407]: shutting down MiniUPnPd
Feb  6 16:48:54 WAN Connection: WAN was restored.
Feb  6 10:48:55 miniupnpd[1678]: HTTP listening on port 48865
Feb  6 10:48:55 miniupnpd[1678]: Listening for NAT-PMP/PCP traffic on port 5351

Was this with a proper reset to factory defaults?

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573

 

[jogl]

Was this with a proper reset to factory defaults?

I believe so, I did the GUI factory reset and did the reset button as well, just to be sure. Manually re-entered settings.

 

[texashoser]

Is the 2.4 Ghz problem with these last two FW updates isolated to the 68U or does it affect other devices like the 88U?

 

[L&LD]

Is the 2.4 Ghz problem with these last two FW updates isolated to the 68U or does it affect other devices like the 88U?

It may affect any router which received a new wireless driver. See the changelog for details.