Welcome Guest ( Log In | Register )

Bump Topic Topic Closed RSS Feed
5 Pages < 1 2 3 4 > » Bottom

Outline · [ Standard ] · Linear+

 Tp LInk TL-MR3420 Owner CLub V2.5, need a pro here

views
     
maxcheam
post Apr 18 2013, 10:32 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(winyap991 @ Apr 18 2013, 09:21 AM)
Last time i use this OpenWrt Attitude Adjustment 12.09-rc1 - OpenWrtID / LuCI 0.11 Branch (0.11+svn9599) all fine but after upgrade to Back window or Huntsman cannot access to Internet.

I follow this step to setting RC1
- login 192.168.1.1 ( you will see LuCI Gui interface )
- click login
- go to System
- go to Administration
- key in your new password ( For web Gui )
- re key in your same password again
- click save and apply
- go to Network
- click Edit on Wan ( 3G wan )
- select UMTS/GPRS/ED-VO protocol
- click switch protocol
- Modem device ( ZTE modem = /dev/ttyUSB1 , Huawei modem = /dev/ttyUSB0 <- last is zero )
- service type : select UMTS only or UMTS/GPRS
- Key in your ISP APN , ( Unet, Maxisbb, bbnet, celcom3g, u3g, my3g and so on )
- Go to ADvance setting
- Modem init time out: 5 ( key in )
- Use gateway Metric : 0
- Tick the box of : if uncheck, No default route is configure
- Use custom DNS server : 8.8.8.8 click the icon at the end
- second roll: 8.8.4.4
- LCP echo failed Threshold : 0
- LCP echo interval : 5
- Inactivity timeout: 0
- select Wifi
- click Edit
- select your wifi prefer channel 1~11
- enter your wifi name in ESSID
- go to Wireless security
- encryption : WPA2-PSK
- key : wifi password
- click save and apply
- then click enable to on your wifi ( if u need it )
- now go to System
- Reboot
- click Performs reboot
- plug in your Usb modem after
- wait for reboot finish and enjoy

Why?

I use V2 3420 + ZTE MF680 modem

TQ
*
The way ROOter firmware works is slightly different than the original OpenWRT firmware. You should follow the guide that Wahroonga Farm pointed out.
maxcheam
post Apr 19 2013, 05:27 PM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(chuahcs79 @ Apr 19 2013, 01:03 PM)
after mine hang, the usb modem is not recognizable, and no matter how many time reboot still same,  sad.gif
*
This is a common problem for me even before ROOter firmwares but it rarely happens. When it does happen, I just need to unplug the modem from the router making sure that no more power supplies to it and plug it back in. But need to repeat a few times until it register to the cell tower correctly.

I think this is an issue at the telco side especially when they reset your SIM/account or the system at the tower is reset.

As for using Huntsman, I don't have much issue except for enjoying the new features. It doesn't matter if it's 04-14 or 04-19 version
maxcheam
post Apr 19 2013, 05:30 PM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(miezaidin @ Apr 19 2013, 03:31 PM)
wanna change back to stock firmware..... doh.gif ...

change to E372...be like this...
*
This is a new way of connecting for Rooter firmware. You'll see it if you're using modems that support QMI-to-WWAN. It's supposed to bypass 25Mbps limitation of PPP dialing method.
maxcheam
post Apr 21 2013, 08:26 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



I take back my words about not having any issues with Huntsman firmware. I did a few more tests yesterday and found out that if I'm using "Enabled with Restart" for Connection Keep Alive under Modem > Connection tab, the connection won't be kept alive if it's idle for too long. I'm not sure if it's telco specific but for Maxis, it's almost consistent. The only way to get back the connection is to either reboot the router or take out the modem and plug it back in.

Perhaps Dairyman or Wahroonga Farm can check it out.

All this while, I've been using "Enabled" without the restart because I have my own scheduled tasks to monitor the connection and restart if necessary. That's why I don't have much issue if the connection got stuck.
maxcheam
post Apr 21 2013, 08:40 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(BladeRider88 @ Apr 21 2013, 08:29 AM)
Thanks for the sharing...i do facing the same issue if i am using "Enabled with Restart" for Connection Keep Alive
May i know is it you use this command:

