While Perderabo is right about the myriad of configurations a given box can have, on just about every Unix I've dealt with, 'ifconfig -a' will list the configuration, including IP address, for all your network interfaces.
Quote:
Originally Posted by vertigo23
Also, it's certainly possible to configure a machine with no loopback interface. On BSD for example, just run 'ifconfig lo0 delete'.
The rfcs state that address 127.0.0.1 must never leave the originating system. Deleting the loopback interface will cause packets addressed to the loopback address to generate an error and this error constitutes a "contact". ;-)
I have a need to allow only certain IP addresses to access a machine running solaris 9. I am not sure how this can be accomplished.
Thanks in advance for your help.
Patch (2 Replies)
Is there any API call to get IP Address of a machine? I know there is function which returns name of the machine, gethostname(). But I need the IP.
Thanks & Regards,
Ahsan (7 Replies)
Hi all,
I am writing a program to retrieve the IP address or machine name of the local machine using C.
Is there any C function that does this?
ny clue will be of gr8 help!!!
thanx a lot. (1 Reply)
I am using windows Xp. From windows I would connect to my IBM AIX unix machine using telnet client. Is there any command available to view the IP address of Windows machine from Unix? (Note that ifconfig will give unix mahcine's IP address currently logged in.) (3 Replies)
Hi
i want to know the Ip address of the machine from where i logged into the unix server and made some changes to a file.
Can I know the last changes made to a unix file ? (3 Replies)
Hello
Please I ask if it is possible to recover data that is stored on a remote machine that I access via ssh on a usb ? if so, how?
Thank you so much (5 Replies)
hi all
i want to set ip address to a vitrual machine i am using following command.
but it is not ifconfig -a command output.
what is wrong i dont know
bash# ifconfig interfacename plumb
bash# ifconfig interfacename auto-dhcp
Please use code tags next time for your code and data. (4 Replies)
i m writing a program which finds the i.p address of the machine.
but it just prints out the first three character of the ifconfig output
but i want to just print my i.p address lik 10.0.0.222 which is in second line after inet addr:
code :
#include<iostream>
#include<cstdlib>
using... (1 Reply)
Discussion started by: console
1 Replies
LEARN ABOUT REDHAT
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