1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Enabling telnet access on WAG200G [is it possible?]

Discussion in 'Other Linksys Equipment' started by Slaytanic, Nov 1, 2006.

  1. Slaytanic

    Slaytanic LI Guru Member

    yesterday I've bought the WAG200G-EU (Annex A) ADSL Wireless Router and I've immediately started playing with it.. I've been quite surprised by the fact that it does not allow telnet access for configuration, providing only the Web interface.. So, I downloaded the firmware sources and looking into the filesystem that is copied onto the device, there is also the utelnetd file (in /usr/sbin if I remember well).. So, my question are:
    1) Why didn't they enable telnetd? Only because it is not a business product (as a linksys operator told me)?
    2) Do you think it is possible to enable the telnet daemon without modifying the firmware?
    3) Are there modified/non-official firmwares for this router?

    I hope some of you will point me in the right direction ;-)
  2. greg9905

    greg9905 LI Guru Member

    WAG200G looks to be good. Anyone tried another firmware on it yet?

    1. Probably doesn't matter, IF the firmware source package is as cool as it looks.
    2. Yes - see: http://www.suburbia.com.au/~dan/ It's the same process as enabling it on the Netgear DG834G. Put it into debug mode.
    3. Proabably... Nothing says it supports it, but as it _looks_ the same as the Netgear DG834G, with pretty much the exact version, it'll probably run dd-wrt.

    Anyone want to try to load another firmware on it?
  3. Slaytanic

    Slaytanic LI Guru Member

    Thank you very much for having pointed me to http://www.suburbia.com.au/~dan/! I think I won't try an unofficial firmware on this model until I find one that says to support it..
  4. greg9905

    greg9905 LI Guru Member

    I did a bit more digging, and the WAG200G is pretty much the same firmware as the DG834G. In fact, there seem to be a whole family of devices that are pretty much the same box. The platform is the TI AR7. There is an port to this platform of OpenWRT in progress: http://wiki.openwrt.org/CategoryAR7Device

    Here is the OpenWRT page for the DG834G, which is the most similar box so far: http://wiki.openwrt.org/OpenWrtDocs/Hardware/Netgear/DG834G?highlight=(CategoryAR7Device)

    I'll also wait until something is a bit more tested out before trying it. I'm a bit surprised that someone doesn't just build a firmware from the toolkit that Linksys provides. I was able to compile a new firmware, but I'm not quite sure where to go about starting to change things. I'd really like to install ssh on the router. The other thing I'd like to have is WDS support for my Airport Express hooked up to my stereo and that's extending my wireless network. I've got to admit it's very cool that Linksys provided the whole MonteVista toolkit to build the firmware. And, it appears to even cross-compile.

    Still, it's nice to find out that the WAG200G is a worthwhile little box, and not just cute and useless. :)
  5. woytekm

    woytekm LI Guru Member


    I've done firmware rebuild for wag200g-EU annex A. The rebuilded firmware has telnetd, sshd, a few other tools ( no wireless tools for now cause wireless extensions doesn't work correctly ), and 256K of writable flash partition wchich means you can make your own startup/firewall scripts. Currently i'm working to make it avaliable to the public - if it'll be ready for the release - i'll post the info here.
  6. masterb

    masterb LI Guru Member

    Hi woytekm, I'm working on wag354g, I hope you could share your knowledge. I'm stuck on enabling telnet, and I hope you could help me.
  7. woytekm

    woytekm LI Guru Member

    If 354g GPL image published by Linksys has the same structure as 200g image, you shoud check code/target/usr/etc/rcS - router startup script, for some information about telnetd. In 200g telnetd was removed ( and telnetd startup command disabled in the rcS ) from the productional release of the code - i've had to compile and install utelnetd myself ...

    Feel free to ask if you have some questions ...

  8. masterb

    masterb LI Guru Member

    Hi, thank you for your answer.
    The structure of 354g sources is really a chaos, and code is written by cybertan. Luckily telnetd was already included in the busybox package, and I have been able to enable it. Now I have moved further and compiled also dropbear for ssh client and server.
    I'm really attracted by the possibility of having a rw partition, can you explain me how to do it?

    Also, what compiler do u use? The crappy gcc 2.95 from TI?

    At the end, this the version of my adsl drivers, maybe yours are newer?
    # cat /proc/avalanche/avsar_ver 
    ATM Driver version:[]
    DSL HAL version: []
    DSP Datapump version: [] Annex A
    SAR HAL version: [01.07.2b]
    PDSP Firmware version:[0.54]
    Chipset ID: [7300/7300A]
  9. woytekm

    woytekm LI Guru Member

    unfortunately wag200 (firmware 1.00.07) dsl drivers look older than yours ...

    wag200g:~#cat /proc/avalanche/avsar_ver
    ATM Driver version:[]
    DSL HAL version: []
    DSP Datapump version: [] Annex A
    SAR HAL version: [01.07.2b]
    PDSP Firmware version:[0.53]

    and in regard to writable flash space:
    WAG200 has five partitions on flash, last partition ( /dev/mtdblock/5 )
    is destined for the language versions of the www interface. I've simply used mkfs.minix on this space ( busybox has mkfs.minix built in, you just have to turn it on in the setup script ). My software version doesn't have language option this way, but it has 256K of writable minix filesystem instead ...

    This operation is very dangerous for the router if the flash structure is different than WAG200G - if you overwrite bootloader partition - the router is bricked for good. This is how WAG200 flash structure looks like:

    wag200g:/proc# cat partitions
    major minor #blocks name

    31 0 2880 mtdblocka
    31 1 704 mtdblockb
    31 2 128 mtdblockc
    31 3 64 mtdblockd
    31 4 64 mtdblocke
    31 5 256 mtdblockf

    destination of the partitions :

    a - filesystem image
    b - linux kernel
    c - ADAM2 bootloader code
    d - nvram data
    e - ADAM2 environment variables
    f - space for language versions of the www interface ( this is the space that i've used for the filesystem ).

    partitions a+b are written during the software upgrade. writing something random to c or e will probably make the router completely unusable and unbootable, so be very careful while playing with the flash !

  10. masterb

    masterb LI Guru Member

    hi, thank you of all your info. I have backed up all my partition using netcat. I noticed that the /dev/mtdblock/4 partition is filled with "ff", and it's size is 128k. Was this the same for your wag language partition?

    I'll try to compile busybox with mkfs...thank you for your great knowledge. Also, I forwarded your post about wag200g unofficial firmware to an italian forum. I think there are some beta tester ready for you!
  11. Divakaran

    Divakaran Network Newbie Member

    Hi - Woytekm - Greetings. I am trying to enable wireless client mode in my WIFI WAG200G ADSL router. I need your help to get the right firmware. I hope you had one and please help. I am trying to enable SCP to copy files for custom build. Please help. Appreciate your help in advice for providing the url to donwload. My email is diva.varadam@gmail.com


Share This Page