Remove banner

Discussion in 'Cisco/Linksys Network Storage Devices' started by idunham, Mar 3, 2009.

  1. idunham

    idunham Addicted to LI Member

    Hey all,

    Have a question that is probably reallllly simple.

    Whenever i SSH into my nas using the jac0 firmware, i get the greeting "BusyBox v1.00-rc2 (2009.02.01-05:21+0000) Built-in shell (ash)
    Enter 'help' for a list of built-in commands."

    But when i try to do an rdiff-backup with plink it says "Integer overflow while attempting to establis the remote connection" and further down it says "Please make sure that nothing is printed by your login shell with this command executed."

    How can i get rid of the welcome?

  2. JonasSS

    JonasSS Addicted to LI Member

    Have you checked for a /etc/motd file?
  3. jac_goudsmit

    jac_goudsmit Super Moderator Staff Member Member

    You mean the Jac2b firmware (judging from the compilation date) :wink:

    The actual error message is probably: Integer overflow while attempting to establish the remote connection by executing %s Please make sure that nothing is printed (e.g., by your login shell) when this command executes. Try running this command: %s which should only print out the text: rdiff-backup <version>

    Did you install rdiff backup on the NAS200 according to these instructions?

    What command are you using to do your backup? Do you open the SSH connection manually with plink? If so, are you using the right options? I don't think it should even need a shell - the rdiff-backup on your computer probably simply instructs the SSH server to run rdiff-backup on the NAS200 and pipe stdin and stdout to the network. I think that's how WinSCP works although I'm not sure of the details.

    Either way, there is no easy way to remove the header without recompiling busybox, rebuilding the software and reinstalling it.

    And no, there is no /etc/motd on the NAS200. It's an embedded device and it's not even intended to have a shell login so there's no reason for an MOTD file. JonasSS, you were just kidding, right?

  4. idunham

    idunham Addicted to LI Member

    Yes, I did install rdiff-backup according to those instructions. My biggest problem that i encountered is getting the keys to work for passwordless login. Whether i use dropbearkey to get the keys, or i convert PuTTy keys to dropbear. Didn't matter, "server refused the key" is all i would get.

    Yes, i open the SSH connection with Plink. I am trying to force this command to run on a Windows 2000 server box. So, plink is the process that seemed to make sense to allow ssh to work.

    The command i use for plink is

    rdiff-backup -v5 --no-hard-links --print-statistics --remote-schema 'plink -pw password %s' H:\User_files root@

    If i do try to use 'plink -pw password %s rdiff-backup --server' It comes up saying

    Unable to open connection:
    Host does not existFatal Error: Truncated header string (problem probably origin
    ated remotely)

    Couldn't start up the remote connection by executing

    plink -pw password Fatal Error: Bad commandline options: option -p not rec

    Remember that, under the default settings, rdiff-backup must be
    installed in the PATH on the remote system. See the man page for more
    information on this. This message may also be displayed if the remote
    version of rdiff-backup is quite different from the local version (1.2.6).

    Now, if i would try to run the command without %s i get this error.

    Fatal Error: Bad commandline options: option -p not recognized
    See the rdiff-backup manual page for more information.

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice