linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David A. Gatwood" <dgatwood@gatwood.net>
To: murali nagarajan <muralin@gdatech.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problem with ping/telnet
Date: Tue, 5 Feb 2002 14:53:07 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.3.96.1020205145050.16943C-100000@gatwood.net> (raw)
In-Reply-To: <022601c1ae91$34c80820$0900a8c0@Domain.invalid>


On Tue, 5 Feb 2002, murali nagarajan wrote:

> - PING command does not work
>   The erro message I get is   "ping: unknown protocol icmp"

Don't know.  Might be a kernel compile issue or something, or it might be
related to the second issue.  Not sure.


> - Telnet program does not work which tells me that the service is unknown.
>    The error message I get is "telnet: tcp/telnet: unknown service"

This one's easy.  Telnet explicitly asks the system for the default port
number for telnet service.  If you don't have a valid /etc/services file
(with telnet listed), it won't be able to do so, and it will fail.  If you
specify a port number by hand (e.g. telnet foo.com 23), it should work.
Or you can just put in an /etc/services file.


Later,
David

---------------------------------------------------------------------
                    Check out my weekly web comic:
                     http://www.techmagazine.org


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-02-05 22:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 22:05 Problem with ping/telnet murali nagarajan
2002-02-05 22:53 ` David A. Gatwood [this message]
2002-02-06  0:08   ` murali nagarajan
2002-02-06  0:46     ` David A. Gatwood
2002-02-06  1:03       ` Jeffrey D. Kowing
2002-02-06 19:59         ` murali nagarajan
  -- strict thread matches above, loose matches on Subject: below --
2002-02-07  4:50 Bill Fink

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.3.96.1020205145050.16943C-100000@gatwood.net \
    --to=dgatwood@gatwood.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=muralin@gdatech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).