08-19-2011
If you just want to define the equivalent info if the client is IPv6 rather than IPv4, i.e telling the client the server where it can find the boot file, and the boot file location on that server, the options for IPv6 are
59 OPT_BOOTFILE_URL
60 OPT_BOOTFILE_PARAM
Option code 59 is a URL, but can be an IP address if enclosed in brackets, []
Option code 60 can be a boot file, similar format to what you'd define in OptBootF for an IPv4 client.
Exact details are defined in RFC 5970
Obviously the IPv6 client needs request those parameters.
If you are just porting IPv4 DHCP definitions from Solaris DHCP to ISC DHCP the option codes are the same , 66 and 67
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hello
i'm working on aix 5300-05-03 hacmp ver 5.4
well my issue is that when firewall (gateway to internet ) goes down my machine start to work very very slowly!!!
the output of the sniffer is that on the output card , my machine try to convert ipv4 to ipv6 0.0.2.0
my machine is not configure... (1 Reply)
Discussion started by: ariec
1 Replies
2. AIX
hello
i'm working on AIX 5300-05-03 P520 hacmp 5.4
when connection to the internet is going down , firewall down, my application work verey verey slowly!!! and on the sliffer output i'm got trys of my serevr to do convert from ipv4 ipv6 ( 0.0.2.0 and AAAAAAAA).
some one have an idea why... (1 Reply)
Discussion started by: ariec
1 Replies
3. Solaris
Hi folks, i hope you'll help me to configure my ipv6 tunnel.
First, i create my tunnel in:
Hurricane Electric Free IPv6 Tunnel Broker
My IP is 83.228.93.34
in HE:
------------------------
Server IPv4 address: 216.66.84.46
Server IPv6 address: 2001:470:1f14:16a::1/64
Client IPv4 address: ... (2 Replies)
Discussion started by: static
2 Replies
4. Shell Programming and Scripting
I have perl script that I use to check and ping a list of ip,
The problem is, I didnt understand how to ping ipv6 on perl,
Could I use Ping::External??And how could I get the ping result (reply or not)?
This is my code
#!/usr/bin/perl --
use Net::Ping;
use Data::Validate::IP;
use... (3 Replies)
Discussion started by: franzramadhan
3 Replies
5. UNIX for Advanced & Expert Users
Hi
I am looking to set-up ISC DHCP to support ipv6, and to migrate my existing SUN DHCP ipv4 to ISC,
finding the ipv4 options for the SUN DHCP options was ok eg
TFTPsrvN = tftp-server-name
OptBootF = bootfile-name
However if I set up a DHCPv6 does anyone know what the equivalent... (0 Replies)
Discussion started by: eeisken
0 Replies
6. UNIX for Advanced & Expert Users
Hi,
Apologies if this is the wrong forum or this question has been answered already.
I'm using the ISC dhcpd server on Centos 6.0, and can happily assign a single IPV6 address to a client with entries like this:
subnet6 fd01:0:0:5::/64
{
option dhcp6.name-servers fd01:0:0:5::226;... (0 Replies)
Discussion started by: jusme
0 Replies
7. AIX
Hi all,
I have setup ipv6 in AIX machine using autoconf6 command.
I was successfull in doing this. after execution of the command local link address was assigned to one of the interfaces
(en1).But I have to setup the following environment as well.
1) Machine with only IPv6 support(IPv4... (0 Replies)
Discussion started by: ard
0 Replies
8. Solaris
Hi,
I am looking for a solution to configure ntp between ipv4 ( ntp server ) to ipv6 ( client) .
I had google, but lot many sites suggest to have dual stock or tunnaling.
my issue is I have client has only ipv6 address ans server has ipv4 address. is it possible to sync time,... (4 Replies)
Discussion started by: naveen.surisett
4 Replies
9. Solaris
Hello dears
how to assign IPv4 and IPv6 addresses with same interface on solaris 10 (1 Reply)
Discussion started by: ttashman
1 Replies
dhcp(5) Standards, Environments, and Macros dhcp(5)
NAME
dhcp - Dynamic Host Configuration Protocol
DESCRIPTION
Dynamic Host Configuration Protocol (DHCP) enables host systems in a TCP/IP network to be configured automatically for the network as they
boot. DHCP uses a client/server mechanism: servers store configuration information for clients, and provide that information upon a
client's request. The information can include the client's IP address and information about network services available to the client.
This manual page provides a brief summary of the Solaris DHCP implementation.
Solaris DHCP Client
The Solaris DHCP client is implemented as background daemon, dhcpagent(1M). This daemon is started automatically during bootup if there
exists at least one dhcp.interface file in /etc. Only interfaces with a corresponding /etc/dhcp.interface file are automatically configured
during boot. Network parameters needed for system configuration during bootup are extracted from the information recieved by the daemon
through the use of the dhcpinfo(1) command. The daemon's default behavior can be altered by changing the tunables in the /etc/default/dhc-
pagent file. The daemon is controlled by the ifconfig(1M) utility. Check the status of the daemon using the netstat(1M) and ifconfig(1M)
commands.
Solaris DHCP Server
The Solaris DHCP server is implemented as a background daemon, in.dhcpd(1M). This daemon can deliver network configuration information to
either BOOTP or DHCP clients. The Solaris DHCP service can be managed using the dhcpmgr(1M) GUI or the command line utilities dhcpcon-
fig(1M), dhtadm(1M), and pntadm(1M).
DHCP Configuration Tables
The Solaris DHCP server stores client configuration information in the following two types of tables:
dhcptab tables Contain macros and options (also known as symbols), used to construct a package of configuration information to
send to each DHCP client. There exists only one dhcptab for the DHCP service. The dhcptab(4) can be viewed and mod-
ified using the dhtadm(1M) command or dhcpmgr(1M) graphical utility. See dhcptab(4) for more information about the
syntax of dhcptab records. See dhcp_inittab(4) for more information about the DHCP options and symbols.
DHCP network tables DHCP network tables, which contain mappings of client IDs to IP addresses and parameters associated with those
addresses. Network tables are named with the IP address of the network, and can be created, viewed, and modified
using the pntadm command or dhcpmgr graphical utility. See dhcp_network(4) for more information about network
tables.
SEE ALSO
dhcpinfo(1), dhcpagent(1M), dhcpconfig(1M), dhcpmgr(1M), dhtadm(1M), ifconfig(1M), in.dhcpd(1M), netstat(1M), pntadm(1M), syslog(3C),
dhcp_network(4), dhcptab(4), dhcpsvc.conf(4), dhcp_inittab(4), dhcp_modules(5)
Solaris DHCP Service Developer's Guide
Alexander, S., and R. Droms. RFC 2132, DHCP Options and BOOTP Vendor Extensions. Silicon Graphics, Inc. Bucknell University. March 1997.
Droms, R. RFC 1534, Interoperation Between DHCP and BOOTP. Bucknell University. October 1993.
Droms, R. RFC 2131, Dynamic Host Configuration Protocol. Bucknell University. March 1997.
Wimer, W. RFC 1542, Clarifications and Extensions for the Bootstrap Protocol. Carnegie Mellon University. October 1993.
SunOS 5.10 13 Mar 2001 dhcp(5)