do you need a dsl module for it? i think broadcom removes it in 6359.
BrainSlayer wrote:
the bootloader is a simple broadcom cfe based one with a integrated webserver. i have all sourcecodes for these devices including the sourcecodes for the bootloader. but i always stopped working on it when i had some time due the internal adsl part. its hard to write something generic for it since the ADSL protocol is different in many countries. here in germany annex-b is normal. in other countries its annex-a and there are other variants too
Posted: Mon Mar 01, 2010 14:42 Post subject: Westell 7501 with DSL?
The Westell [b]7500[/b] is a combo DSL modem and router. The Westell [b]7501[/b] is a router only and will work with virtually any modem-cable or dsl as long as it has a RJ45 connection. What problem can be solved with a "dsl module" on the router? You want to turn it into a modem? That's the 7500, not the 7501.
Broadcom frequently disables (read-fuses)parts of their chips for different applications. I suspect that the 6359 is a 6358 without the DSL modem function. Of course, I've been wrong before.
Posted: Wed Mar 03, 2010 0:48 Post subject: A NEW issue with the Westell 7501
I haven't heard anyone post anything regarding this issue so here goes.
It would appear that no matter what firewall setting I choose, port 4567 remains OPEN. And I can't seem to find a setting to change this!
So just what is Port 4567?
If you google this port, it is known as a backdoor for Verizon to do remote login of their equipment. Well, not only do dislike the idea of Verizon sneaking in, but I don't like leaving the port OPEN for hackers to find!
Want to see for yourself? If you don't have access to port scanner on a friends computer, try going to the online Norton Security Scanner, that's how I found it in the first place.
Posted: Wed Mar 03, 2010 5:34 Post subject: Re: A NEW issue with the Westell 7501
Unit-1 wrote:
I haven't heard anyone post anything regarding this issue so here goes.
It would appear that no matter what firewall setting I choose, port 4567 remains OPEN. And I can't seem to find a setting to change this!
So just what is Port 4567?
If you google this port, it is known as a backdoor for Verizon to do remote login of their equipment. Well, not only do dislike the idea of Verizon sneaking in, but I don't like leaving the port OPEN for hackers to find!
Want to see for yourself? If you don't have access to port scanner on a friends computer, try going to the online Norton Security Scanner, that's how I found it in the first place.
If off topic posts persist, someone is going to get p*ssed. Please look at the topic title before posting. And don't assume nothing is being done just because the thread is not updated hourly.
Posted: Thu Mar 04, 2010 21:06 Post subject: Re: A NEW issue with the Westell 7501
exnetgear wrote:
If off topic posts persist, someone is going to get p*ssed. Please look at the topic title before posting. And don't assume nothing is being done just because the thread is not updated hourly.
Is there anywhere on DD-WRT's site to check if any work is in progress on these? I know about the router database lookup, and occasionally scan through the front page articles, but just want to make sure I'm not missing something.
Is there anywhere on DD-WRT's site to check if any work is in progress on these? I know about the router database lookup, and occasionally scan through the front page articles, but just want to make sure I'm not missing something.
Probably it's better to file a ticket to implement support of Verizon/Westell 7501 router and just watch it. When it's resolved -- the support has been implemented.
I don't know how some of you have come to the conclusion that support for this router is being worked on by the dd-wrt developers - it ain't.
None of them has declared that he has time or interest in doing the job so far, that is the first thing that must happen.
Using the trac system for requesting dd-wrt support of a router is abuse of the trac, it is intended for bug reporting on currently supported routers.
The developers, if they agree to work on support for the router, will need a router to work on and they are not gonna buy it with their own money.
Someone has to donate a router and it will not be returned, it will be used for development in the future as well as to test on if bug reports are filed for the router.
I believe that 2 donated routers is needed this time, Tornado will also need one to implement and maintain jtag support for it.
A dd-wrt developer can probably not do any work on the router before it has jtag support.
Shouldn't be any problem since the router is so cheap,right?
So lets se now if there are any of you who are able to organize this. Wishful thinking, "me too" and "when will it be done" posts doesn't take the development a single step further. _________________ Kernel panic: Aiee, killing interrupt handler!
Just for the record, I gave the link to the timeline to answer the question about where someone could RESEARCH the progress (or lack of it), not so that people would heckle the devs in yet another way.