08-16-2001
On solaris u can use
ifconfig hme0 dhcp release to release the ip address and the same can be verified using ifconfig -a and the ip address should be 0.0.0.0 and to get the ip address use
ifconfig hme0 dhcp start.
Substitute the apropriate interface name if it is not hme0
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When using DHCP how can I can my hostname. I vi all the hosts file and if still didn't work. So now my hostname is unknown and I want to change it. So if anyone out there can help me. Thank You (6 Replies)
Discussion started by: aojmoj
6 Replies
2. Solaris
Recently, the root pass expired on a Solaris box. And then, i can't log into the system anymore.....Below are two issues i met:
1. I tried to login the system via telnet and ssh. Only the ssh prompt me to set a new password. The system only told me that the pass is expired and turn it off during... (1 Reply)
Discussion started by: sleepy_11
1 Replies
3. Linux
Hi,
Request you to please let me know if any command is there in linux to release the ip of the ethernet card and renew the ip address of it again.
Similar to ipconfig /release and ipconfig /renew in windows.
Regards
Arun (2 Replies)
Discussion started by: Arun.Kakarla
2 Replies
4. Solaris
Hello experts ....
How can i renew my veritas license? Without using "vxlicinst" command? It is not renewing with that command?
Is there any manual way to install a license key...
Thanks in advance...... (3 Replies)
Discussion started by: younus_syed
3 Replies
5. UNIX for Dummies Questions & Answers
Hi All-
I have an assigned static IP address on my Linux box and was wondering if there is a way to change that to a DHCP without actually logging in?
Possibly a hot key I can press prioir to login?
I am running Centos
Thanks! (0 Replies)
Discussion started by: jvpike
0 Replies
6. IP Networking
Hi All,
I have two doubts here in DHCP Solaris environment.. could anyone please clarify me?
1. If a new client comes up and it needs an IP to be assigned by a DHCP server, how can it communicate with the DHCP server in the first case without any IP? The SUN doc says something about "BOOTP"... (4 Replies)
Discussion started by: satish51392111
4 Replies
7. IP Networking
Dear Experts,
I have a TI DM8148 EVM board REV C, the EZSDK5.05 SW package, and DVRRDK1.09 SW package.
EZSDK5.05, DVRRDK1.09 both use Linux2.6.37, however, there are some modifications between these two kernels.
When I use uImage of DVRRDK1.09 to boot up EVM board, this board can be given a... (0 Replies)
Discussion started by: oobin168
0 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.
The loopback interface lo0 is created at boottime, it always exists and cannot be destroyed with ifconfig(8). Additional loopback interfaces
can be created by using the ifconfig(8) create command.
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), ifconfig(8)
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.
BSD
September 3, 2006 BSD