IPv6 Stateful / Static Addressing

Hi All, 
I'm trying to setup a static set of IPv6 address assignments in a lab / testing setting. I have working IPv6 connectivity via a PPPoE interface and the router is able to ping the IPv6 internet without issue. In addition, I have some machines on the LAN side of the router that can ping and connect to the IPv6 internet using the router's LAN address as the gateway.
Everything works fine when I am statically assigning / configuring the addresses on each machine on the LAN.
Now, to keep configuration simple I'd like to centralize configuration on the router. I do the same with IPv4 using DHCP pools that have client-identifier specified in the pool; thus assigning static addresses to clients via DHCP.
I'm trying to accomplish the same thing with IPv6 stateful but I'm having issues. I've been able to assign a prefix to DHCPv6 stateful assignments, and I can see via the debug logs on the router that my local machines are grabbing IPv6 addresses statefully. Everything works but I'm unable to figure out two things:
1) How to constrain client requests to a pool based on client identification. As above, with IPv4 pools using a client-identifier with a MAC addresses accomplishes this.
2) How to constrain the addresses assign to the clients within the pool; assignment seems to happen on a prefix level only and I really want to assign the entire address.
I can see using the debug logs on the router that there are some references to the "username" of the request client (seems to be the DUID) and how this username has no entry in the pool database so an address is being assigned at random. I think the key is possible in adding static entries to this pool database but I can't see how that would be done at all.
Any hints / tips?
Thanks!
Dylan

A scalable solution would be to configure a RADIUS server and provide the client their IP address via the frame-ip-address attribute. A hack could be to have a group defined on the EasyVPN server which is associated with an IP pool that has only one address available.

