What's new

OC and web interface

  • 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!

Not bad. In your Asus, type "iptables -L -n" what's the output?
 
Not bad. In your Asus, type "iptables -L -n" what's the output?

here is the result in screen shot.
Its kind of weird that I could access GUI after restart router, but 30 min or so later I won't be able to access it.
 

Attachments

  • openvpn9.jpg
    openvpn9.jpg
    69.2 KB · Views: 271
here is the result in screen shot.
Its kind of weird that I could access GUI after restart router, but 30 min or so later I won't be able to access it.

Your firewall on the router seems fine..
It's an interesting problem. Something goes bad during the 30min after startup.

Last try from me. In you Asus type, "killall httpd". Maybe repeat a couple of times until u see error. Then wait for a minute or so. Meanwhile, use the previous command "ps | grep http" to see if httpd shows up again. When it does, try to access the GUI from your PC.

That's all from me at the moment. Sorry, I've little clue of what might have happened during that 30mins.
 
Your firewall on the router seems fine..
It's an interesting problem. Something goes bad during the 30min after startup.

Last try from me. In you Asus type, "killall httpd". Maybe repeat a couple of times until u see error. Then wait for a minute or so. Meanwhile, use the previous command "ps | grep http" to see if httpd shows up again. When it does, try to access the GUI from your PC.

That's all from me at the moment. Sorry, I've little clue of what might have happened during that 30mins.

here is the return,
 

Attachments

  • openvpn10.jpg
    openvpn10.jpg
    214.3 KB · Views: 489
O great. Looks promising then. Something goes bad int "httpd" (Asus restarts httpd for you after you "killall httpd")

I thought the default clk for AC68U is 800,533. Are you still in overclocked mode?
 
O great. Looks promising then. Something goes bad int "httpd"

I thought the default clk for AC68U is 800,533. Are you still in overclocked mode?

after I did the reset, and I check the nvram get clkfreq, it shows 800, 666 as default.
I guess I did ddr configuration upgrade before. I am not sure if I could still access the router 30 mins later.
 
Are you running in a double NAT setup (I see that your router is getting a 192.168.1.xx WAN address)? Not sure how, if at all, that would affect things....but maybe add another piece of the puzzle.
 
Are you running in a double NAT setup (I see that your router is getting a 192.168.1.xx WAN address)? Not sure how, if at all, that would affect things....but maybe add another piece of the puzzle.

My router connects to an ATT modem/router having 192.168.1.254 as the getway. it has been this setup for more then a year.

Looks like AC68U comes with 666 as default (http://www.snbforums.com/threads/ac68u-ddr-configuration-upgrade-tools.13454)

Try 800,533 and run for another 30 mins or so.

If the problem is gone, you might have a faulty unit (or your overclock before had introduced some damage..)

I am not sure if I could down clock to 533, and if I reset the router to factory, it will back to 800, 666 again.

a few mins later, I could't access the GUI again.
 
Do you still have the VPN Client running? with the block clients if tunnel goes down checked?

And it does sound like you are double NAT.
 
Do you still have the VPN Client running? with the block clients if tunnel goes down checked?

And it does sound like you are double NAT.

I didn't run VPN windows client, and i had reset the router to factory, so the openVPN was not set up. In addition, I have also attached the vpn windows client setup here.
I will try to flash stock ASUS OEM firmware tomorrw to see if that can solve the problem.
 

Attachments

  • 20150817225025.jpg
    20150817225025.jpg
    183.1 KB · Views: 375
I am not sure if I could down clock to 533, and if I reset the router to factory, it will back to 800, 666 again.

a few mins later, I could't access the GUI again.

Correct. Factory reset will be 800,666. That doesn't prevent people from down clock to 800,533. Worth trying unless you proved before down clock is impossible on your unit.
 
How are you cabling your connection from asus to modem? are you using wan port on asus?
yea, I use WAN port. I have just flashed to stock ASUS FW then DDWRT FW, and I have no problem to access GUI for a few hours. I hope this could solve the issue when I flash back to Merlin build.
 
Since we don't know why this is happening, this may not fix it but have you thought about bridging your ATT modem so that you can avoid double nat? your asus would then get a public IP address from the model rather than a private one.
 
Since we don't know why this is happening, this may not fix it but have you thought about bridging your ATT modem so that you can avoid double nat? your asus would then get a public IP address from the model rather than a private one.

I will try it when I flash back to Merlin build.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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