Quote Originally Posted by tschulte79 View Post
Hi!

I'm trying to setup an IPv6 address, but this seems to fail when running openSUSE and SLES instances which use Wicked for network configuration.

At first I enabled IPv6 in a fresh VPC according to this documentation:
http://docs.aws.amazon.com/AmazonVPC...rted-ipv6.html

In "eu-central-1" I tested:

* openSUSE Leap 42.2 (ami-2af53a45)
* SLES 12 SP2 (ami-c425e4ab)
* Amazon Linux AMI 2016.09.1 (ami-af0fc0c0)

When the Amazon Linux instance boots, it is automatically set up with the configured IPv4 and IPv6 addresses.
The openSUSE / SLES instances are successfully set up with the configured IPv4 address, but instead of getting the configured IPv6 address, it just uses an "fe60:" link-local address.

The following workaround is possible to retrieve the desired IPv6 address:

# systemctl disable wicked.service
Disabling the wicked.service seems to be mandatory for running the following commands.

# dhclient6 -v eth0
This does not work. "dhclient6" just fetches the IPv4 address which the system already knows, so it doesn't change anything relevant.

# dhclient -6 -v eth0
This command temporarily solves the issue by fetching the desired IPv6 address:

Code:
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on Socket/eth0
Sending on   Socket/eth0
Created duid \000\001\000\001 <,\024\006\3746\273!\305.
PRC: Soliciting for leases (INIT).
XMT: Forming Solicit, 0 ms elapsed.
XMT:  X-- IA_NA 36:bb:21:c5
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on eth0, interval 1060ms.
RCV: Advertise message on eth0 from fe80::47a:xxxx:xxxx:xxxx.
RCV:  X-- Preference 255.
RCV:  X-- IA_NA 36:bb:21:c5
RCV:  | X-- starts 1487499156
RCV:  | X-- t1 - renew  +75
RCV:  | X-- t2 - rebind +120
RCV:  | X-- [Options]
RCV:  | | X-- IAADDR 2a05:d014:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
RCV:  | | | X-- Preferred lifetime 150.
RCV:  | | | X-- Max lifetime 450.
RCV:  X-- Server ID: 00:03:00:01:06:7a:8f:xx:xx:xx
RCV:  Advertisement immediately selected.
PRC: Selecting best advertised lease.
PRC: Considering best lease.
PRC:  X-- Initial candidate 00:03:00:01:06:7a:8f:xx:xx:xx (s: 152, p: 255).
XMT: Forming Request, 0 ms elapsed.
XMT:  X-- IA_NA 36:bb:21:c5
XMT:  | X-- Requested renew  +3600
XMT:  | X-- Requested rebind +5400
XMT:  | | X-- IAADDR 2a05:d014:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
XMT:  | | | X-- Preferred lifetime +7200
XMT:  | | | X-- Max lifetime +7500
XMT:  V IA_NA appended.
XMT: Request on eth0, interval 930ms.
RCV: Reply message on eth0 from fe80::47a:xxxx:xxxx:xxxx.
RCV:  X-- IA_NA 36:bb:21:c5
RCV:  | X-- starts 1487499156
RCV:  | X-- t1 - renew  +75
RCV:  | X-- t2 - rebind +120
RCV:  | X-- [Options]
RCV:  | | X-- IAADDR 2a05:d014:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
RCV:  | | | X-- Preferred lifetime 150.
RCV:  | | | X-- Max lifetime 450.
RCV:  X-- Server ID: 00:03:00:01:06:7a:8f:xx:xx:xx
PRC: Bound to lease 00:03:00:01:06:7a:8f:xx:xx:xx.
Checking DAD results for 2a05:d014:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Of course this does not survive a reboot, so I'd need to find a way to set up IPv4/IPv6 automatically.
Please note that I'm able to reproduce this issue with every new EC2 instance, as long as Wicked is involved.
No additional configuration changes were done, so all config files should contain the original values.

Any suggestions?

Thanks!
Thomas


Can you check if you enabled IPv6 forwarding . If its enabled IPv6 auto assign will not work .

May be you can try setting net.ipv6.conf.all.accept_ra = 2 if you still want to forward traffic on server

Thanks,
Sarath