Re: TP-Link TL-MR3420 V2 (2.1)

Hi,

a little question , why since today after patch 12748 there is no snapshot for mr3420 v2 ?


Best Regards

Re: TP-Link TL-MR3420 V2 (2.1)

most likely because the build bots haven't compiled it yet. The new snapshot was dated 15 Feb.

Re: TP-Link TL-MR3420 V2 (2.1)

robthebrew,

the lastest snapshot is dated 18 feb, mr3220 v2 is present, mr3420 v2 not.

Re: TP-Link TL-MR3420 V2 (2.1)

xopal wrote:

I just submitted patch to openwrt dev. #12748 please be patient.

Would you mind resubmitting the patches through the mailing list?
I think the developers stopped accepting patches through trac.

Re: TP-Link TL-MR3420 V2 (2.1)

Hi all,


any news ? New snapshot today without mr3420 v2

Re: TP-Link TL-MR3420 V2 (2.1)

https://dev.openwrt.org/changeset/35964

57 (edited by madmax 2013-03-13 15:30:00)

Re: TP-Link TL-MR3420 V2 (2.1)

Hi,

today I flashed my mr3420 v.2 with the new snapshot, after reboot the the ethernet led is off but my 8 ports switch result connected, trying to ping no result. Using serial port the router start correctly, in network config all seems ok, but ethernet ports dont work.

From Dmesg:

