OpenWrt Forum Archive

Topic: Update on Linksys WRT1900AC support

The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

PsyD@f'Ke wrote:

A big shoutout thank you to JW0914! It seem the issue was with the iphones pointed to the router for dns. Now that the router isn't being used for dns queries, the problem seems to have gone away. Also (seems) I remember seeing a lot of 150/150 in the log, and think it had something to do with > Max. concurrent queries. I'm wondering if the iphone doesn't just hammer dns?

You may have mentioned this in another post, but have you tried setting the main DNS on the router to Google?  I've never owned an Apple device, so it could very well be they pull DNS differently, however if DNS is set on the router, all clients should be pulling from the router's first. 

For example, I have 4 DNS addresses set on the WAN interface [Network - Interfaces - WAN - Advanced Settings]:

DNS 1: 8.26.56.26 [Comodo #1]
DNS 2: 8.20.247.20 [Comodo #2]
DNS 3: 8.8.8.8 [Google #1]
DNS 4: 8.8.4.4 [Google #2]

Comodo's [as in Comodo Internet Security] DNS is a good deterrent against malware/phishing sites, but also has false positives occasionally, preventing you from navigating to the page... which is why Google DNS is set as #3 & #4.

Setting the DNS on clients isn't ideal since it can create networking problems if the client connects to a network or intranet that requires it's DNS to be queried prior to querying internet domains.  If this occurs, it's  more of an inconvenience than anything else since you'll have to repeatedly set/unset the DNS manually.

(Last edited by JW0914 on 26 Jun 2015, 17:28)

JW0914 wrote:

I know on my R6300 running DD-WRT the 5gHz spectrum has upper/lower options that have to be set (lower lower, lower upper, upper lower, upper upper), which sounds a lot like how DFS is implemented... unfortunately, the upper/lower option isn't built into openwrt.

Please also remember that each client must also match the same channel config set on the router

Well running channel 108 in OpenWRT is the same as 100 Upper/Upper in DD-WRT so I don't really call that a huge loss.

The discussion was also about that his wifi wasn't coming up at all, not about connectability, ie not a client discussion at all - obviously the client needs to be able to support whatever the AP is running, be it DFS bands or 5GHz or anything else.

// Stefan

JW0914 wrote:
PsyD@f'Ke wrote:

A big shoutout thank you to JW0914! It seem the issue was with the iphones pointed to the router for dns. Now that the router isn't being used for dns queries, the problem seems to have gone away. Also (seems) I remember seeing a lot of 150/150 in the log, and think it had something to do with > Max. concurrent queries. I'm wondering if the iphone doesn't just hammer dns?

You may have mentioned this in another post, but have you tried setting the main DNS on the router to Google?  I've never owned an Apple device, so it could very well be they pull DNS differently, however if DNS is set on the router, all clients should be pulling from the router's first. 

For example, I have 4 DNS addresses set on the WAN interface [Network - Interfaces - WAN - Advanced Settings]:

DNS 1: 8.26.56.26 [Comodo #1]
DNS 2: 8.20.247.20 [Comodo #2]
DNS 3: 8.8.8.8 [Google #1]
DNS 4: 8.8.4.4 [Google #2]

Comodo's [as in Comodo Internet Security] DNS is a good deterrent against malware/phishing sites, but also has false positives occasionally, preventing you from navigating to the page... which is why Google DNS is set as #3 & #4.

Setting the DNS on clients isn't ideal since it can create networking problems if the client connects to a network or intranet that requires it's DNS to be queried prior to querying internet domains.  If this occurs, it's  more of an inconvenience than anything else since you'll have to repeatedly set/unset the DNS manually.

I'm quoting this particular reply even though I could have replied to any other one, this isn't pointed at you specifically.

Maybe the reason I haven't had any issues with my fruity devices at all is because I always redirect DNS via DHCP to another DNS machine I have and apparently fruity loops like that DNS, so I simply never encountered the issue.

// Stefan

JW0914 wrote:

I should have elaborated more on my earlier question... were you able to use DFS prior to running RC2?

I never tried to prior to RC2. I set up a second AP on Channel 36 and set the WRT1900AC to auto (both using 80MHz), that didn't work.

@stesmi

I read your post regarding DFS channels. Thats why I tried channel 120 so that there would be enough headroom for the 80MHz. But it doesn't seem to matter which channel I use since it will just fail to use DFS.

I thought DFS channels were fixed since they show up in LuCI. Guess I'll have to try and build my own custom build with your patch.

JW0914 wrote:
PsyD@f'Ke wrote:

A big shoutout thank you to JW0914! It seem the issue was with the iphones pointed to the router for dns. Now that the router isn't being used for dns queries, the problem seems to have gone away. Also (seems) I remember seeing a lot of 150/150 in the log, and think it had something to do with > Max. concurrent queries. I'm wondering if the iphone doesn't just hammer dns?

You may have mentioned this in another post, but have you tried setting the main DNS on the router to Google?  I've never owned an Apple device, so it could very well be they pull DNS differently, however if DNS is set on the router, all clients should be pulling from the router's first. 

For example, I have 4 DNS addresses set on the WAN interface [Network - Interfaces - WAN - Advanced Settings]:

DNS 1: 8.26.56.26 [Comodo #1]
DNS 2: 8.20.247.20 [Comodo #2]
DNS 3: 8.8.8.8 [Google #1]
DNS 4: 8.8.4.4 [Google #2]

Comodo's [as in Comodo Internet Security] DNS is a good deterrent against malware/phishing sites, but also has false positives occasionally, preventing you from navigating to the page... which is why Google DNS is set as #3 & #4.

Setting the DNS on clients isn't ideal since it can create networking problems if the client connects to a network or intranet that requires it's DNS to be queried prior to querying internet domains.  If this occurs, it's  more of an inconvenience than anything else since you'll have to repeatedly set/unset the DNS manually.

Actually, that's how I had it set up originally..   Router points to Google DNS > All clients point to Router for DNS. As you know now, this configuration just doesn't work at my house.

What's been working is the following.

Router's pointed to Google for DNS (Captain Dunsel at this point) > However, all clients are pointed to Google DNS. If you look at the DNS setting on any of our phones, in the DNS spot, it says 8.8.8.8 and 8.8.4.4.  It's been 3 days now, and the router's no longer crashing, and the family isn't reporting any iphone slowness. They would know because I have a wife that works from home, and kids on summer break. They use the hell out of the internet right now (specifically wifi), so they are my front line for reporting problems.

Appreciate the suggestion for dns security > malware protection.  One can't be secure enough on today's internet smile  If all goes well, over the next few weeks, I'll give it a try.

Best Regards,

davidc502 wrote:
JW0914 wrote:
PsyD@f'Ke wrote:

A big shoutout thank you to JW0914! It seem the issue was with the iphones pointed to the router for dns. Now that the router isn't being used for dns queries, the problem seems to have gone away. Also (seems) I remember seeing a lot of 150/150 in the log, and think it had something to do with > Max. concurrent queries. I'm wondering if the iphone doesn't just hammer dns?

You may have mentioned this in another post, but have you tried setting the main DNS on the router to Google?  I've never owned an Apple device, so it could very well be they pull DNS differently, however if DNS is set on the router, all clients should be pulling from the router's first. 

For example, I have 4 DNS addresses set on the WAN interface [Network - Interfaces - WAN - Advanced Settings]:

DNS 1: 8.26.56.26 [Comodo #1]
DNS 2: 8.20.247.20 [Comodo #2]
DNS 3: 8.8.8.8 [Google #1]
DNS 4: 8.8.4.4 [Google #2]

Comodo's [as in Comodo Internet Security] DNS is a good deterrent against malware/phishing sites, but also has false positives occasionally, preventing you from navigating to the page... which is why Google DNS is set as #3 & #4.

Setting the DNS on clients isn't ideal since it can create networking problems if the client connects to a network or intranet that requires it's DNS to be queried prior to querying internet domains.  If this occurs, it's  more of an inconvenience than anything else since you'll have to repeatedly set/unset the DNS manually.

Actually, that's how I had it set up originally..   Router points to Google DNS > All clients point to Router for DNS. As you know now, this configuration just doesn't work at my house.

What's been working is the following.

Router's pointed to Google for DNS (Captain Dunsel at this point) > However, all clients are pointed to Google DNS. If you look at the DNS setting on any of our phones, in the DNS spot, it says 8.8.8.8 and 8.8.4.4.  It's been 3 days now, and the router's no longer crashing, and the family isn't reporting any iphone slowness. They would know because I have a wife that works from home, and kids on summer break. They use the hell out of the internet right now (specifically wifi), so they are my front line for reporting problems.

Appreciate the suggestion for dns security > malware protection.  One can't be secure enough on today's internet smile  If all goes well, over the next few weeks, I'll give it a try.

Best Regards,

If you do eventually find out why this issue occurs on apple devices, please let me know as I'm curious to find out why the issue is occurring.

Hello, sorry but I have just install the Chaos Calmer and can not telnet or even ping

The DEFAULT IP is 192.168.1.1 same?

deraol wrote:

Hello, sorry but I have just install the Chaos Calmer and can not telnet or even ping

The DEFAULT IP is 192.168.1.1 same?

it depends... did you reflash OpenWRT and select keep settings?  If so, it'll be your previous IP.

If that's not it, run ipconfig /all if windows or ifconfig if linux to find what IP you're being assigned.

Thanks ...
But it is not being assigned any ip and my previous ip was 192.168.1.1

deraol wrote:

Thanks ...
But it is not being assigned any ip and my previous ip was 192.168.1.1

Should be a quick fix, we just have to narrow down what the issue is... is the power led on the router blinking (farthest led to the left if facing the router)? It should be solid, if not, you're going to have to flash via TTL.  If it is solid, proceed below:

1. Disconnect the WAN cable from the router and unplug the power cord
2. Completely disable the firewall on your pc and run a LAN cable from one of the LAN ports on the router to your PC
3. Plug the router power cable back in (NOT the WAN cable) and see if you're being assigned an IP that's not a link local IP (169.254.x.x)
4.If you're still being assigned a link local, manually assign your PC an IP of 192.168.1.2/255.255.255.0, and try to telnet in.

If that fixes it, do not forget to re-enable your firewall PRIOR to plugging the WAN cable back in the router

(Last edited by JW0914 on 27 Jun 2015, 02:26)

Also, if the flash occurred successfully, your should hear the fan kick on high for 15 - 30 seconds then turn off.  If it doesn't, that's usually the first clue the flash didn't go right.

yet nothing with telnet
as I do the flash via TTL

also no fan
brick then?

deraol wrote:

yet nothing with telnet
as I do the flash via TTL

I have no problem helping you, nor does anyone else... but that response is unacceptable, especially considering the two previous posts of mine to which you were responding.  If you don't want to help yourself, don't expect other people to help you.

deraol wrote:

also no fan
brick then?

You'll need to reflash via TTL then.

When you flashed, did a bunch of hash signs (the # sign) occur?  If the TTL flash is successful, there will be at least two lines of hash signs.

(Last edited by JW0914 on 27 Jun 2015, 02:38)

Also, if the TTL flash did complete successfully, try flashing [overwriting] both the primary and backup image.  If that still does not work, flash the OEM Linksys image via TTL to both the primary and backup, then flash openwrt from the Linksys web ui

JW0914 wrote:
deraol wrote:

yet nothing with telnet
as I do the flash via TTL

I have no problem helping you, nor does anyone else... but that response is unacceptable, especially considering the two previous posts of mine to which you were responding.  If you don't want to help yourself, don't expect other people to help you.

I'm sorry for double post
It will not occur again
unfortunately for me it will be very difficult to achieve TTL
Thanks for your time anyway

deraol wrote:
JW0914 wrote:
deraol wrote:

yet nothing with telnet
as I do the flash via TTL

I have no problem helping you, nor does anyone else... but that response is unacceptable, especially considering the two previous posts of mine to which you were responding.  If you don't want to help yourself, don't expect other people to help you.

I'm sorry for double post
It will not occur again
unfortunately for me it will be very difficult to achieve TTL
Thanks for your time anyway

I'm confused... you stated "as I do the flash via TTL".  You didn't flash the firmware via TTL? 

The point wasn't about a double post, but of a complete lack of detailed response.  We can't see your router, so in order to provide help, details must be provided; especially when requested.

(Last edited by JW0914 on 27 Jun 2015, 02:47)

my English is horrible
I did not ttl
I made via browser
I do not know how to disassemble

deraol wrote:

my English is horrible
I did not ttl
I made via browser
I do not know how to disassemble

No worries about a language barrier... if it's easier, feel free to email me in your native language and I can use google translate (jw0914@live.com).  [I don't think OpenWRT allows for posting in non-english on an english forum.]

Recovering via TTL is extremely simple, and the disassembly of the router is even more simple.

On the bottom of the router, in the middle of each foot is a phillips screw... unscrew all 4 (1 for each foot).  Once they're unscrewed, the blue front of the router slides apart from the black portion.   Once the blue front is off, the remaining black casing is 2 pieces (top and bottom) and held together via plastic clips.  This is the most difficult and time consuming, especially when taking it apart for the first time.  You'll have to have some patience and gently pry apart the top and bottom half, being careful not to force it too much, otherwise the clips will break.  It took me around 10 minutes the first time I separated the two halves.  Just go slow and don't force it... if one side you're working on doesn't want to pop loose of the plastic clips, move to another side and work back.

You don't need to unscrew the antennas, unless you want to, as only the top half of the black casing has to come off to gain access to the serial port.  Directions on how to flash via TTL are at the bottom of this link: OpenWRT WRT1900ac  In order to flash via TTL, you must have a FTDI USB to TTL cable... depending where you live, a local electronics store may have one, however most people by theirs online.  Prices will vary online from ~ $15 - $25 USD.

If using Windows, this is the PuTTY profile to use for the serial connection.  Simply copy and paste it to a text file, rename the text file to Serial.reg, right click the file, then select merge.  Then, open PuTTY and select "Serial" from the profile list.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\Serial]
"Present"=dword:00000001
"HostName"=""
"LogFileName"="C:\\putty.log"
"LogType"=dword:00000000
"LogFileClash"=dword:ffffffff
"LogFlush"=dword:00000001
"SSHLogOmitPasswords"=dword:00000001
"SSHLogOmitData"=dword:00000000
"Protocol"="serial"
"PortNumber"=dword:00000000
"CloseOnExit"=dword:00000001
"WarnOnClose"=dword:00000001
"PingInterval"=dword:00000000
"PingIntervalSecs"=dword:00000000
"TCPNoDelay"=dword:00000001
"TCPKeepalives"=dword:00000000
"TerminalType"="xterm"
"TerminalSpeed"="38400,38400"
"TerminalModes"="CS7=A,CS8=A,DISCARD=A,DSUSP=A,ECHO=A,ECHOCTL=A,ECHOE=A,ECHOK=A,ECHOKE=A,ECHONL=A,EOF=A,EOL=A,EOL2=A,ERASE=A,FLUSH=A,ICANON=A,ICRNL=A,IEXTEN=A,IGNCR=A,IGNPAR=A,IMAXBEL=A,INLCR=A,INPCK=A,INTR=A,ISIG=A,ISTRIP=A,IUCLC=A,IXANY=A,IXOFF=A,IXON=A,KILL=A,LNEXT=A,NOFLSH=A,OCRNL=A,OLCUC=A,ONLCR=A,ONLRET=A,ONOCR=A,OPOST=A,PARENB=A,PARMRK=A,PARODD=A,PENDIN=A,QUIT=A,REPRINT=A,START=A,STATUS=A,STOP=A,SUSP=A,SWTCH=A,TOSTOP=A,WERASE=A,XCASE=A"
"AddressFamily"=dword:00000000
"ProxyExcludeList"=""
"ProxyDNS"=dword:00000001
"ProxyLocalhost"=dword:00000000
"ProxyMethod"=dword:00000000
"ProxyHost"="proxy"
"ProxyPort"=dword:00000050
"ProxyUsername"=""
"ProxyPassword"=""
"ProxyTelnetCommand"="connect %host %port\\n"
"Environment"=""
"UserName"=""
"UserNameFromEnvironment"=dword:00000000
"LocalUserName"=""
"NoPTY"=dword:00000000
"Compression"=dword:00000000
"TryAgent"=dword:00000001
"AgentFwd"=dword:00000000
"GssapiFwd"=dword:00000000
"ChangeUsername"=dword:00000000
"Cipher"="aes,blowfish,3des,WARN,arcfour,des"
"KEX"="dh-gex-sha1,dh-group14-sha1,dh-group1-sha1,rsa,WARN"
"RekeyTime"=dword:0000003c
"RekeyBytes"="1G"
"SshNoAuth"=dword:00000000
"SshBanner"=dword:00000001
"AuthTIS"=dword:00000000
"AuthKI"=dword:00000001
"AuthGSSAPI"=dword:00000001
"GSSLibs"="gssapi32,sspi,custom"
"GSSCustom"=""
"SshNoShell"=dword:00000000
"SshProt"=dword:00000002
"LogHost"=""
"SSH2DES"=dword:00000000
"PublicKeyFile"=""
"RemoteCommand"=""
"RFCEnviron"=dword:00000000
"PassiveTelnet"=dword:00000000
"BackspaceIsDelete"=dword:00000001
"RXVTHomeEnd"=dword:00000000
"LinuxFunctionKeys"=dword:00000000
"NoApplicationKeys"=dword:00000000
"NoApplicationCursors"=dword:00000000
"NoMouseReporting"=dword:00000000
"NoRemoteResize"=dword:00000000
"NoAltScreen"=dword:00000000
"NoRemoteWinTitle"=dword:00000000
"RemoteQTitleAction"=dword:00000001
"NoDBackspace"=dword:00000000
"NoRemoteCharset"=dword:00000000
"ApplicationCursorKeys"=dword:00000000
"ApplicationKeypad"=dword:00000000
"NetHackKeypad"=dword:00000000
"AltF4"=dword:00000001
"AltSpace"=dword:00000000
"AltOnly"=dword:00000000
"ComposeKey"=dword:00000000
"CtrlAltKeys"=dword:00000001
"TelnetKey"=dword:00000000
"TelnetRet"=dword:00000001
"LocalEcho"=dword:00000002
"LocalEdit"=dword:00000002
"Answerback"="PuTTY"
"AlwaysOnTop"=dword:00000000
"FullScreenOnAltEnter"=dword:00000000
"HideMousePtr"=dword:00000000
"SunkenEdge"=dword:00000000
"WindowBorder"=dword:00000001
"CurType"=dword:00000001
"BlinkCur"=dword:00000001
"Beep"=dword:00000001
"BeepInd"=dword:00000000
"BellWaveFile"=""
"BellOverload"=dword:00000001
"BellOverloadN"=dword:00000005
"BellOverloadT"=dword:000007d0
"BellOverloadS"=dword:00001388
"ScrollbackLines"=dword:00002710
"DECOriginMode"=dword:00000000
"AutoWrapMode"=dword:00000001
"LFImpliesCR"=dword:00000000
"CRImpliesLF"=dword:00000000
"DisableArabicShaping"=dword:00000000
"DisableBidi"=dword:00000000
"WinNameAlways"=dword:00000001
"WinTitle"="Secure Shell - Serial"
"TermWidth"=dword:00000050
"TermHeight"=dword:00000028
"Font"="Courier New"
"FontIsBold"=dword:00000000
"FontCharSet"=dword:00000000
"FontHeight"=dword:0000000a
"FontQuality"=dword:00000003
"FontVTMode"=dword:00000004
"UseSystemColours"=dword:00000000
"TryPalette"=dword:00000000
"ANSIColour"=dword:00000001
"Xterm256Colour"=dword:00000001
"BoldAsColour"=dword:00000000
"Colour0"="170,210,0"
"Colour1"="255,125,0"
"Colour2"="25,25,25"
"Colour3"="20,20,20"
"Colour4"="0,0,0"
"Colour5"="0,255,0"
"Colour6"="0,0,0"
"Colour7"="85,85,85"
"Colour8"="187,0,0"
"Colour9"="255,85,85"
"Colour10"="0,187,0"
"Colour11"="85,255,85"
"Colour12"="187,187,0"
"Colour13"="255,255,85"
"Colour14"="0,163,255"
"Colour15"="0,100,255"
"Colour16"="187,0,187"
"Colour17"="255,85,255"
"Colour18"="0,187,187"
"Colour19"="85,255,255"
"Colour20"="187,187,187"
"Colour21"="255,255,255"
"RawCNP"=dword:00000000
"PasteRTF"=dword:00000000
"MouseIsXterm"=dword:00000000
"RectSelect"=dword:00000000
"MouseOverride"=dword:00000001
"Wordness0"="0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"
"Wordness32"="0,1,2,1,1,1,1,1,1,1,1,1,1,2,2,2,2,2,2,2,2,2,2,2,2,2,1,1,1,1,1,1"
"Wordness64"="1,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,1,1,1,1,2"
"Wordness96"="1,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,1,1,1,1,1"
"Wordness128"="1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1"
"Wordness160"="1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1"
"Wordness192"="2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,1,2,2,2,2,2,2,2,2"
"Wordness224"="2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,1,2,2,2,2,2,2,2,2"
"LineCodePage"="UTF-8"
"CJKAmbigWide"=dword:00000000
"UTF8Override"=dword:00000001
"Printer"=""
"CapsLockCyr"=dword:00000000
"ScrollBar"=dword:00000001
"ScrollBarFullScreen"=dword:00000000
"ScrollOnKey"=dword:00000000
"ScrollOnDisp"=dword:00000001
"EraseToScrollback"=dword:00000001
"LockSize"=dword:00000000
"BCE"=dword:00000001
"BlinkText"=dword:00000000
"X11Forward"=dword:00000000
"X11Display"=""
"X11AuthType"=dword:00000001
"X11AuthFile"=""
"LocalPortAcceptAll"=dword:00000000
"RemotePortAcceptAll"=dword:00000000
"PortForwardings"=""
"BugIgnore1"=dword:00000000
"BugPlainPW1"=dword:00000000
"BugRSA1"=dword:00000000
"BugIgnore2"=dword:00000000
"BugHMAC2"=dword:00000000
"BugDeriveKey2"=dword:00000000
"BugRSAPad2"=dword:00000000
"BugPKSessID2"=dword:00000000
"BugRekey2"=dword:00000000
"BugMaxPkt2"=dword:00000000
"BugWinadj"=dword:00000000
"StampUtmp"=dword:00000001
"LoginShell"=dword:00000001
"ScrollbarOnLeft"=dword:00000000
"BoldFont"=""
"BoldFontIsBold"=dword:00000000
"BoldFontCharSet"=dword:00000000
"BoldFontHeight"=dword:00000000
"WideFont"=""
"WideFontIsBold"=dword:00000000
"WideFontCharSet"=dword:00000000
"WideFontHeight"=dword:00000000
"WideBoldFont"=""
"WideBoldFontIsBold"=dword:00000000
"WideBoldFontCharSet"=dword:00000000
"WideBoldFontHeight"=dword:00000000
"ShadowBold"=dword:00000000
"ShadowBoldOffset"=dword:00000001
"SerialLine"="COM3"
"SerialSpeed"=dword:0001c200
"SerialDataBits"=dword:00000008
"SerialStopHalfbits"=dword:00000002
"SerialParity"=dword:00000000
"SerialFlowControl"=dword:00000000
"WindowClass"=""
"BugChanReq"=dword:00000000
"ConnectionSharing"=dword:00000000
"ConnectionSharingUpstream"=dword:00000001
"ConnectionSharingDownstream"=dword:00000001
"SSHManualHostKeys"=""

(Last edited by JW0914 on 27 Jun 2015, 03:33)

JW0914 wrote:

You don't need to unscrew the antennas, unless you want to, as only the top half of the black casing has to come off to gain access to the serial port.  Directions on how to flash via TTL are at the bottom of this link: OpenWRT WRT1900ac  In order to flash via TTL, you must have a FTDI USB to TTL cable... depending where you live, a local electronics store may have one, however most people by theirs online.  Prices will vary online from ~ $15 - $25 USD.

Cheaper ones work fine, too. I have a bunch of $2 USD pl2303 USB-TTL adapters that work fine for this purpose.

leitec wrote:
JW0914 wrote:

You don't need to unscrew the antennas, unless you want to, as only the top half of the black casing has to come off to gain access to the serial port.  Directions on how to flash via TTL are at the bottom of this link: OpenWRT WRT1900ac  In order to flash via TTL, you must have a FTDI USB to TTL cable... depending where you live, a local electronics store may have one, however most people by theirs online.  Prices will vary online from ~ $15 - $25 USD.

Cheaper ones work fine, too. I have a bunch of $2 USD pl2303 USB-TTL adapters that work fine for this purpose.

I didn't know they made ones that cheap =]

Yup, although it's now $3, apparently: http://www.amazon.com/PL2303HX-RS232-Ca … 03+usb+ttl

You don't actually need control signals for something as simple as serial console access (versus doing actual data transfer over the serial connection) so this works fine. You can take the plastic off of the ends and connect them directly to the header on the router.

@deraol

You may want to try this procedure to see if you're able to get the backup firmware to load:

contributed from forum user edgeman

  1. Reset the router by holding the reset button in until the PWR LED starts to flash
    * Should take about 15 seconds
    * Once power light stops flashing, power off the router with the power switch

  2. Turn the power back on and the Power LED will light
    * As soon as any other LED turns on, power off the router with the power switch

  3. Turn the power back on and the Power LED will light.
    * As soon as any other LED turns on, power off the router with the power switch

  4. Turn the power back on and the Power LED will light.
    * As soon as any other LED turns on, power off the router with the power switch

  5. Turn the power back on and the Power LED will light.
    * Let router power up completely; it should now be on the alternate firmware

This procedure is taken from the Linksys WRT1900AC OpenWRT Wiki page

(Last edited by JW0914 on 27 Jun 2015, 15:23)

RickStep wrote:

Thanks for the quick turn around time for the code.

No problem at all! I was planning on doing something like this anyway at some point; a recent lockup led me to a new firmware version (and more lockups) and to your post.

The  flowchart was generated in response to [Chadster766]

Thanks, Chadster766 for getting the ball rolling on all of this smile

My previous record with RC2 was right around 48 hours before it locked up and needed a reboot, so I'm happy to report that I've been running it with this script for 7 days and 13 hours with some pretty heavy streaming and downloading. 7.5 days is going to be the limit right now because my cats broke into the server closet to play and managed to unplug a few things.

My CPU temperature hovers around 60 degrees, +/- 4 or so with the script running. I'm not sure if that's high or low compared to anyone else but it's working for me. If that seems high, I can adjust the CPU temperature checks to be a little more aggressive with the fan speeds.

I forgot to mention in my last post that I removed the following line from my crontab so that it wouldn't interfere with the new script:

 */5 * * * * /sbin/fan_ctrl.sh

For anyone else just now reading about this, I recently wrote a script to run all the time that effectively replaces /sbin/fan_ctrl.sh. It does checks of the system and adjusts fan speeds every 5 seconds and is based on this post:
https://forum.openwrt.org/viewtopic.php … 11#p280811

You can download it from here (save it to wherever you'd like):
https://raw.githubusercontent.com/jjack … control.sh

After downloading it, be sure to make it executable

chmod +x fancontrol.sh

To test the script:

./fancontrol.sh verbose

To just run the script in the background all the time:

./fancontrol.sh &

Please let me know how this works for any of you all.