NIC The Status Down but I can ping the localhost??!! Post: 27434

10 More Discussions You Might Find Interesting

1. Solaris

PING - Unknown host 127.0.0.1, Unknown host localhost - Solaris 10

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 ...

2. Shell Programming and Scripting

NIC status bash shell

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. Shell Programming and Scripting

Status of NIC

Can anybody tell me the command to find out the current status of Network Interface Card?

4. Solaris

x86 Solaris 10 nic driver added but not attached. NIC is not detected.

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...

5. Red Hat

I want to tune NIC's rps, rfs and xps value. which NIC device should I modify.

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....

6. AIX

Unable to ping localhost

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. ...

7. Solaris

Network issue on multinic. Unable to ping a host from One NIC but other works

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:/#...

8. Solaris

Nic Failed Status

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 ...

9. Shell Programming and Scripting

Network script for ping status

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...

10. Linux

Add two different subnet public IPs to single NIC or two different NIC on same box

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...

LEARN ABOUT BSD

lo

LO(4)							     Kernel Interfaces Manual							     LO(4)

NAME

       lo - software loopback network interface

SYNOPSIS

       /sys/conf/SYSTEM:
	    NLOOP     1    # loop-back pseudo-device

DESCRIPTION

       The  loop  interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communica-
       tion.  As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which	it
       is to be used.  These addresses may be set or changed with the SIOCSIFADDR ioctl.  The loopback interface should be the last interface con-
       figured, as protocols may use the order of configuration as an indication of priority.  The  loopback  should  never  be  configured  first
       unless no hardware interfaces exist.

DIAGNOSTICS

       lo%d:  can't  handle  af%d.   The  interface  was handed a message with addresses formatted in an unsuitable address family; the packet was
       dropped.

SEE ALSO

       intro(4N), inet(4F), ns(4F)

BUGS

       Previous versions of the system enabled the loopback interface automatically, using a nonstandard Internet address (127.1).   Use  of  that
       address is now discouraged; a reserved host address for the local network should be used instead.

3rd Berkeley Distribution					  August 1, 1987							     LO(4)