Version 1.4.2

[DoesItMatter]

BTW, I flashed DD-WRT yesterday, only to get up this morning to find two computers using my wireless network. (I hadn't set up wireless yet because I didn't have my netbook handy.) Why does DD-WRT default with a functional, unsecured network? I imagine they'd tell me I should have checked it out immediately after flashing, but wouldn't it be better to have wireless disabled? You need a wired connection anyway to perform the flash and enable wireless web administration, so who is benefiting from it? Even the stock firmware of the WZR-HP-G300NH has the sense to have a secured network out of the box. Sorry for the rant.

Way back when, the FON 2100/2200/2201+ were out in mass quantities
because they were offered cheap, they were simple, and they were
easily used as repeaters, on-the-road bridges, etc.

Most only had the 1 WAN port so when flashing, they left wireless
enabled by default, and usually it was setup with no encryption.

I don't think they have changed that for fresh/new flashes.

Definitely something to pay attention to for any future flashes.

[caeci11ius]

Getting bad packet loss when large numbers of sessions are running through the router. LAN connectivity stays up fine, but WAN goes bonkers. Ping output (google.com):

Code: Select all

Reply from 74.125.237.51: bytes=32 time=72ms TTL=56
Reply from 74.125.237.51: bytes=32 time=209ms TTL=56
Reply from 74.125.237.51: bytes=32 time=77ms TTL=56
Reply from 74.125.237.51: bytes=32 time=81ms TTL=56
Reply from 74.125.237.51: bytes=32 time=130ms TTL=56
Reply from 74.125.237.51: bytes=32 time=97ms TTL=56
Reply from 74.125.237.51: bytes=32 time=78ms TTL=56
Reply from 74.125.237.51: bytes=32 time=150ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=107ms TTL=56
Reply from 74.125.237.51: bytes=32 time=124ms TTL=56
Reply from 74.125.237.51: bytes=32 time=102ms TTL=56
Reply from 74.125.237.51: bytes=32 time=142ms TTL=56
Reply from 74.125.237.51: bytes=32 time=142ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=137ms TTL=56
Reply from 74.125.237.51: bytes=32 time=190ms TTL=56
Reply from 74.125.237.51: bytes=32 time=234ms TTL=56
Reply from 74.125.237.51: bytes=32 time=91ms TTL=56
Reply from 74.125.237.51: bytes=32 time=48ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=106ms TTL=56
Reply from 74.125.237.51: bytes=32 time=273ms TTL=56
Reply from 74.125.237.51: bytes=32 time=146ms TTL=56
Reply from 74.125.237.51: bytes=32 time=170ms TTL=56
Reply from 74.125.237.51: bytes=32 time=119ms TTL=56
Reply from 74.125.237.51: bytes=32 time=140ms TTL=56
Reply from 74.125.237.51: bytes=32 time=77ms TTL=56
Reply from 74.125.237.51: bytes=32 time=173ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.237.51: bytes=32 time=130ms TTL=56
Reply from 74.125.237.51: bytes=32 time=112ms TTL=56
Reply from 74.125.237.51: bytes=32 time=252ms TTL=56
Reply from 74.125.237.51: bytes=32 time=101ms TTL=56
Reply from 74.125.237.51: bytes=32 time=214ms TTL=56
Reply from 74.125.237.51: bytes=32 time=118ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=208ms TTL=56
Reply from 74.125.237.51: bytes=32 time=131ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.237.51: bytes=32 time=241ms TTL=56
Reply from 74.125.237.51: bytes=32 time=172ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.237.51: bytes=32 time=107ms TTL=56
Reply from 74.125.237.51: bytes=32 time=156ms TTL=56
Reply from 74.125.237.51: bytes=32 time=180ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=152ms TTL=56
Reply from 74.125.237.51: bytes=32 time=44ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=140ms TTL=56
Reply from 74.125.237.51: bytes=32 time=93ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=181ms TTL=56
Reply from 74.125.237.51: bytes=32 time=154ms TTL=56
Request timed out.
Request timed out.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination port unreachable.
Reply from 74.125.237.51: bytes=32 time=26ms TTL=56
Reply from 74.125.237.51: bytes=32 time=25ms TTL=56
Reply from 74.125.237.51: bytes=32 time=23ms TTL=56
Reply from 74.125.237.51: bytes=32 time=27ms TTL=56
Reply from 74.125.237.51: bytes=32 time=74ms TTL=56
Reply from 74.125.237.51: bytes=32 time=29ms TTL=56
Reply from 74.125.237.51: bytes=32 time=25ms TTL=56
Reply from 74.125.237.51: bytes=32 time=23ms TTL=56

Takes a little while for this to start happening after hitting start in Transmission (running on a PC, not the router). Happens before the link is anywhere near capacity though, so it doesn't seem to be an issue with that. Sessions is set to 500 in Transmission, so it's not a stupidly large number either (though not that small). Using PPPoE to connect. Have seen issues like this before when using the modem to connect, but when modem is bridged and using PPPoE with Gargoyle, it used to work fine. Have been away for a while, so not sure which version this issue appeared with. Has anyone else seen similar?

