Interface sometimes "hangs" but no issues so far, wireless is working.
Will post more in the morning.
Update 10:48AM Good morning.
A little update. The build survived the night it seems although stupidly i didn't check the uptime this morning before i started making changes.
Enabling UpNP: worked/seems to be working
Enabling WPA2 Personal for both WL0+1: worked/seems to be working
However WL1 doesn't seem to be consistent when switching to "auto" for the channel width. (Still investigating)
Changing the TX power to [55] on wl0+wl1: worked and seems to be working
Overclocking to 533Mhz: worked and also seems to have helped slightly the interface "hang" issue.
Here is the info i get from status on the CPU temp:
WL0 57.00 °C / WL1 53.37 °C
Turning off telnet and ttraff: worked but i haven't tested yet.
So so far no major issues other than the occasional "hang" of the interface which could be localized. If there is anything else anyone would like me to test i'd be happy to. I'll be testing USB drives over network for a fat32 drive next and post more tonight.
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Wed Oct 29, 2014 17:28 Post subject: Lennox thermostat will not connect wirelessly with this vers
For some reason my Lennox thermostat for furnace does not connect with this version. Wireless is GainSpan Corp and only supports b mode.
Did connect with last BS build as well as any Kong builds I have used. Back on Kong 24354 again.
No change in settings between each update.
Back to Kong 24354 for now.
Posted: Thu Oct 30, 2014 12:26 Post subject: Re: Lennox thermostat will not connect wirelessly with this
myersw wrote:
For some reason my Lennox thermostat for furnace does not connect with this version. Wireless is GainSpan Corp and only supports b mode.
Did connect with last BS build as well as any Kong builds I have used. Back on Kong 24354 again.
No change in settings between each update.
Back to Kong 24354 for now.
--bill
Just installed 25203 on a RT-AC66U and the Lennox thermostat does show up in the network and is connecting to the network. _________________ Netgear XR500, R7800
Asus AC87Ua1
Repeater Bridge
Netgear R6400v2otp
Using firmwares from 25139 to 25179 (broadcom/dd-wrt.v24_micro_generic.bin) WRT54GS v6 goes in loop!
Recovered byRTSv430 via telnet.
Last working release is 24461.
Anyway it's not K26 or K3.x.
Posted: Fri Oct 31, 2014 5:46 Post subject: DD-WRT v24-sp2 (10/27/14) mega e4200 v1
Firmware DD-WRT v24-sp2 (10/27/14) mega on e4200 v1:
Well i can't seem to get usb over the network working.
It was working in the previous build fine. I'll keep at it but i'm hoping someone else with the same device could also take a crack at it.
I also noticed in administration i don't have the option to enable jffs, is this normal ?
i have installed it from scratch in ASUS RT-AC66U with hard reset and reset to asus firmware.
I had complications with the installation. it didn't like to first setup the services etc and then the wan so I had to do a hard reset and then change the wan setup then the other things (but it can be a router problem)
I'm using the radvd config default so no custom at all.
still no ipv6 like with the kong build. the router has ipv6 and the ping works on the router.
1/ it appears to not refresh very well the ipv6 on the client pc (several ipv6 different in a time frame of 48 hours) I need to make a manual refresh of each ethernet conenction.
It doesn't do that with tomatUSB from shibby.
2/ it doesn't transfer the dns ipv6 to the client also even if they are manually entered in the ipv6 page. TOMATOUSB by shibby does that.
3/ the client host in ipv6 even with dns manually confirmed don't have access to ipv6 internet but well on the different client of the NAT.
tomatousb by shibby does that.
3/ still with the other ddwrt release, i don't have access to the internet translation of my webservers. like some.thing.org doesn't work but I have to go through the internal ip adress. But i guess that's a feature of ddwrt but it was more clear on tomatousb by shibby.
I was wondering if anyone has noticed TX Errors. I dont remember seeing this before but I have 3 WZR 1750's and 5 Buffalo WZR-HP-G300NH2.
I know this is the Attheros section so I will post this in both sections.
The Atheros units TX errors are showing no errors. The broadcom units 1750's are all showing TX Errors.
Also, while the atheros units are showing 17dp the broadcom units are 71 which is the low end of the spectrum. _________________ Please Fix The Following Bugs:
EOIP Settings not applied automatically after FW upgrade or reboot. http://svn.dd-wrt.com/ticket/4061
The port 80 forwarding bug with out reapplying settings appears to have been fixxed.