Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Vaako]

Hi,

I have managed to make a connection via Serial-Console to the Technicolor TG789Bvn / TG799vn wich is the O-Box 3 here in Belgium.
Although it is also possible to access it via Telnet if I connect a TTL to RS232 to ETHERNET converter that than is accessable via a IP address.

The command prompt that shows up is:

TG233 login:

After put the name Administrator I see this output:

Code: [Select]

TG233 login: starting pid 1049, tty '/dev/ttyS0': '/bin/login'^C
starting pid 1050, tty '/dev/ttyS0': '/bin/login'
TG233 login:
TG233 login: Administrator


BusyBox v1.10.3 (2013-08-16 16:29:13 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

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



                             ______  Technicolor TG799vn v2

                         ___/_____/\

                        /         /\\  10.5.D.W

                  _____/__       /  \\

                _/       /\_____/___ \  Copyright (c) 1999-2013, Technicolor

               //       /  \       /\ \

       _______//_______/    \     / _\/______

      /      / \       \    /    / /        /\

   __/      /   \       \  /    / /        / _\__

  / /      /     \_______\/    / /        / /   /\

 /_/______/___________________/ /________/ /___/  \

 \ \      \    ___________    \ \        \ \   \  /

  \_\      \  /          /\    \ \        \ \___\/

     \      \/          /  \    \ \        \  /

      \_____/          /    \    \ \________\/

           /__________/      \    \  /

           \   _____  \      /_____\/

            \ /    /\  \    /___\/

             /____/  \  \  /

             \    \  /___\/

              \____\/



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

{Administrator}=>
{Administrator}=>


What commands are used to show the dsl information.

Any help is welcome! 

[Bald_Eagle1]

Maybe this document will help (different model, but maybe same commands):-

http://wiki.aa.org.uk/images/3/33/TG582n_CLI_Guide_v1.0_public.pdf


Just a few examples:-


xdsl info                     Displays status information about modem
xdsl config                   Modify/Display dsl configuration see page 856
xdsl debug bitloadinginfo     Displays # bits per tone see page 857
xdsl debug deltconfig         Dual Ended Line Testing interface see page 858
xdsl debug deltinfo           Dual Ended Line Test result display see page 859
xdsl debug modemoptioninfo    The modem options bitmap display see page 860
xdsl debug multimode          Config custom multimode see page 861
xdsl debug traceconfig        Config the adsl tracelevel see page 862
xdsl version                  Display xdsl version information. see page 863de]

[Vaako]

Thank you so much for your help!

The strange thing is that if I put any command like "xdsl info" results are:

Code: [Select]

{Administrator}=>xdsl info
-sh: xdsl: not found
{Administrator}=>

I don't now what I'm doing wrong.
My Linux knowledge is minimal jus tto let you know.

If I put the command "help" this is the output:

Code: [Select]

{Administrator}=>help