[    0.800000] libphy: ag71xx_mdio: probed
[    0.810000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    1.370000] ag71xx ag71xx.0 eth0: invalid speed specified
[    1.370000] ag71xx: probe of ag71xx.0 failed with error -22
[    1.380000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[    1.930000] ag71xx ag71xx.1 eth0: invalid speed specified
[    1.940000] ag71xx: probe of ag71xx.1 failed with error -22

From Hyper Terminal:

root@OpenWrt:/etc/config# ifconfig eth1
ifconfig: eth1: error fetching interface information: Device not found
root@OpenWrt:/etc/config# ifconfig lan
ifconfig: lan: error fetching interface information: Device not found
root@OpenWrt:/etc/config# ifconfig wan
ifconfig: wan: error fetching interface information: Device not found
root@OpenWrt:/etc/config# ifconfig eth0
ifconfig: eth0: error fetching interface information: Device not found
root@OpenWrt:/etc/config#

Re: TP-Link TL-MR3420 V2 (2.1)

Hi, this firmware works ok on MR3420 v2.2 hardware.

But I need to try client mode wireless (wifi as WAN)
But it comes with wpad-mini, and theres not enough space on /overlay for wpad.
wpad is needed to connect to PEAP over wireless.

Re: TP-Link TL-MR3420 V2 (2.1)

HI, I had flash last snapshot to my MR3420 v2.1.
How can I to install luci? No this pkg in current snapshots...(

Re: TP-Link TL-MR3420 V2 (2.1)

did you bother searching the forum before posting?


hnyman wrote:

....... 184 failed with Luci and those old packages from the previous build were deleted.

185 failed totally, and so did 186 a few minutes ago. Next try tomorrow... "waiting, next in ~ 23 hrs 36 mins".
Apparently one of the buildbots (Nico) can't reach the svn server, and failed rapidly most platforms :-(
http://buildbot.openwrt.org:8010/grid

Re: TP-Link TL-MR3420 V2 (2.1)

Hi!

I have a new TP-Link TL-MR3420 v2.1  .
I tried to get it to work with a Vodafone USB modem K3805-Z.
The modeswitch doesn't work reliably with the factory firmware.
Even the beta firmware the Chinese developers provided didn't help.

So I would like to try OpenWRT.
Here is where the trouble starts.

I decided to use the AR71xx tree.
Sources:
http://wiki.openwrt.org/toh/tp-link/tl-mr3420
More details and specifics for my model here:
http://wiki.openwrt.org/toh/tp-link/tl-ap121
Progress Thread here:
https://forum.openwrt.org/viewtopic.php?id=41326&p=1

Problem:
Adding Support MR3220 V.2 + MR 3420 V.2 to AARC1 12.09-rc1
diff: http://pastebin.com/gzf2VNhK
It seems only to be possible to use this by recompiling the source?!?
And the space required to compile yourself is 5.3-7.6 GIGAbyte !
So I hoped for the patch to be included in the Buildbot generated Snapshots.

Now I run into the trap with the Buildbot not working reliably.
So the good build got erased and I burned a crippled one.

I realised this when LUCI wasn't available.
opkg list | grep luci
came up emtpy.
I found the reason searching the forum.

I patiently waited for
http://buildbot.openwrt.org:8010/builders/ar71xx
to show 'success' for the latest build.

Now I had to decide between factory and sysupgrade build.
Since the installed build wasn't complete I used the bigger factory build.

Begin Quote:
root@OpenWrt:/tmp# wget http://downloads.openwrt.org/snapshots/ … actory.bin
Connecting to downloads.openwrt.org (78.24.191.177:80)
openwrt-ar71xx-gener 100% |*******************************|  3840k  0:00:00 ETA
root@OpenWrt:/tmp# sysupgrade -v /tmp/openwrt-ar71xx-generic-tl-mr3420-v2-squashfs-factory.bin
Saving config files...
etc/sysctl.conf
etc/shells
etc/shadow
etc/rc.local
etc/profile
etc/passwd
etc/inittab
etc/hosts
etc/group
etc/dropbear/dropbear_rsa_host_key
etc/dropbear/dropbear_dss_host_key
etc/config/wireless
etc/config/ubootenv
etc/config/system
etc/config/network_works
etc/config/network_orig
etc/config/network
etc/config/firewall
etc/config/dropbear
etc/config/dhcp
Sending TERM to remaining processes ... syslogd klogd hotplug2 procd ubusd netifd dnsmasq ntpd
Sending KILL to remaining processes ...
Switching to ramdisk...
Performing system upgrade...
Unlocking firmware ...

Writing from <stdin> to firmware ...
Appending jffs2 data from /tmp/sysupgrade.tgz to firmware...
Writing from <stdin> to firmware ...  [w]TRX header not found
Error fixing up TRX header
Upgrade completed
Rebooting system...
login as: root
root@192.168.137.222's password:

BusyBox v1.19.4 (2013-03-24 08:43:13 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
-----------------------------------------------------
BARRIER BREAKER (Bleeding Edge, r36114)
-----------------------------------------------------
  * 1/2 oz Galliano         Pour all ingredients into
  * 4 oz cold Coffee        an irish coffee mug filled
  * 1 1/2 oz Dark Rum       with crushed ice. Stir.
  * 2 tsp. Creme de Cacao
-----------------------------------------------------

End Quote

But LUCI is still missing?
opkg update
opkg list | grep luci
still nothing.

I had a long look at the built-in 'uci' but I realised I would overlook something if I were using this tool alone.

So I followed the instructions from
http://luci.subsignal.org/trac/wiki/Installation
    Add the a line like this to your /etc/opkg.conf to enable the openwrt package repository:
    src luci  http://downloads.openwrt.org/kamikaze/8.09.2/ar71xx/packages
              (I decided my 'architecture' was ar71xx)
    Type opkg update
    For LuCI Essentials: opkg install luci-light
    For LuCI Administration: opkg install luci
    Any modules at your choice: opkg install luci-app-*
    For HTTPS support install the luci-ssl meta package
    Since opkg-installed services are disabled by default, you have to manually enable the web server to launch it on boot:
root@OpenWrt:~# /etc/init.d/uhttpd enable
root@OpenWrt:~# /etc/init.d/uhttpd start

BUT the Result for all install options is:
"Package xyz has no valid architecture, ignoring."
Same result with
opkg list | grep luci

So I have done everything possible I can think of and
I haven't even started with the actual problem I am trying to resolve.

Why is LUCI still not available? Any ideas?

Kind Regards.

Re: TP-Link TL-MR3420 V2 (2.1)

because sometimes some packages (like luci) fail to get built even though the build doesn't totally fail.   

they'll show up again in a few days.

trying to install luci from kikaze branch ... that makes zero sense.

If you're going to install trunk on something and you are somewhat handy with sysadmin type compilation of stuff,  just bite the bullet and build your own.    But yes it takes a surprising amount of space.   it's something like 10GB...  OTOH  that's not exactly a lot of space nowadays (unless you're working with a vpn host)

Re: TP-Link TL-MR3420 V2 (2.1)

Thank you for the fast response.

vhrm wrote:

because sometimes some packages (like luci) fail to get built even though the build doesn't totally fail.   
they'll show up again in a few days.

As far as I understand if the Buildbot says 'success' all the planned packages are in the build.
I can't imagine the snapshots being build on pure luck...

What kind of installation option is the best?
Maybe I have interpreted the sources wrong that I mentioned?
Do you have a hint? I am rather new to OpenWRT...

vhrm wrote:

trying to install luci from kikaze branch ... that makes zero sense.

It is the method to install it manually suggested by the developers .
Who am I to say the Developers got it all wrong?

vhrm wrote:

If you're going to install trunk on something and you are somewhat handy with sysadmin type compilation of stuff,  just bite the bullet and build your own.    But yes it takes a surprising amount of space.   it's something like 10GB...  OTOH  that's not exactly a lot of space nowadays (unless you're working with a vpn host)

I only have a Mobile Broadband connection with a very limited data cap.
So that is not an option.

Kind Regards.

Re: TP-Link TL-MR3420 V2 (2.1)

ok.   maybe you should reopen this bug on the subject for the 4th time:
https://dev.openwrt.org/ticket/10282

i'm sure THIS time it'll be a different cause and different resolution.

i wouldn't be snide, but this is a recurring issue and you clearly haven't searched   about it because it causes people problems all the time and i've personally read about it in at least 4 threads in the past month.    the next problem you'll run into is that once you install trunk you'll only be able to install packages with kernel modules that day since once the repo is rebuilt you'll have version mismatch errors.    this isn't ideal, but that's the way it is currently.

Re: TP-Link TL-MR3420 V2 (2.1)

Hi.

I am also known for my posts sounding harsher then being intended to.
So I will take your post with a grain of salt.

vhrm wrote:

ok.   maybe you should reopen this bug on the subject for the 4th time:
https://dev.openwrt.org/ticket/10282

i'm sure THIS time it'll be a different cause and different resolution.

Thanks for pointing me to that ticket.

vhrm wrote:

i wouldn't be snide, but this is a recurring issue and you clearly haven't searched   about it because it causes people problems all the time and i've personally read about it in at least 4 threads in the past month.

I clearly have searched. I have spent more than 20 hours searching mad . I clearly have found several threads about it. And I clearly have applied the necessary measures expected from an end user. And I clearly have NOT assumed for all the fixes to be defective.
So I clearly could assume the old fixed bugs were fixed for real and the last mentioned bug was the buildbot not working. So when the Buildbot worked successfully I CLEARLY could assume the build to be okay and complete. <tries to cool down, sound of steam hissing>

vhrm wrote:

the next problem you'll run into is that once you install trunk you'll only be able to install packages with kernel modules that day since once the repo is rebuilt you'll have version mismatch errors.    this isn't ideal, but that's the way it is currently.

I would love to use an updateable installation.
Would it be enough to just use the jffs2 version of the snapshot?
Can you point me in the right direction please?

Regards.

Re: TP-Link TL-MR3420 V2 (2.1)

The problem is inherent with using trunk.  For reasons that i'm not aware of in this whole openwrt project they use hashes as part of the version numbers for kernels.   This means, practically, that if anything changes in the kernel then suddenly all the modules in the trunk snapshot are no longer compatible with your "old" kernel.  (even though in practice they most likely are fine, opkg won't install them.   You could prob. force it, but that always leads to headaches down the road).

