Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 317947 Details for
Bug 463619
[LTC 6.0 FEAT] 201223:DHCPv6 updates
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
TFD for the information refresh time option
dhcpv6_irt-tfd (text/plain), 2.11 KB, created by
IBM Bug Proxy
on 2008-09-29 10:41:00 UTC
(
hide
)
Description:
TFD for the information refresh time option
Filename:
MIME Type:
Creator:
IBM Bug Proxy
Created:
2008-09-29 10:41:00 UTC
Size:
2.11 KB
patch
obsolete
>TFD for "Information Refresh Time Option for DHCPv6" Feature. > >BASIC INFORMATION >================= >This TFD covers DevTrack ID 201223 > >Release: RHEL6 >Contact: Sridhar Samudrala <sri@us.ibm.com> > Mitsuru Chinen <chinen@jp.ibm.com> > >PHASE 1 >======= >Risk Assessment >--------------- > This is a "low" risk feature that only affects users that enable IPv6 in >their network environment. > >Planned Test Methodology >------------------------ > Manual tests > >PHASE 2 >======= >Description of Feature >---------------------- >Update DHCPv6 implementation(Client and Server) to support RFC4242, >"Information Refresh Time Option for DHCPv6". This feature establishes >the lifetime for the configuration data without IPv6 address information. >It is an update of RFC3736 that we already supported. It is necessary to >keep the appropriate configuration data (e.g. DNS server) > >Test Plan >--------- >Manual Tests: >1. Prepare 2 Linux boxes. One is a server, the other is client. > >2. Prepare dhcp6s.conf on the server. > | # cat /root/dhcp6s.conf << EOF > | option dns_servers 2001:db8::2; > | allow information-refresh-time 600; > | interface eth0 { > | link AAA { > | }; > | }; > | EOF > >3. Prepare dhcp6c.conf on the client > | # cat /root/dhcp6c.conf << EOF > | interface eth0 { > | information-only; > | request domain-name-servers; > | }; > | EOF > >4. Start dhcp6s at the server > | # dhcp6s -vf -c /root/dhcp6s.conf lan0 > >5. Start dhcp6c at the client > | # dhcp6c -vf -c /root/dhcp6c.conf eth0 > >*) Step 6 and 9 must be done within 600 seconds. >6. At the client, check /etc/resolv.conf includes the address of DNS > server written in dhcp6s.conf <== Check 1 > | # cat /etc/resolv.conf > | nameserver 2001:db8::1 > >7. At the server, stop the dhcp6s. > >8. At the server, modify the address of DNS server written in dhcp6s.conf > from 2001:db8::1 to 2001:db8::2. > | # dhcp6s -vf -c /root/dhcp6s.conf lan0 > >9. At the server, restart dhcp6s > >10. After 600sec is passed from dhcp6c starts, check /etc/resolv.conf includes > the new address of DNS server at the client <== Check 2 > | # cat /etc/resolv.conf > | nameserver 2001:db8::2
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 463619
: 317947 |
321368