Built-in commands:
-------------------
        . : [ [[ alias bg break cd chdir continue echo eval exec exit
        export false fg hash help jobs kill let local pwd read readonly
        return set shift source test times trap true type ulimit umask
        unalias unset wait

{Administrator}=>

The command "ls" was possible after I did this:
cd ..
ls

Code: [Select]

{Administrator}=>ls
bin          init         mnt          root         tmp
dev          lib          opt          sbin         usr
etc          linuxrc      proc         scripts      var
home         log.txt      release.txt  sys          xdsl
{Administrator}=>

Any suggestions what I can try next?

[burakkucat]

Please show us the output produced by the following command lines --

echo $PATH
ls -l /bin
ls -l /sbin
ls -l xdsl

You might like to see if ./xdsl info produces any output . . . 

[Vaako]

Please show us the output produced by the following command lines --

echo $PATH
ls -l /bin
ls -l /sbin
ls -l xdsl

You might like to see if ./xdsl info produces any output . . . 

Here is the output:

echo $PATH

Code: [Select]

{Administrator}=>echo $PATH
/bin:/sbin:/usr/bin:/usr/sbin:/scripts:/usr/bin/X11:/usr/local/bin
{Administrator}=>


ls -l /bin

Code: [Select]

{Administrator}=>ls -l /bin
lrwxrwxrwx    1 root     root            7 Aug 16  2013 ash -> busybox
-rwsr-xr-x    1 root     root       351172 Aug 16  2013 busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 cat -> busybox
-rwxrwxrwx    1 root     root        41356 Aug 16  2013 chkimage
lrwxrwxrwx    1 root     root            7 Aug 16  2013 chmod -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 chown -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 cp -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 date -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 dd -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 df -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 dmesg -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 echo -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 egrep -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 false -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 fgrep -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 getopt -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 grep -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 gunzip -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 gzip -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 hostname -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 ip -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 kill -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 ln -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 login -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 ls -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 mkdir -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 mknod -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 mktemp -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 mount -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 mt -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 mv -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 netstat -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 pidof -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 ping -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 ping6 -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 ps -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 pwd -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 rm -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 rmdir -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 run-parts -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 sed -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 sh -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 sleep -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 stty -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 su -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 sync -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 touch -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 true -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 umount -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 uname -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 usleep -> busybox
lrwxrwxrwx    1 root     root            7 Aug 16  2013 vi -> busybox
-rwxr-xr-x    1 root     root       171416 Aug 16  2013 wget
-rwxr-xr-x    1 root     root        64420 Aug 16  2013 wput
lrwxrwxrwx    1 root     root            7 Aug 16  2013 zcat -> busybox
{Administrator}=>


ls -l /sbin

Code: [Select]

{Administrator}=>ls -l /sbin
-rwxr-xr-x    1 root     root         3280 Aug 16  2013 add_syslog
lrwxrwxrwx    1 root     root           14 Aug 16  2013 arp -> ../bin/busybox
-rwxr-xr-x    1 root     root       132204 Aug 16  2013 call_qcsapi
-rwxr-xr-x    1 root     root       815844 Aug 16  2013 cwmpd
lrwxrwxrwx    1 root     root           14 Aug 16  2013 getty -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 halt -> ../bin/busybox
-rwxr-xr-x    1 root     root          502 Aug 16  2013 hotplug
-rwxr-xr-x    1 root     root         6788 Aug 16  2013 htpasswd
lrwxrwxrwx    1 root     root           14 Aug 16  2013 hwclock -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 ifconfig -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 ifdown -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 ifup -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 init -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 insmod -> ../bin/busybox
-rwxr-xr-x    1 root     root         6008 Aug 16  2013 ipv6-mgmt
-rwxr-xr-x    1 root     root        70708 Aug 16  2013 iwconfig
lrwxrwxrwx    1 root     root            8 Aug 16  2013 iwevent -> iwconfig
lrwxrwxrwx    1 root     root            8 Aug 16  2013 iwgetid -> iwconfig
lrwxrwxrwx    1 root     root            8 Aug 16  2013 iwlist -> iwconfig
lrwxrwxrwx    1 root     root            8 Aug 16  2013 iwpriv -> iwconfig
lrwxrwxrwx    1 root     root            8 Aug 16  2013 iwspy -> iwconfig
lrwxrwxrwx    1 root     root           14 Aug 16  2013 klogd -> ../bin/busybox
-rwxr-xr-x    1 root     root         6900 Aug 16  2013 l2tftp
lrwxrwxrwx    1 root     root           14 Aug 16  2013 lsmod -> ../bin/busybox
-rwxr-xr-x    1 root     root        46532 Aug 16  2013 mini_httpd
lrwxrwxrwx    1 root     root           14 Aug 16  2013 modprobe -> ../bin/busybox
-rwxr-xr-x    1 root     root         7792 Aug 16  2013 monitor_reset_device
-rwxr-xr-x    1 root     root         7916 Aug 16  2013 monitor_wifi
lrwxrwxrwx    1 root     root           14 Aug 16  2013 pivot_root -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 poweroff -> ../bin/busybox
-rwxr-xr-x    1 root     root         6552 Aug 16  2013 qpm
lrwxrwxrwx    1 root     root           14 Aug 16  2013 reboot -> ../bin/busybox
-rwxr-xr-x    1 root     root         4972 Aug 16  2013 restore_bootcfg_env
lrwxrwxrwx    1 root     root           14 Aug 16  2013 rmmod -> ../bin/busybox
-rwxr-xr-x    1 root     root         5092 Aug 16  2013 rmt_qcsapi
-rwxr-xr-x    1 root     root         6464 Aug 16  2013 rmt_qcsapi_eth
lrwxrwxrwx    1 root     root           14 Aug 16  2013 route -> ../bin/busybox
-rwxr-xr-x    1 root     root         6468 Aug 16  2013 show_access_points
-rwxr-xr-x    1 root     root         3768 Aug 16  2013 show_rfcal_version
-rwxr-xr-x    1 root     root         4332 Aug 16  2013 show_traffic_rates
lrwxrwxrwx    1 root     root           14 Aug 16  2013 start-stop-daemon -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 sulogin -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 syslogd -> ../bin/busybox
-rwxr-xr-x    1 root     root       168800 Aug 16  2013 tc
-rwxr-xr-x    1 root     root         8408 Aug 16  2013 tch_dfs_reentry
-rwxr-xr-x    1 root     root        10344 Aug 16  2013 tch_events
-rwxr-xr-x    1 root     root         5652 Aug 16  2013 tch_led
-rwxr-xr-x    1 root     root        16428 Aug 16  2013 tch_monitor
-rwxr-xr-x    1 root     root        11048 Aug 16  2013 tch_traffic_monitor
-rwxr-xr-x    1 root     root        20280 Aug 16  2013 tch_vb_discover
drwxrwxr-x    4 root     root            0 Aug 16  2013 transformer
-r--r--r--    1 root     root         3091 Aug 16  2013 transformer.lua
-rwxr-xr-x    1 root     root        28716 Aug 16  2013 ucicli
lrwxrwxrwx    1 root     root           14 Aug 16  2013 udhcpc -> ../bin/busybox
lrwxrwxrwx    1 root     root           14 Aug 16  2013 vconfig -> ../bin/busybox
-rwxr-xr-x    1 root     root         4176 Aug 16  2013 writerfmem
{Administrator}=>


ls -l xdsl

Code: [Select]

{Administrator}=>ls -l xdsl
-rw-r--r--    1 root     root            0 Jan  2 03:44 xdsl
{Administrator}=>


./xdsl info

Code: [Select]

{Administrator}=>./xdsl info
-sh: ./xdsl: Permission denied
{Administrator}=>

Permission denied even after I use superuser:

Code: [Select]

{Administrator}=>su


BusyBox v1.10.3 (2013-08-16 16:29:13 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

{Administrator}=>./xdsl
sh: ./xdsl: Permission denied
{Administrator}=>


[roseway]

One possibility is that the file xdsl isn't executable. This may be grasping at straws but you could try

Code: [Select]

sh xdsl

or

sh ./xdsl

[burakkucat]

One possibility is that the file xdsl isn't executable.

The problem is more fundamental than that.

Code: [Select]

{Administrator}=>ls -l xdsl
-rw-r--r--    1 root     root            0 Jan  2 03:44 xdsl
{Administrator}=>

We can see that the file xdsl has a size of zero! 

[Vaako]

One possibility is that the file xdsl isn't executable. This may be grasping at straws but you could try

Code: [Select]

sh xdsl

or

sh ./xdsl

Hmmm,

I tryed both and it gives no output:

Code: [Select]

{Administrator}=>sh xdsl
{Administrator}=>

Code: [Select]

{Administrator}=>sh ./xdsl
{Administrator}=>


[roseway]

We can see that the file xdsl has a size of zero!

I missed that. It rather suggests that the CLI has been disabled in the firmware (unless there's another xdsl executable somewhere else on the system).

[Vaako]

I also was looking to enable a telnet server on this modem and find out that telnetd is already installed but not enabled.

Telnetd schould be in /usr/sbin/telnetd

Code: [Select]

{Administrator}=>cd usr
{Administrator}=>cd sbin
{Administrator}=>ls
brctl           flash_info      jffs2dump       wdskey
chpasswd        hostapd         mkfs.jffs2      wpa_cli
flash_erase     hostapd_cli     ntpclient       wpa_supplicant
flash_eraseall  inetd           telnetd
{Administrator}=>

/etc/inetd.conf
The inetd.conf has this line:

Code: [Select]

telnet stream  tcp     nowait  root    /usr/sbin/telnetd   /usr/sbin/telnetd
Does someone knows what parts are needed to run the telnetd server?

[burakkucat]

I also was looking to enable a telnet server on this modem and find out that telnetd is already installed but not enabled.

Huh?   

Of course it is enabled. You have successfully connected to the device using a telnet client executing on the computer. (The computer's telnet client requires that the modem/router's telnet server should be active.) 

[Vaako]

I also was looking to enable a telnet server on this modem and find out that telnetd is already installed but not enabled.

Huh?   

Of course it is enabled. You have successfully connected to the device using a telnet client executing on the computer. (The computer's telnet client requires that the modem/router's telnet server should be active.)

I do not connect to Telnet via IP address.
I connect via the modem onboard connector with an TTL-to-RS232 converter.
115200 baud / Data bits 8 / Parity 0 / Stop bits 1 / Flow Control None

I also found out that rc.local / rc.conf file does not exist on this system, so it must be a SYSTEMD !?

[burakkucat]

I do not connect to Telnet via IP address.
I connect via the modem onboard connector with an TTL-to-RS232 converter.
115200 baud / Data bits 8 / Parity 0 / Stop bits 1 / Flow Control None

Ah, I see. You are connecting via modem's console serial port UART. So what is the result of trying --

/usr/sbin/inetd &

I also found out that rc.local / rc.conf file does not exist on this system, so it must be a SYSTEMD !?

I don't think so. Earlier you showed us the listing of the contents of the /sbin/ directory and there was present, in the output --

Code: [Select]

lrwxrwxrwx    1 root     root           14 Aug 16  2013 init -> ../bin/busybox

It is not mandatory for an init based system to have an rc.local, an rc.sysinit or an rc.conf file(s).

[Vaako]

Hi burakkucat,

Yeah, thats right I connect via the serial pins directly on the modem's PCB but it is a TTL signal and schould be converted to RS232 level.

This is the result of  /usr/sbin/inetd &

Code: [Select]

{Administrator}=>/usr/sbin/inetd &
[1] + Done                       /usr/sbin/inetd
{Administrator}=>

Is it possible to Enable telnet via inetd, these are used for startup services or not?

[burakkucat]

I was wondering if that was enough to start inetd and, thus, telnetd (the telnet server) on the modem.

Having executed /usr/sbin/inetd &, are you now able to access the modem via telnet?

If that is unsuccessful, power cycle the modem (to reset everything) and then execute /usr/sbin/telnetd &. Now try to access the modem via telnet, one again.

I'm not sure exactly how the various services are started on that modem . . . I do not have any experience of using one. I'm just guessing, based on the information that you have been able to show.