* * * * * /bin/ping -q -s 1 -c 60 8.8.8.8 & > /dev/null


as your own scheduled tasks to monitor the connection and restart if necessary?
*
that command is to keep the connection alive by pinging Google DNS every minute but doesn't do anything else.

I'm using this:
*/5 * * * * /bin/ping -c 10 openwrt.org || reboot

It will ping openwrt.org every 5 minutes with 10 tries and will run the reboot command if one or more out of the 10 pings failed. You can change the schedule to a shorter/longer time or a different address to ping depending on your preference.

I can't guarantee that it will fix the issue though 'cause we'll need more time to test it out. However, at least the logic of it make sense. whistling.gif

This post has been edited by maxcheam: Apr 21 2013, 08:41 AM
maxcheam
post Apr 21 2013, 08:44 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(BladeRider88 @ Apr 21 2013, 08:42 AM)
i see...well, i will try to use the command and settings that you mention above and see what happen next.

To be honest, with the Huntsman's feature, i feel reluctant to use the AA version  laugh.gif
*
haha.. same here! sweat.gif
I don't think I'll ever turn back to other version without those features. thumbup.gif
maxcheam
post Apr 22 2013, 10:49 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(maxcheam @ Apr 21 2013, 08:40 AM)
that command is to keep the connection alive by pinging Google DNS every minute but doesn't do anything else.

I'm using this:
*/5 * * * * /bin/ping -c 10 openwrt.org || reboot

It will ping openwrt.org every 5 minutes with 10 tries and will run the reboot command if one or more out of the 10 pings failed. You can change the schedule to a shorter/longer time or a different address to ping depending on your preference.

I can't guarantee that it will fix the issue though 'cause we'll need more time to test it out. However, at least the logic of it make sense.  whistling.gif
*
latest update on my tests:
It seems that adding the scheduled task doesn't solve the issue. From my observation, when the issue happen, none of the scheduled tasks run. I'm assuming that cron service somehow froze up.

Here's what I'm testing now:
Take out the original scheduled task added in ROOTer firmware to keep the connection alive but leave my own tasks intact. I restart the cron service on the safe side to ensure that it will run the new config.
*/2 * * * * /etc/root <--- deleted this

maxcheam
post Apr 23 2013, 08:38 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(maxcheam @ Apr 22 2013, 10:49 AM)
latest update on my tests:
It seems that adding the scheduled task doesn't solve the issue. From my observation, when the issue happen, none of the scheduled tasks run. I'm assuming that cron service somehow froze up.

Here's what I'm testing now:
Take out the original scheduled task added in ROOTer firmware to keep the connection alive but leave my own tasks intact. I restart the cron service on the safe side to ensure that it will run the new config.
*/2 * * * * /etc/root  <--- deleted this
*
unfortunately, this doesn't work either. Confirmed that cron daemon isn't working when the issue happen. I tried to start manually using command "/etc/init.d/cron start but got an error:
crond: invalid number /dev/null

I decided to revert back the command in /etc/init.d/cron:
start () {
loglevel=$(uci_get "system.@system[0].cronloglevel")
[ -z "$(ls /etc/crontabs/)" ] && exit 1
mkdir -p /var/spool/cron
ln -s /etc/crontabs /var/spool/cron/ 2>/dev/null
service_start /usr/sbin/crond -c /etc/crontabs -l ${loglevel:-5} <-- Was commented out
# service_start /usr/sbin/crond -c /etc/crontabs -l /dev/null <-- Currently commented out this
}

I'm able to start cron after that. Monitoring in progress.