The problem is somewhat described (illustrated, more than described, i guess )  here :
https://forum.openwrt.org/viewtopic.php?id=41154

There's no real way around it.    Normally, one would run attitude adjustment which doesn't have this problem because it doesn't change.   But that's not a choice if you need stuff that's only in trunk.

The way you deal with it is that if you need to install something new you do an update to the latest snapshot, but then you risk importing new bugs or running into a situation like now where luci is missing.  If there's sysupgrade for your platform you even get to keep most of your settings so it's not so bad.

And you definitely want to run the squashfs snapshots (because they allow failsafe mode).   Only time you would not want the squashf is if you wanted to uninstall a bunch of the default packages and reclaim the space.   But even then you're better off, imo, rolling your own squashfs image.   possibly w/ the image builder, but that's a whole other story.

Re: TP-Link TL-MR3420 V2 (2.1)

Thank you for the very informative post!

vhrm wrote:

Normally, one would run attitude adjustment which doesn't have this problem because it doesn't change.   But that's not a choice if you need stuff that's only in trunk.

I have new hardware with '???' in the 'is it supported' table. So I was only ready to try OpenWRT because the machine was useless to me anyway. To minimize the risk of 'bricking' it I had no choice but to go with the newest build.
And as far as I know the trunk is the newest piece of code available.
I have been studying OpenWRT for 5 days now several hours per day and my head is spinning with tons of confusing information bits.
Your post definitely helped me clear some things up (and  triggered new questions smile ).

