Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

trying to set static ipv6 address


  • Please log in to reply
3 replies to this topic

#1
fadedmaximus

fadedmaximus
  • Member
  • 2 posts
  • Joined 17-October 12
  • OS:none specified
  • Country: Country Flag
I'm trying to set a static ipv6 address in the unattend.xml for deployment but whenever it deploys the address that the machine is assigned isn't the address that is specified in the unattend.xml file. I tried looking around on-line but couldn't find any examples of ipv6 and only ipv6. If anybody can shed some light on how to fix the file to assign a static ipv6 address that would be great.

The unattend file specifies "2001:4898:e8:100b:98de:554a:9c3c:fbbf" as the ipv6 address, but the address that got assigned was "2001:4898:e8:100b:5dff:febc:8217"

Here is the tcp/ip section of the unattend file:

		<component name="Microsoft-Windows-TCPIP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" 

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
			<Interfaces>
				<Interface wcm:action="add">
					<Ipv4Settings>
						<DhcpEnabled>false</DhcpEnabled>
						<Metric>20</Metric>
						<RouterDiscoveryEnabled>false</RouterDiscoveryEnabled>
					</Ipv4Settings>
					<Identifier>Local Area Connection</Identifier>
					<Ipv6Settings>
						<DhcpEnabled>false</DhcpEnabled>
						<Metric>30</Metric>
						<RouterDiscoveryEnabled>true</RouterDiscoveryEnabled>
					</Ipv6Settings>
					<UnicastIpAddresses>
						<IpAddress wcm:action="add" wcm:keyValue="1">2001:4898:e8:100b:98de:554a:9c3c:fbbf/22</IpAddress>
					</UnicastIpAddresses>
					<Routes>
						<Route wcm:action="add">
							<Identifier>0</Identifier>
							<Prefix>0.0.0.0/0</Prefix>
							<Metric>10</Metric>
							<NextHopAddress><our default gateway address></NextHopAddress>
						</Route>
					</Routes>
				</Interface>
			</Interfaces>
		</component>

Thanks,

Edited by fadedmaximus, 17 October 2012 - 05:29 PM.



How to remove advertisement from MSFN

#2
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,897 posts
  • Joined 28-April 06
  • OS:Server 2012
  • Country: Country Flag

Donator

The IP Address needs to be in CIDR Format, as per [TechNet]

I can't seem to find an online converter for an IPv6 address to CIDR format, just the other way... or IPv4.
MSFN RULES | GimageX HTA for PE 3-5 | lol probloms
msfn2_zpsc37c7153.jpg

#3
fadedmaximus

fadedmaximus
  • Member
  • 2 posts
  • Joined 17-October 12
  • OS:none specified
  • Country: Country Flag

The IP Address needs to be in CIDR Format, as per [TechNet]

I can't seem to find an online converter for an IPv6 address to CIDR format, just the other way... or IPv4.


I found this site: dns crawler]
Adding in the ip address: 2001:4898:e8:100b:98de:554a:9c3c:fbbf
and the subnet mask 255.255.252.0, or /22, I get the netmask to be ffff:fc00:0:0:0:0:0:0

The calculator gives me:
CIDR Block
2001:4898:e8:100b:98de:554a:9c3c:fbbf/22

That is the address that I had initially set, so it appears that it is already in CIDR format like it requires.

<UnicastIpAddresses>
               <IpAddress wcm:action="add" wcm:keyValue="1">2001:4898:e8:100b:98de:554a:9c3c:fbbf/22</IpAddress>
</UnicastIpAddresses>

Edited by fadedmaximus, 18 October 2012 - 10:53 AM.


#4
johnhc

johnhc

    MSFN Junkie

  • Member
  • PipPipPipPipPipPipPipPipPip
  • 3,362 posts
  • Joined 02-March 08
  • OS:Windows 7 x64
  • Country: Country Flag
fadedmaximus, do you realize you are creating about 81 x 10 to the 30th power addresses? Did you mean to do this or 4,194,304 addresses (128-22=106 for the mask)? In your first post, the IP address changed to has only seven 16 bit values. One must be missing. I was curious how it was being changed. Where are you observing the assigned address, HW or VM? Are you stepping on some reserved addresses (a crazy guess/question). Enjoy, John




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users