Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sat May 05, 2018 1:48 Post subject:
its hard to produce anything if proper logs are missing.
for any wan->lan issues the iptables rules are interesting
"iptables -L" and "iptables -t nat -L" helps alot and the /tmp/.ipt file too.
otherwise i just see this here as interesting discussion but but its no resource for fixing any problem since all informations are missing _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
its hard to produce anything if proper logs are missing.
for any wan->lan issues the iptables rules are interesting
"iptables -L" and "iptables -t nat -L" helps alot and the /tmp/.ipt file too.
otherwise i just see this here as interesting discussion but but its no resource for fixing any problem since all informations are missing
From now on i will present this for you and thanks for letting me/us know what you need to help you.
Would it be useful to you if we presented this data after a flash that has reset to factory defaults and then get the information after we configure our routers as we desire?
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sat May 05, 2018 8:02 Post subject:
no. reset to factory defaults is nothing i advice. thats more a panic button for most users here. i upgrade all my devices without a reset and i take care that all is backward compatible. _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
its hard to produce anything if proper logs are missing.
for any wan->lan issues the iptables rules are interesting
"iptables -L" and "iptables -t nat -L" helps alot and the /tmp/.ipt file too.
otherwise i just see this here as interesting discussion but but its no resource for fixing any problem since all informations are missing
ASUS RT-AC66U
Tried running both 35831 and 35874, but had the same
issues where internet access didn't work at all. Even when logging in via SSH and trying to ping addresses numerically, or trying a traceroute to a known address out on the internet, the traceroute failed.
Have had to fall back to 35034 after both attempts.
35034 continues to work well.
Ran "iptables -L" and "iptables -t nat -L".
Results are in the attachments, but noticed that iptables had obviously failed to load any rules at all in 35874(probably the same in 35831, but I don't have copies of the logs).
I also noticed from looking at /var/log/messages that I have errors in the NAND memory on my Asus - but I think those have been there since I got it, and I am not sure if the MTD filesystem is working around those error locations(?). It appears to be working around them, and I've had no obvious issues with basic functionality.
Joined: 13 Aug 2013 Posts: 6868 Location: Romerike, Norway
Posted: Sun May 06, 2018 8:09 Post subject: Re: Asus RT-AC66U dd-wrt-35831 issue
joel7261 wrote:
Router Model
Asus RT-AC66U
Firmware Version
DD-WRT v3.0-r33006 giga (08/03/17)
Kernel Version
Linux 3.10.107 #15456 Thu Aug 3 11:56:31 CEST 2017 mips
CPU Model
Broadcom BCM5300 chip rev 1
CPU Cores
1
CPU Clock
600 MHz
I flash dd-wrt-35831-Asus_RT-AC66U.trx coming from stock using standard procedure erasing nvram.
Issue is : radio is off for wl0 and wl1
I flash also 35770 version which does not work also.
Version 3306 is good to go. I use it till 2 days and everything is good.