Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Jan 1998 06:50:03 -0600
From:      Frank Griffith <frankg@idfw.com>
To:        "'freebsd-questions@freebsd.org'" <freebsd-questions@FreeBSD.ORG>
Subject:   ed1: device timeout, Can't Ping my Win95 workstations
Message-ID:  <01BD24A6.7FB9DC60@dal01-08.ppp.iadfw.net>

next in thread | raw e-mail | index | archive | help
I am running FreeBSD 2.2.5 on the following:

	486-66 system, with 32 Meg RAM
	325 Meg Western Digital Caviar HD
	generic hayes compatible modem on COM2, IRQ3
	NE2000 compatible ethernet NIC on IRQ10, I/O300
	serial mouse on COM1, IRQ4
	Stealth VLB 2 Meg video card (its a couple of years old, not a new one)

In the same room, I have a Novell NetWare 4.1 server with two Win95
workstations connected to it with BNC cable. The terminators for this cable
are in place and working. These systems are running flawlessly at the
moment and communicating (files and printers) with each other well.
I want to connect the FreeBSD machine to this network and see it with
the Windows 95 machines. I don't care it the FreeBSD unit and the Novell
unit see each other at this time, that will come later.

So, I unhook the BNC cable from one of the Windows 95 unit, being
carefull so I don't disconnect the terminator and ruin the cable connection.
I then hook this cable up to the FreeBSD machine. Remember the
terminator is still in place and the cable is still active. The remaining Win95
workstation and the NW4.1 server are still talking to each other at this point.
In other words the terminators and cables are working. So I think we can
rule them out.

I have gone through the tutorial sections 3-5 several times and corrected
any typos I may have made along the way, but still can't see the FreeBSD
unit with the Win95 workstation. The FreeBSD unit can ping itself by using
its name and localhost. The Win95 can ping itself. But not each other.

Whenever I halt the system I see the message ed1: device timeout.
The last line of my dmesg also says ed1: device timeout.

When I type "iconfig -a"  I get the following output

ed1:   flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            inet 192.168.0.1 netmask 0xffffff00 bradcast 192.168.0.255
            ether 00:40:33:25:da:11
lp0:    flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
tun0:  flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0:    flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
lo0:    flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
             inet 127.0.0.1 netmask 0xff000000

When I boot the FreeBSD unit, I see the followinf message after the hardware
setups:

	swapon . . . 
		.
		.
	Doing initial network setup: hostname
	ifconfig: interface ppp0 does not exist
	lo0:    flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
                         inet 127.0.0.1 netmask 0xff000000
	ed1:   flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            inet 192.168.0.1 netmask 0xffffff00 bradcast 192.168.0.255
            ether 00:40:33:25:da:11

	Writing to routing socket: Network is unreachable
	add net default: gateway 0.0.0.0: Network is unreachable
	Additional routing options: IP gateway=YESed1: device timeout
	.
	recording kernel -c changes
	additional deamons: syslogdJan 19 06:39:36 curly /kernel: ed1: device timeout
	.

Can anyone tell what to try next?




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01BD24A6.7FB9DC60>