Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, January 13, 2019 11:57 PM
My ISP supports IPv4 and IPv6 using DHCP. For IPv4, an address is allocated. For IPv6, only a /56 prefix is allocated, not an address. If I connect a Windows 10 PC to the WAN interface, it will only get a IPv4 address. Is there a way to get it to request a prefix and assign itself an address within the prefix? I realize this is an atypical configuration, but I'm wondering if there is a way to get it to work, irrespective of it not being typical.
Not that it should matter to anyone, but the reason I'm doing this is so I can analyze the traffic on the WAN interface, between my router and the ISP edge router. I can capture packets using wireshark without the PC having an IPv6 address, but I wanted to do a port scan and I can't do that without the PC having working IPv6.
All replies (5)
Wednesday, January 16, 2019 8:18 AM âś…Answered
Hi,
Thanks for your reply.
In my opinion, these settings are configured on the router, so we do everything on WIN 10 is useless.
I am currently performing research on this issue. If we have any updates or any thoughts about this issue, we will keep you posted as soon as possible.
Best regards,
Travis
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Monday, January 14, 2019 2:52 AM
Hi,
Stateful autoconfiguration of IPv6 is the equivalent to the use of DHCP in IPv4. It requires a DHCPv6 service to provide the IPv6 address to the client device and that both client device and server maintain the "state" of that address (i.e. lease time, etc).
Stateless autoconfiguration of IPv6 allows the client device to self configure it's IPv6 addreess and routing based on the router advertisements.
Please refer to the link below:
https://docs.oracle.com/cd/E19455-01/806-0916/6ja8539bh/index.html
You need to configure router to support stateful autoconfiguration or stateless autoconfiguration.
Best regards,
Travis
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Tuesday, January 15, 2019 1:54 AM
Thank you for the reply, but that won't work here. The ISP edge router works only by prefix delegation with a /56. It's intended for routers, not hosts. I'm trying to get the windows 10 host to act like a router by requesting a prefix. Once it has a prefix, any arbitrary address can be set within <prefix>::/64. Maybe this isn't possible.
Friday, January 18, 2019 4:16 AM
Hi,
Thanks for your reply.
In my opinion, these settings are configured on the router, so we do everything on WIN 10 is useless.
I am currently performing research on this issue. If we have any updates or any thoughts about this issue, we will keep you posted as soon as possible.
Best regards,
Travis
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
I think you are correct. The edge router is expecting a request for a prefix with no address. (This request is made by a dhcp client.) The edge router won't respond to any other type of request. It would be nice if the dhcp client on a windows 10 host could handle this, but I have yet to see any evidence that it's possible.
Friday, January 18, 2019 9:09 AM
Hi,
Yes, I agree with you. The key point is on the ISP edge router.
If the information provided is helpful, please "mark it as answer" to help other community members find the helpful reply quickly.
Best regards,
Travis
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]