-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable IPv6 #188
Comments
https://www.networkacademy.io/ccna/ipv6/stateless-address-autoconfiguration-slaac
I don't know how SLAAC & RHEL9 works... and how rhel determinate the IPv6 Address. |
Static IPv6 addresses for DNS:
|
Created a ticket, to update RA configuration: https://redhat.service-now.com/help?id=rh_ticket&table=sc_req_item&sys_id=0be58f5b9773061cd658b82bf253af6c |
Now the Yes the RA looks different:
I don't get an IPv6 default gateway anymore. And I'm not able to provide an IPv6 via DHCPv6, I see a lot of
|
Inf1 uptime is 202 days since that no update and reboot. Let's update and reboot inf1 and inf31 tomorrow morning around 10 CEST COE users informed via slack |
Asked RH NoC to check the switch config. |
Installed a dhcpd6 on inf49. Inf49 becomes all Solicit messages. But did not responde with an Advertise.
Good overview: https://blog.marquis.co/posts/2015-12-22-configuring-a-dual-stacked-dhcp-server/ |
|
UDP packages was not getting to dhcpd6:
firewalld was ne problem at inf49... the temp host |
|
Summary of some test with @dmoessne:
|
Current configuration:
Compare
|
After a reboot of inf1, I still see some udp packages with bad checksum. But dhcpd6 works! |
|
RH internal IT already provided an IPv6 Subnet
The IPv6 network will be from 2620:52:0::/48 and that is our internal only IPv4 mapped space.
There is no external IPv6 connectivity possible with that IP block.
Configuration:
Address assignment method: SLAAC
Net: 2620:52:0:2060::/64
Default GW: 2620:52:0:2060::ffe (but irrelevant as that information is sent/received via RA)
IPv6 VPN available at IAD2 and BRQ2
Tasks
The text was updated successfully, but these errors were encountered: