Version 1.5.2 & 1.4.5

[kris87]

I'm using this 1.4.5 version of firmware on a TP-Link 741nd router and I have a problem with it.

I'm running an ftp server on my pc. I opened the port 21 in firewall and it works now from WAN, but doesn't work from LAN. My oc is connected to routher by wirelessly.

PS.: As I connect my pc to routher with an utp cable, it works from LAN too. Something is wrong with wifi...

[frank604]

Quick question. I've been running 1.5.2 for 2 days or so. Wifi went down and the only msg out of place was xt_TCPMSS: bad length (40 bytes)
Repeating about 5 times. Is this the culprit and should I be concerned?

mini_fo: using base directory: /mini_fo: using storage directory: /over
ar71xx-wdt: enabling watchdog timer
br-lan: port 1(eth0.1) entering disable
device eth0 left promiscuous mode
device eth0.1 left promiscuous mode
br-lan: port 1(eth0.1) entering disable
eth1: link down
device eth0.1 entered promiscuous mode
device eth0 entered promiscuous mode
br-lan: port 1(eth0.1) entering forward
ar71xx: pll_reg 0xb8050014: 0x11110000
eth1: link up (1000Mbps/Full duplex)
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwardi
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwardi
device wlan1 entered promiscuous mode
br-lan: port 3(wlan1) entering forwardi
device wlan1 left promiscuous mode
br-lan: port 3(wlan1) entering disabled
device wlan1 entered promiscuous mode
br-lan: port 3(wlan1) entering forwardi
xt_TCPMSS: bad length (40 bytes)
ath: Failed to stop TX DMA, queues=0x00
ath: DMA failed to stop in 10 ms AR_CR=
ath: Could not stop RX, we could be con
ath: Failed to stop TX DMA, queues=0x00
ath: DMA failed to stop in 10 ms AR_CR=
ath: Could not stop RX, we could be con
xt_TCPMSS: bad length (40 bytes)
xt_TCPMSS: bad length (40 bytes)
xt_TCPMSS: bad length (40 bytes)
xt_TCPMSS: bad length (40 bytes)
xt_TCPMSS: bad length (40 bytes)
xt_TCPMSS: bad length (40 bytes)
xt_TCPMSS: bad length (40 bytes)
root@Gargoyle:~#

[mix]

I think the real error message is the failed to stop dma error which is so common on Atheros devices.

[cosmo1t]

wndr3700 no ext root, running 1.5.1
sysupgrade to 1.5.2

bricked.

had to tftp img file to it to get it up and running again

[Dragon31337]

I can't find TOR settings in 1.5.2 on my TPLINK 1043. =( WHY? It was there on 1.5.1.

[Draak]

That's because "Tor is disabled on routers with less than 64MB of memory" for 1.5.2 and your has only 32MB.

[hnl_dk]

I can't find TOR settings in 1.5.2 on my TPLINK 1043. =( WHY? It was there on 1.5.1.

There is not enough memory in the router... it should not have been enabled in 1.5.1. on your router.
If you wish, use a SWAP partition on a USB disc, then you should get enough memory to be able to enable TOR.

[ispyisail]

If you wish, use a SWAP partition on a USB disc, then you should get enough memory to be able to enable TOR.

True

works well

[Dragon31337]

SO if I plug in an USB and make a swap file there - I'll get TOR options in the web admin?

[hnl_dk]

SO if I plug in an USB and make a swap file there - I'll get TOR options in the web admin?

Yes, if you make a SWAP partition on a flashkey or something like it, then you will be able to enable TOR.
Check this thread: http://www.gargoyle-router.com/phpbb/vi ... 9877#p9877