Similar Messages

  • Can't set ipv6 static address

    As the topic states, I can not setup a static IP to save my life. I've enabled ipv6, I have a hostname6.ce1 I put the hostname (madrid-ipv6) in the hostname6.ce1 file but it will not stay set.
    I've tried the addif command, and it creates a logical interface, but I can't ping out with the address that is set.
    I'm sure I am missing something, and I am new to Solaris. I've got ipv6 static addresses setup in linux with no problems. It's just Solaris 10 that is kicking my butt.
    If anyone can point me in the right direction I would be in your debt.
    Thanks!

    edit: To darren: I've tried that as well. When the system boots, it gives me the error: "Failed to assign ipv6 address to ce1" or something similar to that.
    hmmm, I've tried that, it still doesn't seem to be working. Here is my hostname6.ce1 file:
    madrid-ipv6
    addif fd01::e2/64 up
    this is the output of ifconfig -a6:
    bash-3.00# ifconfig -a6
    lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
    inet6 ::1/128
    ce0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
    inet6 fe80::203:baff:fe9b:92d/10
    ether 0:3:ba:9b:9:2d
    ce1: flags=2000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 3
    inet6 fe80::203:baff:fe9b:92d/10
    ether 0:3:ba:9b:9:2d
    ce1:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 3
    inet6 fd01::e2/64
    and this is what I get when I ping fd01::f2:
    bash-3.00# ping fd01::f2
    ICMPv6 Address Unreachable from gateway fd01::e2
    for icmp6 from fd01::e2 to fd01::f2
    ICMPv6 Address Unreachable from gateway fd01::e2
    for icmp6 from fd01::e2 to fd01::f2
    ICMPv6 Address Unreachable from gateway fd01::e2
    for icmp6 from fd01::e2 to fd01::f2
    I've got to be missing something. This is all on a private switch that doesn't need to connect to the net. I need to connect an iscsi VTL to this sun system but the first step is to be able to ping the damn thing. I've checked the networking to make sure everything is connected. I can ping the VTL using IPV4, but not IPV6. I've checked on a linux system and it can ping the VTL over IPV6 so I know it is setup properly. This is just driving me nuts.
    Edited by: jonwheeler on Sep 11, 2008 9:47 AM

  • IPv6 Link-local addresses: EUI-64 or Static?

    Hello Everyone.
    What is the best practice? Configuring a static link-local address on the interface, or letting the router pick an eui-64 one?
    From a dynamic routing process point of view, does it really matter which type of link local address is used in a production network?
    I know that static addresses are more convinient for humans. But what about the IOS?
    Any other considerations?
    Thank you all.

    Hello,
    I would say that as you already know when you use a routing protocol on IPv6 the neighbor will always be the link local address from the interface from the neighbor itself,
    So I would say why to use Dynamic( Cause it's easy,it's scalable as it's based on a unique value)
    Why to use Static ( So you can create your own system to identify the neighbor, I have read that for security purposes you can use a mechanism that will create random EUI-64 based on a hash but as this is only for Link-Local address I would say it does not apply here)
    Regards

  • IPv6 Static address

    I have a Swann Communication security camera system with their DVR8-4000 hooked to an IPv4 router, connected to the Internet using the new HughesNet Gen4 service. 
    The Swann DVR wired to my router requires a static IP address.  HughesNet Gen4 is implemented with IPv6 and I am told that it does not accommodate an IPv4 type static address.
    I have discussed the issue with both company’s technical support.  HughesNet Gen4 reps recognize the issue and may support static addressing in the future, but not now.  Swann reps will not modify their implementation because of the relatively small Gen4 market.  The Swann rep suggested that replacing my IPv4 router with an IPv6 router might resolve the “static IP address” issue.
    I am looking at several Linksys IPv6 routers including the EA4500 SMART WiFi Wireless Router N900, but know too little about IPv4, IPv6 and router/static addressing to proceed unassisted.
    I will be grateful for any guidance; including 1) can I implement a static address with an Linksys IPv6 router cdonnected to Gen4?  2) Which Linksys routers offer IPv6 support?  3) How does one go about setting an IPv6 static address using HughesNet Gen4 on a Linksys router?

    For your 1st question, the EA4500 does support manual ipv6 but only for 6rd tunneling. For your 2nd question, E4200 v1&2 and the EA series routers support ipv6. Last, for your 3rd question; as long as you have the 6rd tunnel settings from your ISP then you will be able manually set ipv6 on your router.

  • How to use both wired and wireless connection with static addresses

    Now that I have setup my home network with static addresses (router, mini1, mini2 and PC) in the way I want, (big thanks to BDAqua http://discussions.apple.com/thread.jspa?threadID=1271635&tstart=0) I would like to understand some more advanced network concepts.
    I would like to change the network so that I use both the wireless connection and the built-in ethernet connection at the same time in my Mac mini1. I would like to connect my PC to my Mac mini by using the wired ethernet connection so that I reach the Internet from my PC as well. I would also like to be in control of all the addresses therefore I want to assign the addresses manually.
    The question: What addresses should I use between mini1 and PC? Should I use the same wireless address space as I already use between the wireless router and the other computers (router: 192.168.1.1, mini1: 192.168.1.101, mini2: 192.168.1.103) or should I use something totally different like 10.X.X.X? What should I put in ethernet connection "Router"-field, the same as in Airport (192.168.1.1)? What about DNS, same as in Airport?

    If I understand this correctly, you wish your Mini to perform Internet Sharing for your PC, correct!?
    If so you'll pretty much have to let the Mini handle DHCP & NAT on the Ethernet port. You also want to be sure Airport is dragged to the top of Network>Show:>Network Port Configurations, that's what position the Mini will use 1st for Internet itself.
    On the Mini turn on both Web Sharing & Internet Sharing. The PC once connected will have the Mini's Ethernet IP as it's Gateway addy.

  • RRAS 2012 With DHCP Works, Cannot Get Static Address Pool To Connect Completely

    Hello Forums Users:
    I have set up RRAS/DA 2012 successfully incorporating my AD DHCP server.   Every connection works and I see all networks that I have VPN tunnels set up with, which is totally cool.    However, I want to assign remote VPN users IP's from a
    static address pool - and while the setup completes without issue and the client connects, I can see absolutely nothing.    No good pings, no connect to Lync client, Outlook, etc. etc.
    I am OBVIOUSLY missing something but have no idea what that is.   Do I need to add something (and I really have no idea what that "something" is) to RRAS config so the static address pool (192.168.40.0 in this case) has the same access as
    the AD DHCP pool does?
    Thanks again for taking the time to check this out and comment.

    Bill:
    Thanks for the reply....  yes, the idea is to free up a pool of IP's large enough to accomodate all 170 staff.   Our current 192.168.2.x DHCP hands out 150, but I need to plan for DR/BCP when other locations (about 110 users) remote in when their
    location goes dark.
    I already have VPN tunnels between the main locations and a VPN user can see ALL of them when it gets an IP from DHCP.   Are you saying that I have to add routes to all the routers/firewalls to accomplish this?
    Or would I use IPv4 Static Routes?   A network I'd like access to is 192.168.14.0 /24.   Would the route look like any of these?   Sorry it's not clear what I would use as the gateway (192.168.2.1 is the RRAS server network gateway, 192.168.2.6
    is RRAS IP)
    Destination         Net Mask               Gateway                Interface
    192.168.14.0      255.255.255.0        192.168.2.1            LAN
    192.168.14.0    255.255.255.0
      192.168.14.254      LAN             (
    (.254 is the remote gateway)

  • DFSDiag TestDCs Warning - Site Association by IPv6 Link Local Addresses?!?

    Why is DFSDiag
    using IPv6 Link Local Addresses (fe80::/64) for /TestDCs Site Association test?
    C:\Users\Administrator\Documents>dfsdiag /testdcs
    DFSDIAG_INFO - APPL - Client Domain found to be BRREX.
    Starting TestDcs ....
    Validating DFS Service ....
    Validating DFS Service on FINCH.
    DFSDIAG_INFO - APPL - DFS Service on FINCH is OK.
    Validating SiteCostedReferrals Key ....
    Validating SiteCostedReferrals in FINCH.
    DFSDIAG_INFO - APPL - SYSVOL/NETLOGON referrals are site costed.
    Validating Registry Entries ....
    BRREX has a single domain controller.
    Validating SiteAssociation ....
    Validating SiteAssociation of FINCH in every DC.
    DFSDIAG_WARNING - APPL - SiteName from IP - fe80::a402:d343:baa3:5f5e%12 of FINCH in DC - FINCH is NULL while in ADSite it is GoGrid,
    this can lead to different referral ordering.
    DFSDIAG_WARNING - APPL - SiteName from IP - fe80::7473:f9f8:c5c3:17e6%13 of FINCH in DC - FINCH is NULL while in ADSite it is GoGrid,
    this can lead to different referral ordering.
    Finished TestDcs.
    C:\Users\Administrator\Documents>
    DFSDiag problems with IPv6 Link Local addresses has occurred
    three (3) other times.
    My best guess is either AD DS or DFS don't like running on server routing IPv6 via
    6in4 tunnel.
    IPCONFIG follows:
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : finch
    Primary Dns Suffix . . . . . . . : brrex.com
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : brrex.com
    grid-store.brrex.com
    grid-node.brrex.com
    Ethernet adapter Private:
    Connection-specific DNS Suffix . : grid-store.brrex.com
    Description . . . . . . . . . . . : SUSE Network Driver for Windows #2
    Physical Address. . . . . . . . . : 00-16-6E-00-0B-1E
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:470:841e:1::100(Preferred)
    Link-local IPv6 Address . . . . . : fe80::a402:d343:baa3:5f5e%12(Preferred)
    IPv4 Address. . . . . . . . . . . : 10.113.0.40(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 2001:470:841e:1::100
    ::1
    10.113.0.40
    127.0.0.1
    NetBIOS over Tcpip. . . . . . . . : Disabled
    Ethernet adapter Public:
    Connection-specific DNS Suffix . : grid-node.brrex.com
    Description . . . . . . . . . . . : SUSE Network Driver for Windows
    Physical Address. . . . . . . . . : 00-16-6E-00-0B-1D
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 173.1.67.212(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.240
    Default Gateway . . . . . . . . . : 173.1.67.209
    DNS Servers . . . . . . . . . . . : 173.1.67.212
    127.0.0.1
    NetBIOS over Tcpip. . . . . . . . : Disabled
    Tunnel adapter Local Area Connection* 9:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter IP6Tunnel:
    Connection-specific DNS Suffix . : grid-node.brrex.com
    Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:470:1f04:53f::2(Preferred)
    Link-local IPv6 Address . . . . . : fe80::7473:f9f8:c5c3:17e6%13(Preferred)
    Default Gateway . . . . . . . . . : 2001:470:1f04:53f::1
    DNS Servers . . . . . . . . . . . : 173.1.67.212
    127.0.0.1
    NetBIOS over Tcpip. . . . . . . . : Disabled
    Tunnel adapter Local Area Connection* 12:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : grid-node.brrex.com
    Description . . . . . . . . . . . : isatap.grid-node.brrex.com
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter Local Area Connection* 13:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : grid-store.brrex.com
    Description . . . . . . . . . . . : isatap.grid-store.brrex.com
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    ROUTE PRINT follows:
    ===========================================================================
    Interface List
    12 ...00 16 6e 00 0b 1e ...... SUSE Network Driver for Windows #2
    11 ...00 16 6e 00 0b 1d ...... SUSE Network Driver for Windows
    1 ........................... Software Loopback Interface 1
    10 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
    13 ...00 00 00 00 00 00 00 e0 Microsoft Direct Point-to-point Adapater
    14 ...00 00 00 00 00 00 00 e0 isatap.grid-node.brrex.com
    15 ...00 00 00 00 00 00 00 e0 isatap.grid-store.brrex.com
    ===========================================================================
    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination Netmask Gateway Interface Metric
    0.0.0.0 0.0.0.0 173.1.67.209 173.1.67.212 266
    10.0.0.0 255.0.0.0 10.113.0.1 10.113.0.40 11
    10.113.0.0 255.255.255.0 On-link 10.113.0.40 266
    10.113.0.40 255.255.255.255 On-link 10.113.0.40 266
    10.113.0.255 255.255.255.255 On-link 10.113.0.40 266
    127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
    127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
    127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    173.1.67.208 255.255.255.240 On-link 173.1.67.212 266
    173.1.67.212 255.255.255.255 On-link 173.1.67.212 266
    173.1.67.223 255.255.255.255 On-link 173.1.67.212 266
    224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
    224.0.0.0 240.0.0.0 On-link 10.113.0.40 266
    224.0.0.0 240.0.0.0 On-link 173.1.67.212 266
    255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    255.255.255.255 255.255.255.255 On-link 10.113.0.40 266
    255.255.255.255 255.255.255.255 On-link 173.1.67.212 266
    ===========================================================================
    Persistent Routes:
    Network Address Netmask Gateway Address Metric
    10.0.0.0 255.0.0.0 10.113.0.1 1
    0.0.0.0 0.0.0.0 173.1.67.209 Default
    ===========================================================================
    IPv6 Route Table
    ===========================================================================
    Active Routes:
    If Metric Network Destination Gateway
    13 266 ::/0 2001:470:1f04:53f::1
    1 306 ::1/128 On-link
    13 266 2001:470:1f04:53f::/64 On-link
    13 266 2001:470:1f04:53f::2/128 On-link
    12 266 2001:470:841e:1::/64 On-link
    12 266 2001:470:841e:1::100/128 On-link
    13 266 fe80::/64 On-link
    12 266 fe80::/64 On-link
    13 266 fe80::7473:f9f8:c5c3:17e6/128
    On-link
    12 266 fe80::a402:d343:baa3:5f5e/128
    On-link
    1 306 ff00::/8 On-link
    13 266 ff00::/8 On-link
    12 266 ff00::/8 On-link
    ===========================================================================
    Persistent Routes:
    If Metric Network Destination Gateway
    0 4294967295 ::/0 2001:470:1f04:53f::1
    ===========================================================================
    Thanks in advance!

    Did you solve this? I'm having the same problem.

  • Static addressing for Cisco IPSEC client

    Hey Guys,
    Is there a way for Cisco client based users to use static addresses instead of receivinga a dhcp address? This will be setup on a Cisco 2801 router. We usually just do dhcp but this customer is requesting static address for each user.
    Thanks
    Jimmy

    A scalable solution would be to configure a RADIUS server and provide the client their IP address via the frame-ip-address attribute. A hack could be to have a group defined on the EasyVPN server which is associated with an IP pool that has only one address available.

  • Aironet 1100 with Static Address

    Hi All
    I have taken over some access points from a company which were providing our wireless service and have not yet received the IP scheme information.
    I need to get onto one of the Aironet 1100 access points to see what the config etc is.
    I will only be able to take it down for a few hours, how to I actually connect to it.
    I am pretty sure it is configured with a static IP address which I do not know so is there anyway of connecting to it without using the Reset to Default method obviously!
    I have tried IPSU and a hub but no good.
    All replied gratefully received!!
    Darran

    Thanks for the replies guys but it hasnt solved my problem.
    Looks like it's not a static address after all
    I have done the following
    1. Plugged the AP into a switch on our network and connected to it wirelessly. I receive an IP the very same as if I was plugged into the switch directly and when I do an IPconfig I get the very same info as if I was plugged directly in. Still cannot find the AP IP Address though.
    2. Plugged the AP into a switch on our network and connected to the switch and did a show cdp neighbour, the access point does not show up, only other switches.
    3. Read the user guide and connected my laptop directly to the AP with a CAT 5 cable and gave the laptop an address of 10.0.0.2 . The AP does not seem to revert to 10.0.0.1 as suggested in the manual.
    4. I have tried to run the IPSU under all the above conditions, searching by the mac address of the AP but it has not received anything.
    ANy other ideas, Im at my wits end!!

  • Why won't my atv2 connect with a static address

    Hello,
    Suddenly, my ATV2 will not connect to the net with a static address.  I even did a restore hoping it would help.  When I log into the router,  i cannot see the atv2 unless I allow a dhcp address.  We're not talking rocket science:
    I have an airport extreme with the mac address entered on the allow list (which isnt relavent if the router can only see it through dhcp)
    192.169.0.25  preferred static address
    255.255.255.0 subnet
    192.168.0.1 dns
    192.168.0.1 router address
    i get the same results wired or wifi.
    Nothing has changed in my configurations but alas I turned on my ATV2 to discover it was not connecting to my network as before.
    Thanks for taking the time to read my post.

    192.169.0.25  preferred static address
    255.255.255.0 subnet
    192.168.0.1 dns
    192.168.0.1 router address
    i get the same results wired or wifi.
    Did you mean to write 192.169.0.25??
    The router is on 192.168.0.1, that would mean your ATV is on a different subnet to your router.
    ATV's IP address should be 192.168.0.25 instead, so they are on the same subnet.

  • Would my 400 AP`s benefit from a static address ?

    hi all
    just wondering if ap`s would benefit from a static address range
    presumably they collect the same address after lease expiry
    now i need to find 10 new addresses for new non wireless equipment n order for the server team to have a nice continous address range , if i reboot the ap`s and their existing 10 addresses are taken will they pick up new addresses in that range (given that there is still 10 spare)
    many thanks
    Megz

    thanks sabhasin,
    i kinda guessed this was the case. if i static the ap`s then at least there fixed with permanent addresses.
    is there any kind of risks accociated with ap`s on non statics i.e will a renewal create a blip or is it quicker than that.
    how is the layer 3 lwapp working in this way.
    great help so far btw ;)
    Megz

  • (Solved)--Static Address problem

    I set my static address according to the wiki an deverything bu it still refuses to work. I have to use dhcpcd eth0 everytime i boo to make my connection work. Here are a few files:
    rc.conf
    eth0="eth0 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255"
    INTERFACES=(eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    #   - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.1.1"
    ROUTES=(gateway)
    /etc/hosts
    <ip-address>    <hostname.domain.org>    <hostname>
    127.0.0.1    localhost.localdomain    localhost tux
    192.168.1.10    tux.domain.org    tux
    Anything wrong from this?
    Last edited by b0uncyfr0 (2010-03-10 07:52:51)

    tomk wrote:
    chakra-user, ifconfig commands are not persistent across a reboot. That's what config files are for.
    b0uncyfr0, "refuses to work" is vague. What doesn't work exactly? Paste your ifconfig and route output, and the contents of /etc/resolv.conf.
    Ahh well what I meant is that in addition to entries in /etc/rc.conf reg. static IP address and network in DAEMON Array, I did this ifconfig commands and had my eth0 up and running. I know it does not persist across reboots but somehow inspite of having the rc.conf stuff in, it did not wrk but when I ran the rc.conf + ifconfig it worked. Magic Mantra
    inaddition, I saw two lines of eth0="dhcp" in default rc.conf, I had done that also just incase it helps one or all of it together made my eth0 come up. I have now removed duplicate eth0="xxx" entries, removed NetworkManager and kept network and everything works. It is sad that these things must be working in stock install of Arch/Chakra but users have to struggle for such simple things.

  • IPv6 link-local address on point-to-point interface

    Hello,
    I'm a little bit confused. I know that there are two ways of assigning an IPv6 link-local address on interface. We can add it manually, or it is by default created automatically using modified EUI-64. But how is this address made when there is no MAC address on point-to-point link?
    Thanks.
    Martin

    Hello,
    sorry but I don't think that these reasons are reasonable. Why do they need to remember these addresses when are they used only on a link with internal processes? They cannot be used for management purposes, so I would say that it is easier for me to configure one loopback with global address at each router which would be easy to remember, announce it to IGP and it can be used for management, so as for BGP..and I don't need to care about all link local addresses I'm using in my network, which might contain hundreds of links..

  • RRAS 2012 - Cannot Change IPV4 From DHCP -- Static Address Pool

    Have set up RRAS/DA 2012 and it works but I need to change from using our DHCP server to a static address pool.    However, when I go to RRAS server properties & IPv4 tab the section to opt for DHCP/Static is dimmed out.
    Any suggestions to get around this annoyance so I can use static address pools for remote users?
    Thanks as always!

    Hi,
    Please try to use the following PowerSHell command and see how it works.
    Set-VpnIPAddressAssignment -IPAssignmentMethod ‘StaticPool’
    Set-VpnIPAddressAssignment
    http://technet.microsoft.com/en-us/library/hh918431.aspx
    Hope this helps.
    Jeremy Wu
    TechNet Community Support

  • [10.4.2] Unable to Remove Static Address Maps

    As the title says, I am unable to delete certain (pesky) static address maps using Server Admin (and I'm not sure where to delete them using the command line). Basically, here is what happens...select the static map to delete, delete it, hit save, and the record comes right back.
    Looking at the system.log reveals this...
    Dec 21 12:42:25 stusrv02 servermgrd: servermgr_dhcp:bootpd config:Error:Bad machine identifer 'BBS1 - A/V/2B21
    4565-871C-40A4-A180-BCE3296A6877', cannot remove
    ...so is anyone aware of a fix for this? Or a way to delete the offending entries from the command line?
    Dual G5 Xserve   Mac OS X (10.4.2)  
    15" PowerBook G4   Mac OS X (10.4.3)  

    Once again, I have resolved my issue on my own. Although this one took a bit longer, as documentation as to where Mac OS X Server stores information on DHCP static maps is not exactly abundant.
    The bottom line, when adding a DHCP static map using Server Admin, OS X Server stores it in NetInfo. Using the command line utility, dscl, you can easily navigate to the entries in NetInfo and delete them. dscl allows you to navigate exactly as you would in UNIX, using cd, ls, etc...
    From a command prompt, this is what you'd do...
    # dscl [return]
    cd NetInfo/Machines/ [return]
    ls [return]
    You will then see a listing of your static dhcp maps.
    delete "nameof_static_maprecord" [return]
    The above will delete your offending static map. Then simply typing, "quit" at the prompt and hitting return will quit you out of dscl.
    15" PowerBook G4   Mac OS X (10.4.3)  

Maybe you are looking for