*BSD News Article 35042


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!werple.apana.org.au!troll.apana.org.au!rivendell.apana.org.au!phil
From: phil@rivendell.apana.org.au (Phil Homewood)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Need help with TELNET
Date: 28 Aug 1994 01:31:04 GMT
Organization: Rivendell - APANA Brisbane.
Lines: 50
Message-ID: <33opco$9jq@rivendell.apana.org.au>
References: <33m1bo$7fj@adam.cc.sunysb.edu>
NNTP-Posting-Host: rivendell.apana.org.au
X-Newsreader: TIN [version 1.2 PL2]

Romolo Albuquerque (ralbuque@libws4.ic.sunysb.edu) wrote:
: Hi. I'm trying to network 2 machines with FreeBSD-1.1-B. I'm having problems
: trying to use servies like 'telnet, ftp, etc..'. I can ping the host machine
: but can't telnet there. My IP addresses are as follows:

: 1) FreeBSD machine  ( 130.245.150.1 netmask 255.255.255.0)
: 2) Host machine     ( 130.245.150.0 netmask 255.255.255.0)

This might be a problem - x.x.x.0 is usually a network address,
not a host address.  Methinks your routing is confused somewhere
because of this one.

: The problem occurs after I run 'ifconfig' to configure the FreeBSD machine.
: It, somehow, assigns 2 addresses to the ethernet card 'ed0'. I don't know 
: why since I only run the 'ifconfig' command one time.. Here is the output of 
: " netstat -i"

: >ed0   1500  <Link>0.40.33.21.32.70           286     0      279     0     0

Correct: this is the hardware address....

: >ed0   1500  130.245.150 130.245.150.1        286     0      279     0     0

Correct: 130.245.150[.0] is the _network_ address of this interface.
And 130.245.150.1 is the IP of the interface.
No problems here....

: I don't know where the first address comes from since I configured the card
: as follows :
: 	" ifconfig ed0 130.245.150.1 netmask 255.255.255.0 "

That looks correct..

: After this I can ping the host machine but can't telnet or ftp to it.
: When I try to telnet to the host machine, I get the following error message:

You can ping it because a ping to x.x.x.0 means 'ping the network and
get any response from any machine on the net.'.  (dubious correctness
btw).
You can't telnet to it because it makes no sense to telnet to a
network address.

Move the .0 IP to something else and see what happens.

Phil.
--
Phil Homewood                           phil@rivendell.apana.org.au
APANA Brisbane Regional Co-Ordinator    brisbane@apana.org.au
         "I got nothing to say I ain't said before
          I bled all I can, I won't bleed  no more"