Very Computer

  I have a Linux box (kernel 1.0.9) hooked to the net here at work. All works fine
from the Linux end (ftp out, telnet, ping, etc...), but when the machine first boots
up, I am not able to telnet,ping,ftp, etc... INTO linux from elsewhere until I log
in from the console and attempt to make a net connection OUT FROM the linux
machine.

  For example, on the Sun right next to the Linux machine, I type "telnet ptw119".
Telnet responds with "Trying nnn.nnn.nnn.nnn...", and it sits and tries but does
not work. I log into Linux, type "ping [hostname]" and as soon as I hit return,
the telnet session succeeds. I can repeat this phenomenon.

  To get things to work, I put a "ping -c 2 hostname" in the /etc/rc.d/rc.M file. This
makes it work, but it doesn't fix the problem.

  I installed from scratch with Slackware 1.2.0.

Jim Trocki

:   I have a Linux box (kernel 1.0.9) hooked to the net here at work. All works fine
: from the Linux end (ftp out, telnet, ping, etc...), but when the machine first boots
: up, I am not able to telnet,ping,ftp, etc... INTO linux from elsewhere until I log
: in from the console and attempt to make a net connection OUT FROM the linux
: machine.

PLEASE.... this seems to be the standard problem..... does ANYONE have an
answer? I'm trying to get Linux accepted around here, but with quirky things
like this, it will never be taken seriously...

Tim

--
                              Tim Sailer

       "It is a damned poor mind indeed that can't think of at
                least two ways of spelling any word."

    Look, you can't expect to post a 5 line bug report with NO real
    information other then "gee, this doesn't appear to work" and expect
    those of us who are volunteering our time to spend N hours tracking
    it down when we cannot necessarily reproduce ourselves.  In fact,
    that's the major problem!  Much of the time, those programmers doing
    the bug fixing cannot easily reproduce the bugs.

    Sure you can post a 5 line bug report.. in fact, if that is all you
    have time for please do!  But don't complain.... if you really want to
    help you have to do more work.  

    * Determine whether the problem still exists in the latest development
      kernel, if possible. (on nic.funet.fi in pub/OS/Linux/PEOPLE/Linus/v1.1).

    * NARROW the problem down... experiment with different configurations
      and try to narrow the problem down to something we can get a grip
      on.

    * When you do make a bug report, please give more information... the
      machine configuration, the ifconfig, routes, arp table (for ethernet),
      tests you have done, assumptions and conclusions, etc.

    * Be prepared for the bug to not get fixed.  We may not be able to track
      it down immediately, or even for a very long time.

                                                -Matt

--

    1005 Apollo Way             ham: KC6LVW (no mail drop)
    Incline Village, NV. 89451  Obvious Implementations Corporation
    USA                         Sandel-Avery Engineering
    [always include a portion of the original email in any response!]