I am pretty new to this. My router was earlier configured to enable DHCP, thus my UNIX box is using the dhcp address, i.e. I have to do a ifconfig dhcp hme0 start. Since I am planning to use my NT as a web server, I needed to use the static IP address. How do I configure the unix box to use the... (5 Replies)
Hi there,
I have a Debian 5.0 server newly installed.
By default, the ip address is given by dhcp.
pegase:~# grep '^' /etc/network/interfaces
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
pegase:~# head -2 /etc/hosts
127.0.0.1 localhost
127.0.1.1 ... (1 Reply)
Hi All
I am having a solaris 10 virtual machine on vista (using vmware 7) laptop.
Now i want to access virtual machine from vista using putty.
Problem is that i insalled the solaris machine as dhcp. and whenever i connect to internet or reboot my system the IP address of solaris... (1 Reply)
Hi all,
I have literally spent all day trying dozens of different combinations, re-installs and tweaks to try and resolve this problem. I would be EXTREMELY grateful if anyone can help/point me in the right direction.
I am using OpenBSD 4.6 and am trying to connect to my wireless network with... (1 Reply)
Hi All,
Could you please explain the purpose of assigning the static IP by using the DHCP Concept. Like by using the clients MAC address we assign the static IP Address. Waiting for your reply. Thanks in Advance. (6 Replies)
Hello,
Greetings!!
I have a server with 3 TB of disk space and 12 GB RAM and a i7 processor.
What I did thus far is to install Oracle Enterprise Linux (OEL 5.7)as the host system and install Oracle Virtual box and created 3 VM's. Installed OEL 5.7 on one of the VM, working on installing... (1 Reply)
Hi all,
I would need to register a random free subdomain address and associate that to my IP Address. Any suggestion of a good service?
Also I don't have a static IP but i remember that there are services that automatically reset the right IP address behind the subdomain but i don't remember... (1 Reply)
p { margin-bottom: 0.1in; line-height: 120%; }a:link { } Hello,
I'm have an interesting issue with some Raspberry Pi's which I have on my home network.
The pi's are on 192.168.1.102, 192.168.1.103, 192.168.1.104
Something very strange is happening on my network. The pi on 192.168.1.104 is... (2 Replies)
Hi All,
Am using centos 7 in my vmware workstatio with the bridged network. when run the ifconfig cmd its not at all showing the ip address and pls advise how to set static ip address in my linux box. (1 Reply)
Discussion started by: sarathkumar s
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