Oh, btw, I changed the IP of Gargoyle to 192.168.1.251...

Edit: Other useful information I probably should have included before:

* Router is a Netgear WNDR3700 (v1).
* QoS is disabled (but I've also seen this happen when enabled with default settings).
* I saw the router reboot once when I was doing this, but haven't been able to reproduce that since.
* New flash of Gargoyle...only settings changed: IP address, Internet connected using PPPoE, MTU to 1454, wireless enabled with WPA2...everything else is default.

[nickba]

Hello and thanks for this wonderful work.

I have a TL-WR1043ND and I am using the latest 1.4.2 firmware.
First I'd like to suggest a feature that is a manual entry in GUI for DSL modem access when in bridge. I know there is a automatic recognition of the modem IP address in bridge when the modem has a DHCP in bridge mode, but almost all modems I tested doens't have DHCP mode in bridge and I have to edit the /etc/ppp/ip-up.d/modemaccess.sh to make it work.

Now the bug: I was running the latest firmware fine for about 9 days when it stopped to update the DNS with DynDNS. Even forcing the update using GUI, it wouldn't update. After a router reboot, it updated it.
This was happening on the 1.3.16 too.(this was the previous firmware before I installed the 1.4.2).

Again, thanks for your great work!

[NL2009]

I also have this DynDNS problem. It looks like the router updates the DynDNS entry once after a reboot, and then never again.

I am running 1.4.2 on a Linksys WRT54GL with 32MB RAM. All other functions seem to be running well (except "Themes" menu is missing).

My router is configured as a Gateway, connecting via PPPoE.

I have had this same problem for quite some time now. I think this last worked correctly in FW version 1.2.x.

[mathew]

I get wireless dropouts on my TL-WR1043N. This has happened in the past, and I usually resolve it by switching back to 802.11g, But now if I set the wireless to 802.11g, my iPhone 4 is unable to access web pages. It appears that is is able to resolve domain names, but always times out trying to load a page.

My macbook still has wireless drop outs in 802.11n and g. I am happy to supply any debug info if it is needed.

[raz]

I get wireless dropouts on my TL-WR1043N. This has happened in the past, and I usually resolve it by switching back to 802.11g, But now if I set the wireless to 802.11g, my iPhone 4 is unable to access web pages. It appears that is is able to resolve domain names, but always times out trying to load a page.

My macbook still has wireless drop outs in 802.11n and g. I am happy to supply any debug info if it is needed.

I experienced the same. I went back to doritos' build, based on 1.3.14:

http://www.4shared.com/file/sWCh2XUu/ga ... 1043n.html

[qtr]

I've been using the v1.4.2 for a few weeks on my WNDR3700v1 after upgrading from v1.3.16 using the web interface. But yesterday I encountered a problem after trying to save a new config. The problem is I cannot see the router anymore and all internet access is lost. I tried for re-flash the router with the v1.4.2 factory image several time, it works but as soon as I tried to save a configuration the problem occurs again.

Now I have to revert back to using the v1.3.16. Appreciate advise/solution on this problem. Thanks

[caeci11ius]

QTR, I also had that issue with mine the other day when saving some QoS settings, but haven't had it recur since, so just put it down to a one-off...router crashed completely, all LAN access was lost and the problem persisted through multiple reboots. Reflashed it via TFTP and it has been ok since, apart from the problem with large numbers of sessions I've noted above...

By the way, given you've got the same router as me...can you see if downloading a torrent with a lot of sessions (say 500 connections) causes difficulties on your setup? Please also comment on whether you're using PPPoE or another method to connect...

Edit: Originally said PPTP where I meant to say PPPoE

[qtr]

caeci11ius, I don't use torrent nor PPTP, and I don't use QoS so I can't comment on their effects. However during the few weeks that it worked on my router I did experience random internet access lost and reset several times. Now I am running v1.3.16 as only a fresh v1.4.2 TFTP works; but when I tried to save a DHCP or a Firewall restriction config. it would just crashed straight away. One more thing I notice was that with dual band channel 36 default for 5G, and the 5GHz transmission power was set to max, whereas the 2.4G tx power was set only to 5dBm. My HP Touchpad even though seating next to the router could only detect a 2/3 power on the 5G channel; but it could detect the 2.4G channel with the full 3/3 power.

[caeci11ius]

I've just flashed to 1.13.16 (had previously been using 1.13.15 with some success prior to using 1.14.2). QTR, it's interesting that you note some connectivity issues too. Please everyone note that I'm not getting at a bit of packet loss (which would be expected on a highly utilized connection) but rather at the big chunk where in my pings it would say "Destination net unreachable"...since I've flashed back, that doesn't seem to be happening any more...