This post has been edited by maxcheam: Apr 23 2013, 08:39 AM
maxcheam
post Apr 23 2013, 09:43 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(digilife @ Apr 23 2013, 09:39 AM)
It seems that BW 2013.04.04 is much stable after all ?
*
it seems so but I'm not looking back. whistling.gif
maxcheam
post Apr 23 2013, 10:36 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(Wahroonga Farm @ Apr 23 2013, 10:28 AM)
The later Black Widow and Huntsman builds have introduced instability for some modems.

We are currently working back through the ROOter additions to isolate the problem(s).

Your testing has been invaluable as it identified the modem instability and the keep alive function failure which had not beenreported elsewhere.  rclxms.gif

... Back with an update when there is more news.

Cheers
*
Thanks for the update and the hard work as usual! So far, both of the modems (Huawei E398 & Huawei E367) that I'm using are experiencing these problem. I'll continue to post my test results.
maxcheam
post Apr 24 2013, 03:12 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(akping_1 @ Apr 24 2013, 12:44 AM)
user posted image

saw this when connect n using the previous password with putty

should me my hard reset dint work n the password still exist right?
*
The Web GUI - LuCI probably didn't run properly. Try to run this command after you've logged in via PuTTY:
/etc/init.d/uhttpd start

I occasionally have to do this sometimes when using ROOter firmwares.

This post has been edited by maxcheam: Apr 24 2013, 03:13 AM
maxcheam
post Apr 24 2013, 10:24 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(akping_1 @ Apr 24 2013, 08:56 AM)
this is the msg i get from putty

"root@akping:~# /etc/init.d/uhttpd start
Failed to load ustream-ssl library: File not found "
*
Looks like you have some missing packages problem. Like many here have mentioned, your previous configurations were carried over where you kept the configs when flashing the firmware.

to make things easier, just do a factory reset to solve your problem. Since you're still able to access SSH, you might want to try this command:
/sbin/firstboot

it should reset your router. You can confirm it when the WiFi SSID change to the default OpenWRT.

This post has been edited by maxcheam: Apr 24 2013, 10:51 AM
maxcheam
post Apr 24 2013, 10:44 AM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(chuahcs79 @ Apr 24 2013, 03:59 AM)
am still using the above AA version for my mr3040V1 ,. so far is the most stable and best in consistency openwrt,..

thumbup.gif

reason to support my statement above is my load normally always between 0.21~0.25 only,..

which when i use blackwidow or huntsman, my loads is between 0.79~0.98  sweat.gif
router load when running torrent 0.21~0.25
[attachmentid=3407212]
router load when not running torrent 0.3~0.10
[attachmentid=3407218]
and when the router load running too high, sometimes the webinterface 192.168.1.1 become unresponsive and the wireless connection get affected like request time out too,..  sweat.gif

so before anyone of you think is the temperature issue for the wireless connection, this is how i setup my MR3040 V1 + Huawei E1820 ( with usb mini usb table fan blowing )
so it is not the temperature issue

[attachmentid=3407220]
*
here's my load average running on Huntsman 04-19 with MR3420 V1, loading the page from my office via Public IP:
Attached Image

