[ipxe-devel] IPv6 Implementation & Windows 2012r2 Server

Geert Stappers stappers at stappers.nl
Sat Mar 11 15:07:04 UTC 2017


On Fri, Mar 10, 2017 at 12:56:06PM +0000, Felnhofer Roland wrote:
> Dear developers,
> 
> I built a version of "snponly.efi" based on source checked out 2017-03-08 with last commit d9886f1961f9970b4354442e84b98727b69cd73a
> 
> I attach my 2 local header files: console.h and general.h located in <ipxe root>/src/config/local
> 
> Running the following make command:
>                 make bin-x86_64-efi/snponly.efi EMBED=retry_dhcp_ipv6.ipxe
> 
> I've attach the embedded ipxe-file as well.
> 
> Now describing the actual issue.
> Same symptoms can be seen on physical devices as well as on virtual (VMware 6.0 ESXi virtual machine with Intel E1000(E))
> Therefore I ran most of my tests on virtual devices.
> 
> 
> I boot the machine via PXE-boot and chain load iPXE
> iPXE gets loaded
> I get an IPv4 and an IPv6 address.
> Pinging the http and DNS Server using IPv4 and IPv6 - it works
> I try to make an DNS lookup via IPv4 to a Windows 2012r2 Server- it works
> I try to make an DNS lookup via IPv6 to a Windows 2012r2 Server - it does NOT work
> I try to make an http download via IPv4 from a Windows 2012r2 Server - it works
> I try to make an http download via IPv6 from a Windows 2012r2 Server - it does NOT work
> 
> I try to make an http download via IPv6 from a Linux Server - it works
> I try to make an http download via IPv6 from a Linux/Unix Server (Google DNS-Server 2001:4860:4860::8888) - it works
> 
> I assume there is a certain issue between the IPv6 iPXE implementation and the Windows IPv6 implementation.

Seems so.

 
> The Windows DNS and Web Server works without problem for about 100 Linux und Windows Hosts using IPv6 as their primary protocol.

Okay, fine.

So Original Poster, OP, has all what is needed to some solve an interresting problem.
* the problem itself
* most likely an incentive to solve the problem
* working configurations
* a non working configuration
* source code and build tools for one end of the non working configuration
and hopefully full access at the other end of the non working configuration


I wonder what the reason is for the posting of the OP.

@OP  please elaborate



Groeten
Geert Stappers
-- 
Leven en laten leven



More information about the ipxe-devel mailing list