10-30-2010
ps -ef | grep dhcp
Quote:
root 880 1 0 Oct28 ? 00:00:00 dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
cat /etc/network/interfaces
Quote:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
run similar commands on your machine and see what that interface is configured for.
8 More Discussions You Might Find Interesting
1. IP Networking
Hi all,
I am experiencing a problem with dhcp broadcast packages. these broadcast packages are seen on bge1 and bge1:1 interfaces but somehow they are not seen at bge771001 interface which is second virtual interface on the bge1 interface.
I have a server on which I configured it as working... (2 Replies)
Discussion started by: ironoxide
2 Replies
2. IP Networking
I have a Realtek 8139 interface in one of my machines and it will not connect to the network. /etc/rc.conf contains ifconfig_rl0="DHCP" and "rl0" was obtained from a dmesg. A network interface restart yields the following:
# /etc/rc.d/netif restart
Stopping network: lo0 rl0 fwe0 plip0.
rl0: no... (3 Replies)
Discussion started by: figaro
3 Replies
3. 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... (2 Replies)
Discussion started by: mbouster
2 Replies
4. SCO
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 (2 Replies)
Discussion started by: TinhNhi
2 Replies
5. IP Networking
This is my situation
DOS pc serial cable (sl0) Linux Pc eth1
192.168.0.10 <-------------------->192.168.0.2 <------------>192.168.0.1 (router)
I connected the linux pc and the dos pc with a SLIP (serial line internet protocol), so they can communicate in the sl0 interface.
... (3 Replies)
Discussion started by: mghis
3 Replies
6. IP Networking
Hi,
We currently operate a DHCP Server on Vxworks system.
It seems that the server is functioning only over the boot interface.
While trying to use it on a different interface the DHCP client messages seems to reach the interface but stay without response.
From a... (1 Reply)
Discussion started by: zohara
1 Replies
7. UNIX for Dummies Questions & Answers
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... (1 Reply)
Discussion started by: westmoreland
1 Replies
8. IP Networking
Hi All ,
please view the set up below:
-------------------------------------------------------------------
| DHCP Server |-----------| ROUTER & |-----------| Clients |
| 192.168.99.1 | - -<eth1>| DHCP-RELAY|<eth2>-- | 192.168.88.X |
... (2 Replies)
Discussion started by: gdangoor
2 Replies
LO(4) BSD Kernel Interfaces Manual LO(4)
NAME
lo -- software loopback network interface
SYNOPSIS
pseudo-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.
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), ns(4)
HISTORY
The lo device appeared in 4.2BSD.
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.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution