Date: Tue, 11 Apr 95 10:44:01 EDT From: shu@apollo.hp.com To: questions@FreeBSD.org Cc: shu@apollo.hp.com Subject: cannot connect to LAN Message-ID: <199504111444.HAA21047@freefall.cdrom.com>
next in thread | raw e-mail | index | archive | help
Hi,
I bought the most recent freebsd on CDROM from Walnut Creek
a couple of weeks ago. It's my first time using freebsd.
Software, including X11R6, got installed and ran fine on
my 486/50 machine. But somehow I couldn't get the network
going. I am using 3COM509 NIC. The command ifconfig showed
the interface card was up and running:
% ifconfig ep0
ep0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX> mtu 1500
inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255
I could ping to myself, but couldn't ping to any other machines
in the same LAN. It always got the error
send to: host is down
Other machines couldn't ping to freebsd machine either.
I wonder if I have missed anything in the network setup?
On HP-UX, we do need to run another command "lanconfig"
after the command ifconfig. I couldn't find a similar
command for that function in freebsd. Is that required
in freebsd? Thanks for your help!
-Dean Shu
lanconfig(1M) lanconfig(1M)
NAME
lanconfig - configure network interface parameters
SYNOPSIS
lanconfig interface [ether |-ether] [ieee |-ieee]
DESCRIPTION
lanconfig is used to configure the network interface protocol. It
must be used at boot time to configure each interface present on a
machine, and can also be used at a later time to redefine interface
protocol configuration. interface is a string of the form name unit,
such as lan0.
lanconfig enables or disables protocols as defined by the following
parameters:
ieee Enable IEEE 802.3 protocol over the network interface.
-ieee Disable IEEE 802.3 protocol over the network interface.
ether Enable Ethernet protocol over the network interface.
-ether Disable Ethernet protocol over the network interface.
(none) If no optional parameters are supplied, lanconfig
displays the current configuration for interface.
Only users with appropriate privileges can modify the configuration of
a network interface.
If no protocol encapsulation method is enabled, the lan driver cannot
send packets over that interface and any subsequent send() fails,
returning the error [ENETUNREACH].
DIAGNOSTICS
Messages indicating the specified interface does not exist, the
requested parameter value is unknown, or the user is not privileged
and tried to alter an interface's configuration.
SEE ALSO
netstat(1), ifconfig(1m), hosts(4), routing(7).
Hewlett-Packard Company - 1 - HP-UX Release 9.0: August 1992
-------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504111444.HAA21047>