vhrm wrote:

The way you deal with it is that if you need to install something new you do an update to the latest snapshot, but then you risk importing new bugs or running into a situation like now where luci is missing.  If there's sysupgrade for your platform you even get to keep most of your settings so it's not so bad.

That will be the path for me. Thanks again.

vhrm wrote:

And you definitely want to run the squashfs snapshots (because they allow failsafe mode).   Only time you would not want the squashf is if you wanted to uninstall a bunch of the default packages and reclaim the space.

That was unexpected. I thought about added flexibility with jff2. But if I have to go the way of burning snapshots anyway you are obviously right.

BTW, the ticket for 'LUCI not available in the latest build' has been closed again after I reopened it. At least a new piece of information has come up: the LUCI packages aren't marked as necessary in the Buildbot. So it comes up with 'success' even if it wasn't a success...

So the path for me as far as I can see is burning trunk snapshots until the next stable release comes up with a checkmark next to my router model.
And I will have to find way to configure it with uci alone.
And I have to find out how to store the configuration information for all tools in /etc/config (or how to manipulate the sysupgrade script configuration file to rescue additional information).

A lot to do.
But at least I can see the path more clearly( wink ) now.
Thanks again and see you in the next thread.

Kind Regards.

Re: TP-Link TL-MR3420 V2 (2.1)

Anyone able to upgrade RAM on this router?

Re: TP-Link TL-MR3420 V2 (2.1)

alphasparc wrote:

Anyone able to upgrade RAM on this router?

I do with Hynix HY5DU121622DTP-D43 for my friend's 3420v2 router.

Re: TP-Link TL-MR3420 V2 (2.1)

Must be my soldering equipment then...

71 (edited by horizn 2013-04-02 12:21:39)

Re: TP-Link TL-MR3420 V2 (2.1)

hi,

i saw the movie about ugrading mr3420 v2 from factory. i do the same, but i dont have web interface only telnet/ssh is working for me. how can i enable web interface on it?

Re: TP-Link TL-MR3420 V2 (2.1)

horizn wrote:

hi,

i saw the movie about ugrading mr3420 v2 from factory. i do the same, but i dont have web interface only telnet/ssh is working for me. how can i enable web interface on it?

You have to build your own image.
Actually I kind of think that all images should include at least some form of webconfig even though I know it is difficult to squeeze packages into 4MB.

Re: TP-Link TL-MR3420 V2 (2.1)

Status update of my adventures with
TP-Link MR3420 v2.1
and the
Vodafone New Zealand USB Modem K3805-Z.

I realized the space limitations of 4MB so accepted to do the configuration without a browser interface.

I gave up for a time around the 26th of March.
Problem is with the USB driver part addressing the hardware not correctly (as far as I can see).
AT commands get corrupted during transfer.