I've been running this version happily ever since I found the manual fix for cron. I'll have to stick with this version as I still need the DDNS package. thumbup.gif
maxcheam
post Apr 24 2013, 12:56 PM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(BladeRider88 @ Apr 24 2013, 11:32 AM)
Care to share with me your cron settings? As i still having the same issue  sweat.gif
*
I've shared this before but here I go again:
Assuming you just flashed your router without keeping the previous configuration to Huntsman 04-14 or 04-19, edit the following file after - /etc/init.d/cron to be exactly like this one shown below. Note the # sign in red:
start () {
loglevel=$(uci_get "system.@system[0].cronloglevel")
[ -z "$(ls /etc/crontabs/)" ] && exit 1
mkdir -p /var/spool/cron
ln -s /etc/crontabs /var/spool/cron/ 2>/dev/null
service_start /usr/sbin/crond -c /etc/crontabs -l ${loglevel:
# service_start /usr/sbin/crond -c /etc/crontabs -l /dev/null
}

Do a restart after this. No need to add any additional scheduled tasks but make sure you choose either "Enabled" or "Enabled with Restart" in the Modem's Keep Connection Alive option.


maxcheam
post Apr 24 2013, 01:17 PM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(digilife @ Apr 24 2013, 01:03 PM)
so a "new virgin image" ?

to be flashed on which version of the Huntsman ?

thanks

notworthy.gif  notworthy.gif
*
correct, that's what I meant, a "virgin" image. tongue.gif

You can use either 04-14 or 04-19 version. The newer firmware version that Wahroonga Farm mentioned should have gotten that fixed. But, it's only a limited number of models supported. I guess most of you are using MR3420 V1, that is available.
maxcheam
post Apr 24 2013, 01:20 PM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(chuahcs79 @ Apr 24 2013, 01:04 PM)
i did test with the hutnsman 4-19, my averages load was always very high even there is no internet traffic loading,.  sweat.gif
*
Give it a 2nd chance? biggrin.gif
maxcheam
post Apr 24 2013, 01:26 PM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(digilife @ Apr 24 2013, 01:21 PM)
Both my 1043ND and MR3420 are running HM 04-14, only MR3420 fakap on me, whereas 1043ND works flawlessly.

Maybe 1043ND have a bigger flash (8MB) , hence less problem detected.

hmm.gif  hmm.gif
*
Booting the routers from cold shouldn't be a problem. the only problem you'll be experiencing without making the change would be 3G connection will not reconnect after a disconnection. Not sure if this is the problem you see on your MR3420. Have you use your 1043ND long enough to experience the problem?
maxcheam
post Apr 24 2013, 01:33 PM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(digilife @ Apr 24 2013, 01:30 PM)
My 1043ND session starts at 11.30pm > 10.30am , not even an IP change sometimes............mostly streaming sky.fm  classical jazz  biggrin.gif
*
if IP didn't change means it hasn't disconnect and thus, you won't see the issue. It's nice that your 1043ND can always maintain a connection.
maxcheam
post Apr 29 2013, 05:50 PM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



No issue getting connected using Huntsman 04-30 version on MR3020 and E398. Currently, monitoring it's stability before upgrading the rest of my fleet of TP-Link routers. biggrin.gif
maxcheam
post Apr 29 2013, 10:19 PM

Casual
***
Junior Member
384 posts

Joined: Jan 2006
From: Penang



QUOTE(hurricane21 @ Apr 29 2013, 07:29 PM)
No idea what happened, i try to downgrade from 04-23 to 04-19 then upgrade again to 04-30, surprisingly now its working, no more disconnect hmm.gif

BTW sierra modems only can use DCHP client? i tried UMTS/GPRS/EVDO and PPP mode but end up get no connection. hmm.gif
*
QUOTE(chuahcs79 @ Apr 29 2013, 08:43 PM)
just tested the hunstman 4-30 with my MR3040V1

it can auto detect and dial even though the network status showing wrong port or detail display is haywire,..

[attachmentid=3417082]
[attachmentid=3417083]
*
I see that many of you have a wrong impression about ROOter firmwares (namely Redback, BlackWidow and Huntsman) although Dairyman and Waroonga Farm have mentioned before. Note that it's a customized version of OpenWRT which optimize for 3G/4G usage. The only configuration you need to worry about for making 3G/4G connection is at the Modem tab (APN name, Username, Password, SIM PIN, Keep Connection Alive, DNS servers). You don't need to mess with the configurations in the Network tab 'cause whatever you do over there will be overwritten by a scheduled task.

And the Network Status at the Modem tab it's just informational, it doesn't affect your connection at all.

I hope we don't get confused with the original OpenWRT releases. To understand better about ROOter firmwares, please read information on this page - http://www.rfactory.org/OpenWRT/

This post has been edited by maxcheam: Apr 29 2013, 10:24 PM

5 Pages < 1 2 3 4 > » Top
Topic ClosedOptions
 

Change to:
| Lo-Fi Version
0.0542sec    0.35    7 queries    GZIP Disabled
Time is now: 14th December 2025 - 03:16 AM