Date: Fri, 22 Nov 1996 17:09:53 +0100 (MET) From: Greg Lehey <grog@lemis.de> To: GWMANN@ccmail.monsanto.com Cc: questions@FreeBSD.org (FreeBSD Questions) Subject: Re: TCP/IP startup difficulties Message-ID: <199611221609.RAA01078@freebie.lemis.de> In-Reply-To: <0030400001896995000002*@MHS> from "GWMANN@ccmail.monsanto.com" at "Nov 21, 96 12:25:23 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
GWMANN@ccmail.monsanto.com writes:
>
> Hello all.
>
> We are converting from IPX and NETBluey to TCP/IP. So far we have an
> NT server running TCP/IP with one connected NT client (works fine).
> However, we have no router, nor a DNS (we are not yet connected to the
> net).
>
> My FreeBSD box is P/75 32MB RAM, with 3C509 NIC at 340/IRQ 10. On
> boot FreeBSD finds the NIC no problem, and does not pause on the add
> gateway or sendmail startups, "ifconfig -a" shows the following:
>
> lp0: flags=8810(POINTTOPOINT,SIMPLEX,MULTICAST> mtu 1500
> ep0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX> mtu 1500
> inet 164.144.6.80 netmask 0xffffff00 broadcast 164.144.6.255
> ether 00:a0:24:25:e4:59
> lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 552
> sl0: flags=c010<POINTTOPOINT,LINK2,MULTICAST> mtu 552
> tun0: flags=8010<POINTOTPOINT,MULTICAST> mtu 1500
>
> while "netstat -n" gives nothing.
No output at all? That's unusual. You should get something like:
=== grog@freebie (/dev/ttyp6) /usr/home/grog 10 -> netstat -n
Active Internet connections
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp 0 0 192.109.197.137.1060 192.109.197.134.6000 ESTABLISHED
tcp 0 272 192.109.197.137.1051 192.109.197.134.6000 ESTABLISHED
tcp 0 0 192.109.197.137.1015 192.109.197.134.1010 ESTABLISHED
tcp 0 0 192.109.197.137.514 192.109.197.134.1011 CLOSE_WAIT
tcp 0 0 192.109.197.137.1049 192.109.197.134.6000 ESTABLISHED
tcp 0 0 192.109.197.137.1016 192.109.197.134.1012 ESTABLISHED
tcp 0 0 192.109.197.137.514 192.109.197.134.1013 CLOSE_WAIT
tcp 0 0 192.109.197.137.1036 192.109.197.134.6000 ESTABLISHED
(etc)
What does netstat -rn say?
> Another netmask I have tried is 255.255.254.0, since we'll be using
> two class-C nets. I can send or post sysconfig, etc. on request.
Don't worry about net masks yet. You haven't mentioned much in the
way of problems, but net masks are a long way from the basic problem
of getting the thing to talk. But what you seem to have are two
slices of a class B net. Is the address correct?
> We have a Compass Network Analyzer which I have not been able to make
> see my FreeBSD machine. When attempting ping, the Compass unit says
> "Specified IP host does not response to ARP requests." I'm bummed.
That could have many reasons. I'd try it the other way round first:
get the analyzer to look for packets from Ethernet address
00:a0:24:25:e4:59, then start a ping to, say, address 164.144.6.255.
> Someone said something about the NT server using DEC-encompassed
> (Frame_II) IP packets as opposed to Frame_802.2. Is this a potential
> problem?
I suppose so, if it's true, but I haven't heard of people having
trouble connecting to NT before (well, not that kind of problem).
> Since we have no DNS or router set up (we're still using IPX/NETBEUI
> for everthing else) is this the problem?
No, not if you use IP addresses and you're on the same wire.
> Don't remember this kind of problems setting up FreeBSD before on a
> Novell net.
I'd guess that you have the board set up wrong. Wrong port, perhaps?
Check the man page for ep:
The default port to use is the BNC. To choose an alternate port, use the
following flag combinations with ifconfig(8) or in your /etc/hostname.ep?
file.
-link0 Use the BNC port (default).
link0 -link1 Use the AUI port.
link0 link1 Use the UTP port.
Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611221609.RAA01078>