10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
When I do simple nslookup it does not generate any query for IPV6 (AAAA). But sometimes I see DNS query for both A and AAAA are generated. What decides this? The reason I do not want AAAA query is in most of the cases AAAA records are absent. Hence, if one DNS server fails, the clients keeps... (1 Reply)
Discussion started by: broy32000
1 Replies
2. IP Networking
Hello all,
I am trying to receive (tcp/udp/sctp) traffic from all IPs and, eventually, all ports of an IPv6 address block using as few sockets as possible short of implementing my own network stack.
One possible solution was to associate an IP block to an interface then bind to that... (6 Replies)
Discussion started by: redwil
6 Replies
3. Shell Programming and Scripting
Hi All,
Would anyone know how to modify the below, so only the IPv6 address (red) is printed, please?
(in other words, what's between inet6 and the / sign)
ipv6=`/sbin/ifconfig lo0:5 inet6 | grep 'inet6'`
print $ipv6
Currently the output of the above script is:
inet6... (7 Replies)
Discussion started by: chatguy
7 Replies
4. BSD
Hi,
Am using FreeBSD7.4/i386
During IPv6 configuration, I added the following in rc.conf as
Restarted IPv6 network using /etc/rc.d/network_ipv6 restart..
My problem is I need to set link local IPv6 address auto-configured..
Is my proceeding right??
I feel something missing to make... (0 Replies)
Discussion started by: Priya Amaresh
0 Replies
5. HP-UX
How do I configure site-local IPv6 address in HP-UX box?
I can get link local IPv6 address automatically when I put IPv6 up.
aps39-88-root# ifconfig lan0 inet6 up (0 Replies)
Discussion started by: kirtikjr
0 Replies
6. Shell Programming and Scripting
Hi all ,
I have a string in my weblog xheader v6-day-2011:xx:yy:zz:qq:qq:ww:ee:rr
My requirement is to lookup the sting v6-day-2011 in this header and if found would like to extract the V6 ip part .
v6-day-2011 is always constant for a ipv6 entry so i would like to extract every thing... (4 Replies)
Discussion started by: jambesh
4 Replies
7. Solaris
Hi,
inspired by this article, I decided to implement IPMP + IPv6 in Solaris 10.
It worked for me only this way:
1. Setup
# cat /etc/hostname*
10.23.10.113/24 broadcast + group data failover up <- hostname.e1000g0
0.0.0.0/24 broadcast + group data -failover deprecated up standby... (3 Replies)
Discussion started by: masloff
3 Replies
8. Programming
I know there is a function inet_tpon for unix platforms to validate ipv6 addresses.But i need an equivalent of windows.When i use this function with the header file <winsock2.h> the visual studio 2005 on win2003 issues an error saying identifier not found
:confused: (3 Replies)
Discussion started by: guru13
3 Replies
9. IP Networking
Hi All,
I am running a IPv6 UDP server, which is bound to in6addr_any. When I send a packet from a client to the link-local address of any interface on the linux box, the server accepts the packets. But when I send the packets to the global address the server doesnt pick the packets.
On... (0 Replies)
Discussion started by: muralia
0 Replies
10. UNIX for Dummies Questions & Answers
I don't have root access. How do I find i.p address of our sun server? Thanks. (4 Replies)
Discussion started by: vpotluri
4 Replies
dhcp6s.conf(5) File Formats Manual dhcp6s.conf(5)
NAME
dhcp6s.conf - configuration file of the DHCPv6 server daemon, dhcp6s
DESCRIPTION
dhcp6s.conf contains the configuration information of addresses, prefixes, or various network configuration parameters for each of the
interfaces. The network configuration parameters can be described globally for all of the interfaces. The default address preferred life
time is 36000 seconds; the default address valid life time is 72000 seconds if they are not defined in any declaration. The specific decla-
ration order is interface, link, host; within link the more specific declaration is pool.
The interface definitions are described in the following form:
interface <interface name>
{
[declarations];
};
where each of the declarations could be of type link, group, or host. Each declaration and the statements within each of these declara-
tions must be terminated by a semicolon. Additional details of the declarations are specified below.
DECLARATIONS
interface <interface name>
{
[declarations];
};
An interface declaration is used to inform the DHCPv6 server that the links and hosts declared within it are connected to the same network
segment. Common network parameters for this network segment can be defined within the interface declaration.
link <link name>
{
[declarations];
};
A link declaration is used to provide the DHCPv6 server the IPv6 assgined address ranges, prefixes, and hosts. Common network parameters
for this link can be defined within the link declaration.
group
{
[declarations];
};
A group declaration is used to group a list of declarations together to define the common network parameters. These network parameters are
valid within this declaration only. Declarations can be one of the following types: interface, link, pool, or host.
pool
{
[declarations];
};
The pool declaration is used to declare an address pool from which IPv6 address can be allocated, with its own permit to control client
access and its own declaration in which you can declare pool-specific network parameters.
host <host name>
{
[duid <DUID0];
[iaidinfo {}];
[address {}];
[prefix <prefix>/<prefix length>];
[declarations];
};
This declaration allows administrators to describe the addresses, prefixes, and network configuration parameters for this host. As for
this declaration, the DHCP Unique Identifier (DUID), Identity Association Identifier (IAID), and addresses must be specified. The host dec-
laration is used to do Static Address Assginment for a particular DHCPv6 client.
address
{
[<ipv6 address>/<prefix length>];
[prefer-life-time <preferred lifetime>];
[valid-life-time <valid lifetime>];
};
This statement allows administrators to specify the address for the host. Preferred Lifetime and Valid Lifetime also can be set in this
statement. This statement is valid only in host {} declarations.
prefix <prefix>/<prefix length>;
This statement allows administrators to specify the prefix. This parameter is needed when configuring dhcp6s as the Delegation Router for
the Prefix Delegation. dhcp6s assigns the specified prefixes to the requesting routers.
relay <relay>/<prefix length>;
This statement specifies the prefix that the relay agent will put in the link address field of the RELAY-FORW message to indicate the link
the client is attached to. If the link-address matches this prefix, this link declaration will be used. This statement is only valid in the
link declaration.
iaidinfo
{
[iaid <IAID number>];
[renew-time <renew time>];
[rebind-time <rebind time>];
};
This statement allows administrators to describe the information for this IAID. This statement is only valid in host {} declarations. iaid
is required; renew-time and rebind time are optional in this statement.
range <ipv6 address> to <ipv6 address>/<prefix length>;
This statement allows adminstrators to use "range" and "to" keywords and prefix length to specify an address range. For each range not
more than one of the unassigned addresses will be assgined to the requested client.
duid <DUID>;
DUID is a DHCP Unique Identifier for a DHCP participant. Using this option, the administrator can specify the DUID of this DHCPv6 client.
The duid statement is valid only in host {} declarations.
iaid <IAID number>;
IAID is a Identity Association Identifier. IA is a collection of addresses assigned to a client. Using this option, the administrator can
specify the IAID in iaidinfo for a host declaration.
renew-time <renew time>;
This statement allows administrators to specify the RenewTime (T1). The recommended value for RenewTime is .5 times the shortest preferred
lifetime of the address in the IA, if the value is not defined.
rebind-time <rebind time>;
This statement allows administrators to specify the RebindTime (T2). The recommended value for RenewTime is .8 times the shortest pre-
ferred lifetime of the address in the IA, if the value is not defined.
prefer-life-time <preferred lifetime>;
This statement allows administrators to specify the Preferred Life Time for each address.
valid-life-time <valid lifetime>;
This statement allows administrators to specify the Valid Life Time for each address.
option dns_servers <ipv6 addresses or domain name list>;
This statement allows administrators to specify the DNS servers.
send <OPTION>;
This declaration enables dhcp6s to include the specified option in sending DHCPv6 messages.
send unicast;
This declaration enables dhcp6s to send a Server Unicast option. Usually DHCPv6 clients must use multicast addresses to contact the DHCPv6
server and agents. This declaration specifies that dhcp6s will accept unicast messages from DHCPv6 clients if they include a Server Unicast
option.
server-preference <server preference value>;
This declaration enables dhcp6s to include a Preference option for sending DHCPv6 messages. DHCPv6 clients will pick up the DHCPv6 server
which has highest preference value. The highest preference value is 255.
send temp-address;
This declaration assigns a temporary address to the requesting client.
send information-only;
This option enables dhcp6s to give only configuration information rather than assigning client addresses. This could be, for example, DNS
server address configuration information.
allow <OPTION>;
This declaration allows the DHCPv6 client to specify an option in receiving DHCPv6 messages.
allow rapid-commit;
This option enables dhcp6s to allow the Rapid-Commit option from the DHCPv6 client and the Solicit-Reply message exchanges.
allow unicast;
This option enables dhcp6s to allow the Server Unicast option for the DHCPv6 client. Usually DHCPv6 clients must use multicast addresses to
contact DHCPv6 server and agents. With this declaration, dhcp6s accepts unicast messages from DHCPv6 clients if they include a Server Uni-
cast option.
allow information-refresh-time <information refresh time>;
This option enables dhcp6s to offer a client an upper bound for how long a client should wait before refreshing information which the
client retrieves by a response to an information only request. If this option is not specified, dhcp6s offers 86400[sec] (24 hours). If you
want to offer a client not to refresh the information, specify infinity as the value.
EXAMPLES
This is a sample of the dhcp6s.conf file.
option dns_servers 2003::6:1 ibm.com;
prefer-life-time 10000;
valid-life-time 20000;
renew-time 5000;
rebind-time 8000;
interface eth1 {
link AAA {
allow unicast;
send unicast;
allow rapid-commit;
server-preference 5;
renew-time 1000;
rebind-time 2400;
prefer-life-time 2000;
valid-life-time 3000;
range 3ffe:ffff:100::10 to 3ffe:ffff:100::110/64;
prefix 3ffe:ffef:104::/64;
pool {
prefer-life-time 3600;
valid-life-time 7200;
range fec0:ffff::10 to fec0:ffff::110/64;
prefix fec0:fffe::/48;
};
};
host host0 {
duid 00:00:00:00:a0:a0;
iaidinfo {
iaid 101010;
renew-time 1000;
rebind-time 2000;
};
address {
3ffe:ffff:102::120/64;
prefer-life-time 2000;
valid-life-time 3000;
};
};
group {
prefer-life-time 5000;
valid-life-time 6000;
host host1 {
duid 00:00:00:00:a1:a1;
iaidinfo {
iaid 101011;
renew-time 1000;
rebind-time 2000;
};
};
host host2 {
duid 00:00:00:00:a2:a2;
send information-only;
};
};
};
SEE ALSO
dhcp6s(8)
BUGS
Report bugs via http://fedorahosted.org/dhcpv6/
AUTHORS
See http://fedorahosted.org/dhcpv6/wiki/Authors
dhcp6s.conf(5)
