09-02-2002
Couple of things to check:
1. Check if interface is configured - # ifconfig -a
2. Check if interface is seen by the kernel - dmesg and grep for the name of the interface, i.e. # dmesg | grep hme or # dmesg | grep eri
3. Try and ping your interface ip address from another device on the network
10 More Discussions You Might Find Interesting
1. Solaris
Hello,
I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems:
1. When I execute the command ping, I get weird results:
bash-3.00$ usr/sbin/ping localhost ... (4 Replies)
Discussion started by: Przemek
4 Replies
2. Shell Programming and Scripting
Hi can someone tell me what command i can use to find the NIC status im using the bash shell. I'v tried ifconfig -a but this comes back as command not found. (3 Replies)
Discussion started by: warlock129
3 Replies
3. Shell Programming and Scripting
Can anybody tell me the command to find out the current status of Network Interface Card? (2 Replies)
Discussion started by: warlock129
2 Replies
4. Solaris
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies
5. Red Hat
Dear All
I want tune my NIC's rps, rfs and xps value.
In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1).
Here is the question? Which device should I modify ?
eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0)
Any advice is welcome.... (0 Replies)
Discussion started by: nnnnnnine
0 Replies
6. AIX
Hi all,
I have gone through many posts related to this issue,but my issue wasn't resolved hence creating new thread.
I am unable to ping localhost.
ping localhost tries to ping localhost which is defined in DNS.
My /etc/hosts has entry for localhost as
127.0.0.1 loopback localhost.
... (8 Replies)
Discussion started by: chpsam
8 Replies
7. Solaris
Dear,
I hope you all will be ok.
I have an issue with Solaris box running on x86 Blade.
I am unable to ping a node neither traceroute. I am able to do traceroute from oce0:6 port which have IP and subnet of same type which oce0:1 has.
details are as follows:
Problem:
root@rinams02:/#... (3 Replies)
Discussion started by: khaniqshahid
3 Replies
8. Solaris
Hi guys,
Another problem here and I appreciate the help,
the interface in the solaris v440 is showing as "FAILED"
ce0: flags=19040803<UP,BROADCAST,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,FAILED> mtu 1500 index 2
inet 192.168.1.30 netmask ffffff00 broadcast 192.168.1.255
... (14 Replies)
Discussion started by: br1an
14 Replies
9. Shell Programming and Scripting
Actually I am using Red hat Linux 4.4 version.
I want to check the 16 client pc status of connection from server.Whether the connection is available or not.I tried to develop the shell script for this code.But It don't work properly.I am a self study learner.Please give me a shell script for this... (9 Replies)
Discussion started by: kannansoft1985
9 Replies
10. Linux
Hello Admins,
My ask is how can I add two different subnet IPs to same box with two different gateways?
The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware.
How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
DE(4) BSD Kernel Interfaces Manual DE(4)
NAME
de -- DECchip 21040, 21140, 21141, 21142, and 21143 PCI Ethernet interface driver
SYNOPSIS
de* at pci? dev ? function ?
Configuration of PHYs may also be necessary. See mii(4).
DESCRIPTION
The de driver supports Ethernet and Fast Ethernet interfaces based on the Digital Equipment Corporation DECchip 21040, 21140, 21141, 21142,
and 21143 model controllers for PCI bus.
21040 10BASE-T and AUI/BNC
21140 10BASE-T and 100BASE-TX
21141 10BASE-T and 100BASE-TX
21142 10BASE-T and 100BASE-TX
21143 10BASE-T and 100BASE-TX
Supported Network Interface Cards (NIC) include, but are not limited to:
Accton EN1207i
Cogent EM100
Asante AsanteFAST
DEC DE435
DEC DE450
DEC DE500
SMC 9332
Znyx NetBlaster ZX340 series (345, 348, 346)
Generally, if the NIC is for PCI bus, and the major controller chip has the DIGITAL logo on it, with one of the model numbers above, the de
driver should recognize and control it. Beware, however, that many NIC manufacturers change the Ethernet controller chip without changing
the product model number, and a physical inspection of the NIC, or a probe of the NIC with a PCI diagnostic tool is the only way to tell if a
real DEC TULIP controller is present.
Multi-port interfaces are typically configured as a PCI-PCI bridge with multiple de instances on the PCI bus on the other side of the bridge.
DEC sold its semiconductor division to Intel. In addition, there are many "knock-offs" of the DEC TULIP Ethernet controller chips; NICs
based on these chips are handled by the tlp(4) driver.
This de driver should not be confused with the NetBSD VAX de driver for the DEC DEUNA/DELUA Ethernet controller for UniBus.
SEE ALSO
ifmedia(4), intro(4), mii(4), pci(4), tlp(4), ifconfig(8)
http://www.adaptec.com/, http://www.asante.com/, http://www.smc.com/, http://www.znyx.com/
HISTORY
The de driver first appeared in NetBSD 1.1
AUTHORS
Matt Thomas <matt@3am-software.com>.
BSD
February 11, 2000 BSD