Loopback Interface...Vanished??? Post: 28630

9 More Discussions You Might Find Interesting

1. Solaris

Adding Loopback Interface

Hello, I have a SunOS (5.5.1) system that I need to migrate to a new IP address. I would like to have any requests destined for the old IP to be forwarded to this server. One suggestion I had was to add a route on my router that would point the old IP to the new IP. How do I add another...

2. Red Hat

Configure floating IP on loopback interface

Hi All, I need to configure a floating IP on loopback interface of two servers (RHEL 5.4). After configuring, I'm not able to ping to that IP from a different server. I fail to understand what is missing here. I have done similar configuration in another environment & it works fine. Plz help....

3. Solaris

Command line Interface or GUI Interface not shown on solaris

Dear all, I am a newbie in solaris and I need your advice. I have a Solaris version 5.9 installed on Sunfire V240. I am able to ssh the machine from putty remotely. My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI...

4. SCO

Change SCO - GUI or Desktop interface to DOS based interface

Hi all I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface? If you have any ideas, please tell me then. Thank you

5. AIX

rsync error "file has vanished"

Hello, I am using rsync to synchronize some files from one server to other servers. When i take a look at the output file that it produces i noticed that for some files returns the message file has vanished: "<filename>" what might be the cause of that? do i do something wrong or...

6. Linux

Loopback interface doen't appear

Hi all, i have a problem with (Network in Linux) .. my issue with a HW appliance has openfiler 2.3 and is used for File Sharing using samba .. the problem is when i try to list all configured network interfaces using ifconfig -a .. i can't see the loopback interface, Although the file...

7. UNIX for Dummies Questions & Answers

How to Loopback?

This is in the beginning of the program: clear tput cup 1 20 echo "Welcome to UNIX I Final Assignment" tput cup 4 3 echo -e "Who would you like to look up? \c" tput cup 6 5 echo "vans, Rolland" tput cup 8 5 echo "ones, Mildred" tput cup 10 5 echo "mith, Julie" tput cup 12 5 echo...

8. UNIX Desktop Questions & Answers

Loopback

clear echo "vans, Rolland" echo "Press in Your Keyboard to Quit" echo -e "Please Enter Your Choice : \c" read option case $option in I have created the corresponding information for each input on the display so... My question is... How do I display the corresponding information...

9. UNIX for Dummies Questions & Answers

Adding a network interface to a bonded interface

I have a RHEL 5 system with a bonded interface configure using only one network port (eth0). So I have config file for ifcfg-bond0 and ifcfg-eth. I'd like to configure eth5 to be the second SLAVE in the bond. My question is, after I modify ifcfg-eth5, can I add eth5 to the bond0 interface without...

LEARN ABOUT MINIX

lo

LO(4)                                                      BSD Kernel Interfaces Manual                                                      LO(4)

NAME

     lo -- software loopback network interface

SYNOPSIS

     device loop

DESCRIPTION

     The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
     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(2).  The loopback interface should be the last interface configured,
     as protocols may use the order of configuration as an indication of priority.  The loopback should never be configured first unless no hard-
     ware interfaces exist.

     If the transmit checksum offload capability flag is enabled on a loopback interface, checksums will not be generated by IP, UDP, or TCP for
     packets sent on the interface.

     If the receive checksum offload capability flag is enabled on a loopback interface, checksums will not be validated by IP, UDP, or TCP for
     packets received on the interface.

     By default, both receive and transmit checksum flags will be enabled, in order to avoid the overhead of checksumming for local communication
     where data corruption is unlikely.  If transmit checksum generation is disabled, then validation should also be disabled in order to avoid
     packets being dropped due to invalid checksums.

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

     inet(4), intro(4)

HISTORY

     The lo device appeared in 4.2BSD.  The current checksum generation and validation avoidance policy appeared in FreeBSD 8.0.

BSD                                                               March 15, 2009                                                               BSD