MartyT
join:2004-09-03
Georgetown, SC | WRTP54G with 5.01.04 firmware Have any of the hacking kings here messed with the new firmware for this device? See the links below for details.
»www.vonage-forum.com/ftopic20381.html
In the above forum, someone talks about using this firmware on a WRTP54G.
»wiki.openwrt.org/OpenWrtDocs/Har···/WRTP54G
The actual code is apparently available here, located right after the 3.1.24 fw. If the link on this forum is taboo, please advise and I'll remove it.
I have an unlocked WRTP54G that is currently running 3.1.24. It was not reliable for me, and has been boxed away for a while, potentially for sale to someone on eBay.
I've been running an SPA-1001 behind a Tomato based Buffalo router since I retired the WRTP. After I started using port forwarding, instead of simply putting the SPA in the DMZ, I've had zero problems. When the SPA-1001 was in the DMZ, I'd have occasional one way audio problems.
My VOIP provider, Vitelity, suggested the port forwarding instead of the DMZ approach, indicating that consumer level routers don't do DMZ well, even with Tomato FW. They were right. I recommend them highly, for good advice and good service.
If the latest FW for the WRTP does anything to improve things on what I've always considered a dodgy device, I'd probably install it for a friend that is looking to move to VOIP rather than selling it.
Has anyone taken the leap with this new firmware? |
|
|
|
maziloFrom MaziloPremium
join:2002-05-30
Lilburn, GA
kudos:1 | said by MartyT:Have any of the hacking kings here messed with the new firmware for this device? I tried to mod this firmware and it seems to be incompatible with my WRTP54G-ER unit. Someone who has a Linksys/Vonage locked RTP300 runs on this v5 firmware let me play a bit. I tried to unlock this devive using a config.bin hack and it didn't work. According to the owner of this RTP300 unit, CYT unlocker won't work neither.
I have an unlocked WRTP54G that is currently running 3.1.24. It was not reliable for me, and has been boxed away for a while, potentially for sale to someone on eBay. If you have an unlocked WRTP54G-ER based on the JTAG approach, can you tell us what kind of problems had you encoutered with your WRTP54G unit? Someone who unlocked his WRTP54G-ER using the JTAG approach ran into lots of problems. With the backup he made, he was able to flash back the chunck he removed during the JTAG procedure. Then, he unlocked it using sn9 approach. Since then, his unlocked WRTP54G-ER works without any problems.
When the SPA-1001 was in the DMZ, I'd have occasional one way audio problems. You should try using the STUN options on your SPA1001 instead of ports forwarding. |
|
MartyT
join:2004-09-03
Georgetown, SC | My unit was originally a Vonage device, not ER. I unlocked it using the CYT unlocker approach. Sorry you weren't able to get the new FW to work for you.
I thought your service provider had to support STUN before you could use it on your ATA. To my knowledge, Vitelity doesn't support STUN. If that isn't the case, please advise. |
|
maziloFrom MaziloPremium
join:2002-05-30
Lilburn, GA
kudos:1 | said by MartyT:My unit was originally a Vonage device, not ER. I unlocked it using the CYT unlocker approach. Sorry you weren't able to get the new FW to work for you. So, you were able to use CYT unlocker to unlock your Linksys/Vonage locked WRTP54G runs on firmware v5, right? If so, what version of CYT unlocker and/or parameter did you use?
I thought your service provider had to support STUN before you could use it on your ATA. To my knowledge, Vitelity doesn't support STUN. If that isn't the case, please advise. AFAIK, you can still use any open/public STUN servers (I mostly use stun.fwdnet.net, stun.voipuser.org, etc.) to configure your unlocked WRTP54G device to register with Vitelity services. |
|
MartyT
join:2004-09-03
Georgetown, SC | no, the Vonage locked WRTP54G originally had a version 1 FW installed.
I'll ckeck out the public stun servers. Thanks. |
|
maziloFrom MaziloPremium
join:2002-05-30
Lilburn, GA
kudos:1 | said by MartyT:no, the Vonage locked WRTP54G originally had a version 1 FW installed. So, you WRTP54G had v1 firmware installed and you used CYT unlocker to unlock it and then flashed your unit with v5 firmware? |
|
MartyT
join:2004-09-03
Georgetown, SC | No, it is still running 3.1.24. The purpose of my post was to see if anyone was able to get v5 running on an unlocked Vonage unit that has already been thru the CYT unlocking process. |
|
| reply to MartyT
I have been able to unlock my WRTP54G, and have been able to flash with v5 firmware, however, it seems after a little while, the backup firmware reflashes the router to the latest Vonage version 1.00.62. From my understanding, this firmware is backed up on the router, hence when I do a factory reset, this firmware also gets reloaded. Is there any way to prevent this from happening, or at least overwrite the backup firmware? |
|
maziloFrom MaziloPremium
join:2002-05-30
Lilburn, GA
kudos:1 | said by phishstics :
Is there any way to prevent this from happening, or at least overwrite the backup firmware? AFAIK, you will need to disable provision options. OTOH, you can try to flash your WRTP54G with a modded WRTP54G-NA firmware, and it won't be able to make contacts with Vonage to get provisioned, IIRC. |
|
MartyT
join:2004-09-03
Georgetown, SC | reply to phishstics
You unlocked a locked WRTP54G and flashed it with v5 firmware?
How??? Who was it locked to originally? |
|
| reply to MartyT
I used CYT 4.6 to get the admin password changed, then flashed with the v5 firmware found on the Openwrt wiki page. However, it seems as though the router reverts right back to 1.00.62 after a little while. Confirming this again now.
Presently running 5.01.04. I have no use for Vonage anymore, I just turned my service off yesterday (switched to cable company's phone service), which is what started this madness. Thought I had bricked it earlier when trying to flash with 3.1.24 found on that page, but a manual factory reset fixed it, and its making me a little leery of playing around more. |
|
 meister_sdPremium
join:2006-01-29
La Mesa, CA
kudos:7 | said by phishstics :
However, it seems as though the router reverts right back to 1.00.62 after a little while.
You need to go the provisioning area and turn off provisioning. Send it to loopback - 127.0.0.1. CYT should have done this for you. |
|
| reply to MartyT
I am having a hard time finding it, but if I run CYT on the router again with the new firmware, it should disable it right? |
|
| reply to MartyT
got in through /provision.html ...and yes CYT already took care of it. I am successful in running the v5 firmware and its been up for over an hour. |
|
MartyT
join:2004-09-03
Georgetown, SC | Please keep us posted on your results and on any additional features you might find. I'm simply interested in this from a reliability standpoint, as my unlocked WRTP54G running FW v3.1.24 was never stable like my SPA-1001 with a tomato router. |
|
MartyT
join:2004-09-03
Georgetown, SC | phishstics, I tried upgrading my 3.1.24 FW to 5.01.04 after seeing your post, but I get the following error after the progress bar goes all the way to 100%:
"Unable to write to MTD block device"
I am able to re-enter the system after this normally using the old firmware.
Based on your post, I'm assuming you, like me, orginally had a locked Vonage WRTP54G.
Wonder why the FW upgrade worked for you but not for me? |
|
maziloFrom MaziloPremium
join:2002-05-30
Lilburn, GA
kudos:1 | said by MartyT:"Unable to write to MTD block device" That's exactly what I saw on my WRTP54G-ER device when trying to flash it with the Vonage v5 firmware. |
|
MartyT
join:2004-09-03
Georgetown, SC | phishstics indicated he took his Vonage locked device directly to 5.01.04. perhaps the fact that we have devices that have already been reflashed once has something to do with it? |
|
| reply to MartyT
After deciding to go back to the previous firmware I had (1.00.62) because of issues with v5.01.04, I decided to check back here and see your posts.
To be honest, I only start messing around with this stuff a couple days ago, and am kind of learning on the fly. The only difference I see between what you're doing and what I did is that you are attempting to flash from the version 3 firmware, whereas I flashed directly from the latest Vonage 1.00.62 to version 5.01.04. If you use CYT on that version, you can easily flash to the version 5 found on the wiki. Interesting to note, I almost bricked my router by trying to update to the 3.24 (?) version that is up there.
Now onto the reason I went back. Stability. I use another PC in my house pretty regularly through RDC and found the performance to be mediocre at best with the 5 firmware loaded on the router. It would periodically hang up for a few seconds while typing or clicking which was getting pretty annoying. So I dealt with that all day, and then the internet went down...or so I thought. After connecting to my neighbors unlocked wireless (same cable provider, different brand router altogether), and saw I was able to surf, I knew something was up with the router. Did a factory reset and allowed the router to download the 1.00.62 firmware and all is peaches. RDC performance is improved as well.
So I don't know what I am going to do. This version was stable for the entire year I have had this router from Vonage. I no longer need the Vonage service, nor do I need the ports, so I may just CYT again and remove the provisioning link. Or maybe try v3? Who knows... |
|
maziloFrom MaziloPremium
join:2002-05-30
Lilburn, GA
kudos:1 | said by phishstics :
The only difference I see between what you're doing and what I did is that you are attempting to flash from the version 3 firmware, whereas I flashed directly from the latest Vonage 1.00.62 to version 5.01.04. If you use CYT on that version, you can easily flash to the version 5 found on the wiki. Interesting to note, I almost bricked my router by trying to update to the 3.24 (?) version that is up there. I tried to flash v5 firmware on my WRTP54G-ER that ran on v1.00.62 Vonage firmware and got the error message of Unable to write to MTD block device. I flashed back my WRTP54G-ER to v3.1.24 firmware and tried again to flash with v5 firmware to get the same error message. |
|