-------------------------
Output under Windows:

at+CFUN=?
+CFUN: (0,1,4),(0-2)

OK
AT+CPIN=?
OK
AT+CPIN?
+CPIN: READY

OK
AT+CGDCONT=?
+CGDCONT: (1-10),"IP",,,(0,1),(0,1)

OK
AT
OK
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
AT+CGDCONT=?
+CGDCONT: (1-10),"IP",,,(0,1),(0,1)

OK
AT+CFUN=1
OK
at+CFUN=?
+CFUN: (0,1,4),(0-2)

OK
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK

-------------------------
Output from OpenWRT:
(Test with picocom)

Test with picocom:

>AT
OK
>ATI
ERROR
>ATZ
ERROR
>AT
OK
>AT&F
ERROR
>ATE1
OK
>ATQ0
ERROR
>ATZ
ERROR
>AT
OK
>AT+CGDCONT=?
+CGDCONT:
ERROR
>AT+CFUN=?
+CFUN:
ERROR

>AT
OK
>ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ERROR
>AT Q0
ERROR
>AT V1
ERROR
>AT E1
OK
>ATS0=0
ERROR
>AT &C1
ERROR
>AT&D2
ERROR
>AT+FCLASS=0
ERROR
>AT+FCLASS=?
+FCLASS:
ERROR

------------------------------------------------

I haven't even turned on the WiFi yet.

Is anyone successfully using the TP-Link MR3420 hardware revision 2.1 with any USB Mobile Broadband modem as an Internet connection?

I will wait and watch the USB bug tracking pages occasionally.

74 (edited by poisonz 2013-04-08 18:33:11)

Re: TP-Link TL-MR3420 V2 (2.1)

alphasparc wrote:
horizn wrote:

hi,

i saw the movie about ugrading mr3420 v2 from factory. i do the same, but i dont have web interface only telnet/ssh is working for me. how can i enable web interface on it?

You have to build your own image.
Actually I kind of think that all images should include at least some form of webconfig even though I know it is difficult to squeeze packages into 4MB.

Agreed. Though for newbies, kernel compilation is a daunting time consuming (and also HDD space consuming) task. It's better leave it to those who are experienced first.

Fortunately, there is already a working (user-compiled, non-official) OpenWRT image (Attitude Adjustment 12.09 RC1) for MR3420 v2 over the internet @ openwrt-id.org.

I've flashed it to my TL-MR3420 v2.1 and it's working well for me, with only some minor issues (LED & button), without impairing its basic functionality: Ethernet works, USB works, 3G OK, WAN and WLAN also work nicely (speaking of wireless, the Atheros chipset on the router {802.11n + 2T2R MIMO} far out-performed most other USB WiFi adapter on the market; and the ath9k / mac80211 drivers come with it does support packets injection on aircrack-ng suite either, allowing me to have quite some fun with it :).

Best thing is, it comes preinstalled with LuCI web-interface version 0.11+svn9599-1, which is even more updated than the one from the current OpenWRT AA-RC1 package repository (0.11+svn9425-1).

I can use ExtRoot with USB flash drive with it (with some tricky adjustment). And by adding a USB hub (or hubs?), there is even more we can do with this little baby... :o)  OpenWRT is really powerful!

... But the problem is, there are some packages I wanna try which is a bit outdated (eg. ettercap: OpenWRT=NG-0.7.3-2, latest=0.7.6) or even missing (eg. dsniff) from the latest package repository. Well, Kernel / package compilation is the way to go. I'm learning...

Re: TP-Link TL-MR3420 V2 (2.1)

poisonz wrote:

Fortunately, there is already a working (user-compiled, non-official) OpenWRT image (Attitude Adjustment RC1) for MR3420 v2 over the internet @ openwrt-id.org.

Thank you for the fast response!

Unfortunately I can't find the mentioned OpenWRT image on the page you linked?
There seems to be only a copy from this forum where the steps are mentioned to compile it yourself for hardware revision 2 (not 2.1):
https://forum.openwrt.org/viewtopic.php?pid=188467#p188467