DHCP beginning address problem.

Hi guys,
I cannot understand how to configure my TC. I put exactly the same network settings as they were in the Airport Express to share the Internet connection. Everything works fine except the internet itself. The problem as I see it is that dhcp beginning address cannot be set far away from the static IP. In my case, the static IP is 213.170.70.** and I only can change these ** last figures in the dhcp range.
But this conflicts with my provider and I have no internet while the TC itself works fine. If I set "share the only address" it doesn't help either.
Anybody can help?
Many thanks in advance.

None really. These are the three IP Address ranges available for Private Networks. The Internet Engineering Task Force (IETF) has directed the Internet Assigned Numbers Authority (IANA) to reserve these IPv4 address ranges for private networks. This has been published in RFC 1918.
More info: Wikipedia: Private network

Similar Messages

  • DHCP beginning address

    So when I'm assigning DHCP addresses using Apple's airport, I have the option of addresses beginning 10.0.x.x, 172.16.x.x., or 192.168.x.x. What are the differences between these three options? Or are there no essential differences?

    None really. These are the three IP Address ranges available for Private Networks. The Internet Engineering Task Force (IETF) has directed the Internet Assigned Numbers Authority (IANA) to reserve these IPv4 address ranges for private networks. This has been published in RFC 1918.
    More info: Wikipedia: Private network

  • RSV4000 DHCP Gateway address problem

    I have an RSV4000 which I'm using as a gateway. I changed the default 192.168.1.0/24 network to 10.255.255.0/24 and configured the DHCP address pool to use 64 host addresses starting at 10.255.255.64
    Every so often users on VLAN 1 get a gateway IP address of 192.168.1.1 even though they received a DHCP address of 10.255.255.64, 65, 66, etc.
    I ran a packet capture and the RSV4000 is actually giving out the wrong gateway address.
    I have to power cycle the RSV4000 and it works until some random point in time, then starts giving out the wrong gateway address again.
    Is Cisco going to fix this?
    I'm running version 1.3.2.0 and I do not have the V4 model so I can't run v2.0.0.3

    Hey mdoldan,
    Were you the one that upgraded the firmware of 1.3.2.0 on the router or did you receive it like that.
    This is a very odd case, where it is giving out ip address on the default lan even though you changed it.
    Have you tried reflashing the firmware, factory resetting the router and reloading the configurations back to it.
    I would try that and see if the problem persist.

  • DHCP Beginning address wrong?

    I am trying to setup Airport Extreme at our church.  The wireless devices are good for a day.  Then they can not hook up.  I have tried to assign dhcp address as static.  It is not working.

    None really. These are the three IP Address ranges available for Private Networks. The Internet Engineering Task Force (IETF) has directed the Internet Assigned Numbers Authority (IANA) to reserve these IPv4 address ranges for private networks. This has been published in RFC 1918.
    More info: Wikipedia: Private network

  • IP Address Problem

    I have a PowerMac G4 Quicksilver 2002 running OSX 10.3.9, with Verizon DSL service. I suddenly have a very strange problem with my IP Address and some erratic behavior. When the internet connection works, my network settings are:
    Location: Verizon DSL
    Show: Built-in Ethernet
    for TCP/IP
    Configure IPv4: Using DHCP
    IP Address: 71.xxx.xxx.xx (a series of automatically assigned numbers)
    Subnet: 255.xxx.xxx.x (a series of automatically assigned numbers)
    Router: 71.xxx.xxx.x (a series of automatically assigned numbers)
    Recently, without changing any of the settings, I get an IP Address something like 169.xxx.xxx.xx. This IP Address does not work. The tech people at Verizon Online said that the line from my DSL modem to their server was fine, but that the automatically assigned IP Address should be the 71.xxx.xxx.xx number.
    There is no pattern to this error. Originally the connection would work in the morning and begin the error IP Address about 4:00 pm. Today when I booted, the connection was out and the 169.xxx showed in the network window. I used the internal Apple modem and a secondary dial-up account and could connect to the internet. After I disconnected the dial-up, the Ethernet connection worked, showing the correct IP Address of the 71.xxx numbers.
    Does anyone have any ideas what's going on here. Thanks.
    Quicksilver G4   Mac OS X (10.3.9)  
    Quicksilver G4   Mac OS X (10.3.9)  

    I seem to have this (or a very similar) problem repeatedly after updates. I use a wireless connection to the internet when at work, which mostly is trouble free. However following the last two itunes/quicktime updates and now also following the latest security update (Security Update 2006-005 (10.3.9)) which deals with the airport protocol, I have had this problem.
    Where the airport managed to connect and obtain a valid IP address before, with exactly the same settings the computer uses a 'self-assigned' IP address following the update. As you observe the self assigned IP address does not enable you to connect.
    However following the itunes/quicktime updates the problem resolved itself after a few days ( a few hours the second time) and did not reoccur. I have only just encountered the problem following the security update and hope it also resolves itself soon.
    Any advice on how to avoid this altogether would be appreciated.
    15" powerbook G4   Mac OS X (10.3.9)  

  • WTR54GS Fails to obtain a DHCP IP Address from Upstream

    Greetings!
    I had effectively given-up on Linksys Router WTR54GS, as it was advertised that it could be plugged into a pre-existing network (friends home network, a hotel room ethernet jack, etc), but sadly the WTR54GS itself is incapable of obtaining a DHCP IP Address from an upstream DHCP server (like the hotel, etc).
    I have tried repeatedly to work with Linksys Support but everyone wants to blame the upstream router, suggesting that I change it's configuration to "Bridged-mode".  Yeah, right.  Like I'm going to walk down to the hotel lobby main desk and tell them that they need to place THEIR network in bridged mode just so my WTR54GS will work.   I was willing to believe that the first router (version 2.0) that I was sent was defective, and let Tech Support talk me into returning it to my vendor and seeking a replacement. 
    I receieved the replacement (this time version 1.0) and had EXACTLY the same problem.  I returned that one as well (marked defective) after talking with Ellen in Linksys 2nd Level Technical Support.  She promised this would be referred to the Linksys Engineering group for further study.  This was 4+ months ago. 
    I would like to buy another one, but am hesitant to buy because I just do not trust Linksys Technical Support anymore.   Can someone please confirm that Linksys Engineering is aware of this problem, acknowledges its existence, and has resolved (or is at least working on resolving) this problem?
    -Elrendhel
    Forum Administrator, Product Reviewer, & Moderator at MobilitySite,
    Forum Admin, Lead Tech Support Mgr & Moderator at GPS Tuner,
    Moderator at Microsoft's Windows Mobile Owners Circle forums.

    So you have connected WTR through the correct (blue) port to the internet connection?
    You have configured the WTR for wired internet connection type?
    You have configured the WTR for DHCP?
    What does the WTR say on the Status page?
    Have you tested the WTR inside your home network?

  • Clients not receiving DHCP IP address from HREAP centrally Switched Guest SSID

    Hi All,
    I am facing a problem in a newly deployed branch site where the Clients are not receiving DHCP IP address from a centrally switched Guest SSID. I see the client status is associated but the policy manager state is in DHCP_REQD.
    The dhcp pool is configured on the controller itself. The local guest clients are able to get DHCP and all works fine, the issue is only with the clients in the remote site. The Hreap APs are in connected mode. Could you please suggest what could be the problem. Below is the out of the debug client.
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Adding mobile on LWAPP AP 3c:ce:73:6d:37:00(1)
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Reassociation received from mobile on AP 3c:ce:73:6d:37:00
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'Guest-ACL' (ACL ID 0) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying site-specific IPv6 override for station 10:40:f3:91:7e:24 - vapId 17, site 'APG-MONZA', interface 'vlan_81'
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying IPv6 Interface Policy for station 10:40:f3:91:7e:24 - vlan 81, interface id 13, interface 'vlan_81'
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying site-specific override for station 10:40:f3:91:7e:24 - vapId 17, site 'APG-MONZA', interface 'vlan_81'
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 STA - rates (8): 140 18 152 36 176 72 96 108 0 0 0 0 0 0 0 0
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Initializing policy
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state AUTHCHECK (2)
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 AUTHCHECK (2) Change state to L2AUTHCOMPLETE (4) last state L2AUTHCOMPLETE (4)
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 3c:ce:73:6d:37:00 vapId 17 apVapId 1
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last state DHCP_REQD (7)
    *apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 apfMsAssoStateInc
    *apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 apfPemAddUser2 (apf_policy.c:222) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Idle to Associated
    *apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station:  (callerId: 49) in 28800 seconds
    *apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 Sending Assoc Response to station on BSSID 3c:ce:73:6d:37:00 (status 0) ApVapId 1 Slot 1
    *apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 apfProcessAssocReq (apf_80211.c:4672) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Associated to Associated
    *apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) State Update from Mobility-Incomplete to Mobility-Complete, mobility role=Local, client state=APF_MS_STATE_ASSOCIATED
    *apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) pemAdvanceState2 4183, Adding TMP rule
    *apfReceiveTask: May 24 11:35:53.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Adding Fast Path rule
      type = Airespace AP - Learn IP address
      on AP 3c:ce:73:6d:37:00, slot 1, interface = 13, QOS = 3
      ACL Id = 255, Jumbo F
    *apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 7006  IPv6 Vlan = 81, IPv6 intf id = 13
    *apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (ACL ID 255)
    *pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
    *pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 Sent an XID frame
    *apfMsConnTask_3: May 24 13:26:49.401: 10:40:f3:91:7e:24 Updating AID for REAP AP Client 3c:ce:73:6d:37:00 - AID ===> 1
    *apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) DHCP Policy timeout
    *apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.
    *apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station:  (callerId: 12) in 10 seconds
    *osapiBsnTimer: May 24 13:28:59.315: 10:40:f3:91:7e:24 apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
    *apfReceiveTask: May 24 13:28:59.315: 10:40:f3:91:7e:24 apfMsExpireMobileStation (apf_ms.c:4897) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Associated to Disassociated
    *apfReceiveTask: May 24 13:28:59.315: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station:  (callerId: 45) in 10 seconds
    *osapiBsnTimer: May 24 13:29:09.315: 10:40:f3:91:7e:24 apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
    *apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 Sent Deauthenticate to mobile on BSSID 3c:ce:73:6d:37:00 slot 1(caller apf_ms.c:4981)
    *apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 apfMsAssoStateDec
    *apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 apfMsExpireMobileStation (apf_ms.c:5018) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Disassociated to Idle
    *apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Deleted mobile LWAPP rule on AP [3c:ce:73:6d:37:00]
    *apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 Deleting mobile on AP 3c:ce:73:6d:37:00(1)
    *pemReceiveTask: May 24 13:29:09.317: 10:40:f3:91:7e:24 0.0.0.0 Removed NPU entry.

    #does the client at the remote site roams between AP that connects to different WLC?
    #type 9 is not good.
    *pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
    #Does your dhcp server getting hits.
    #Also, get debug dhcp message & packet.
    #Dhcp server is not responding.
    *apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) DHCP Policy timeout
    *apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.

  • Releasing unused DHCP IP addresses in OSX Server 10.4

    In OSX Server 10.4.11 is there any way to release unused DHCP client addresses in the Server Admin app? We have 73 clients showing (and only 30 on the network) because various computers have been added to the network and removed/reinstalled at various times, and that means we're running out of available addresses in our little chunk of the subnet.
    We've previously set a longish lease time on DHCP addresses because we've had problems in the past with sleeping Macs being woken up and having clashing IPs with other Macs that have had that IP reassigned to them, but it means that we do have a long list of unused DHCP clients.
    Does Server 10.5/10.6 allow the release of DHCP addresses from the admin app (oh, for a right-click delete!), or is that just not possible in the DHCP protocol (NB I'm trying to release unused IP addresses, not asking live clients to rescind their IP address).

    It's not legal within the DHCP protocol - as far as the server is concerned, that IP address has been handed to the client and should be reserved for that client until the lease expires. The server has no way of knowing whether the client is still using the address.
    You may be able to break the rules, though - the server stores the DHCP leases in /var/db/dhcpd_leases, so you should be able to stop the DHCP server, edit the file to remove the unnecessary leases, then start the server back up. No guarantees, tho'.

  • DHCP provided address time limits

    Hi there,
    I have been searching for any way to limit DHCP supplied addresses in regards to time usage. I am looking to restrict certain addresses, specified via MAC, to only be able to access my network during specific times of the day.
    For example, I would like for address 192.168.0.28 to only be able to access the network (and the internet of course) between the hours of 9 a.m. to 5 p.m.
    If this cannot be done by OSX 10.5 Server, is there any affordable software or hardware solution out there that anyone knows of which can perform this function?

    I removed the Belkin router and set up the Airport Time Capsule as the DHCP server. No problems since.

  • How to set up both static and DHCP assigned addresses on an AirPort Extreme

    I recently bought an AirPort Extreme to replace my failed Cisco/Linksys router.
    I am having trouble figuring out how I can configure the Extreme to support the already static IP addresses on my network as well as assign IP addresses via DHCP to a few devices where static IPs are not supported, i.e., work laptop.
    Additionally, when DHCP is turned on, are my only options the 10.0, 172.16, and 192.168? What if I am running something like 10.10 or 172.30?
    I am far from green when setting up computer networks, but this AirPort Extreme is making me pull my hair out.
    BTW, I have access to a number of computers running a number of OSes including Windows XP, 7, and 8, as well as Mac OS X Snow Leopard and Mountain Lion.
    The Mountain Lion or Windows 7 machine would be the preferred ones to configure the Extreme. I already have the AirPort Utility software running on them.
    Any help would be appreciated.

    I have found the 'DHCP Reservations' option on the AirPort Extreme to be buggy.  I seem to remember it causing IP conflicts for some reason.  I think what I remember is that if the computer with the reservation was off, and the DHCP server then handed out that IP to another DHCP client, then there would be a conflict when the reserved IP computer was turned back on.  Maybe it was an issue in ealier versions of the AE or OS X as the case may be, and maybe it's been corrected, but I've never bothered using it agian since the method I describe below has always worked without fail.  Also, I'm guessing DHCP Reservations would work fine if one manually enters IPs outside of the DHCP range but in the AE 'DHCP Reservation Setup Assistant' the IP options provided are within the DHCP range which to me makes no sense and increases the potential for IP conflicts.
    Here's what I do to setup a mixed environment of static and dynamic IPs on my network.  It works like a charm and does not require the DHCP server (beyond the distribution of dynamic IPs to hosts using DHCP).
    For machines on my network that are accepting services from the public network, I set them up with static IPs using the 'Manually' option (System Preferences/Network/Ethernet/Configure IPv4).  The settings for 'Router' IP address and 'DNS Server' IP address should both be set with your gateway/router LAN IP).  Use an IP address below or above the DHCP range of adresses (in AE/Internet/DHCP/DHCP Beginning & Ending Address).
    i.e. if my subnet is 10.0.1.1 and my DHCP range is 10.0.1.100 to 10.0.1.150, you could set the static IPs on your local hosts as 10.0.1.x where x = any number from 2 - 99 or from 151 - 200 as an example.
    All other machines and devices that do not require static routing are setup as DHCP clients and get a dynamic IP from the AE.  To me it's a simpler setup though it might take a little extra time to setup initially.
    John

  • Cisco E1000 wont connect to internet anymore - not getting DHCP ip address from Comcast modem

    Very strange issue...
    I have Comcast HSI and have been using my Cisco (Linksys) E1000 for about 3 years now. Bought it as a refurb.
    My issue is that the E1000 is NOT receiving the DHCP info from my Comast modem.
    The internet works when my laptop is directly attached to the modem; but when connecting the modem internet port
    to the E1000 internet port it is NOT grabbing my ISP DHCP ip address thus no clients can broswe 'wired or wireless'.
    I even updated the firmware and am starting to think its time to get a 'BRAND NEW' router as this makes NO SENSE!
    I cannot release/renew as i have NO ip address to release.  I have even tried to configure the E1000 as a static 
    using the ipconfig/all from when the laptop and modem was connected. Comcast says they see nothing on their end. 
    I also factory defaulted the router and redid the config to no avail. 
    Any help would be appreciated.
    Solved!
    Go to Solution.

    You need to enable MAC address clone on the router to recognize the connection from your cable modem. The link below would tell you how to configure the router to work with a cable connection and how to do MAC address clone.
    Setting up a Linksys router with Cable Internet service

  • 802.1x and DHCP assigned addresses

    I've done a lot of reading on this but I am still confused. I'm not a Microsoft guru so I don't really know waht is going on with login scripts, or cached user/pass.
    Scenario 1
    ==========
    I have 802.1x implemented and Joe the contractor comes into the office and plugs in his laptop. He is a guest. I allow guests to have access to a guest VLAN. How can Joe automatically get an IP address, or does he have to do ipconfig /renew?
    Scenario 2
    ==========
    What is the behind the scenes process that takes place for my corporate users that login to a domain....how do they get DHCP assigned addresses?
    Thanks

    I assume from what you have written 'Joe' doesn't have an 802.1x supplicant on his PC? Therefore the switchport eapol frames are ignored by the PC and after a timeout the port is placed in the guest vlan. You need to make sure DHCP is enabled for the guest vlan - either add the appropriate entried to the protecting ACL or add a scope on the router? Depending on the timeouts you may have some delay issues here; I would test this before you roll it out.
    For clients with 802.1x supplicants what happens is the PC effectively thinks it is disconnected from the network until the supplicant has authenticated. Once it has authenticated the PC thinks the network adapter is then connected and it will attempt to lease an IP address by broadcasting a DHCP request.
    There are however a few 802.1x supplicants and I am not sure how they all integrate with the host O/S. I know the built-in Microsoft one operates as I have described.
    HTH
    Andy

  • Incorrect DHCP server address to wireless client

    Guys,
    I have deployed a centralized wireless architecture with 2 x wisms in each of our DCs. I just noticed the clients are receiving incorrect DHCP server address, please note there is no issue with connectivity, i just want to know why incorrect DHCP server address is handed out to the clients.
    The DHCP server address received is apparently virtual interface address of the WiSM. i am running WiSM firmware 7.0.116.0
    Any information is appreciated.
    Cheers
    AP

    DHCP proxy is pretty usless in my mind. It was something that lingered from the old airespace days. In fact if you ask many cisco se's they will tell you they wished they didnt default to proxy. Also, if you ever use cisco ISE, you will need to disable proxy, becuase you will need to configure a helper pointing to the ISE box for DHCP finger printing.
    Steve points out, if you use the WLC as a DHCP server it is a requirement to have it on. But we all agree here on CSC (Steve, Leo, Blake, myslef), that the DHCP server on a WLC is not robust and is problematic at times.

  • DHCP Server Address Range

    Hi there,
    I was wondering if there was a way to change the built-in DHCP server address range from 192.168.1.x to, say, 192.168.0.x?  For example, when you change the router IP from 192.168.1.1 to 192.168.0.1.  I noticed that when you commit such a change, the DHCP range does not update accordingly.  Any ideas?
    Thank you,
    Paul
    Solved!
    Go to Solution.

    Your DHCP server range should update automatically to the 192.168.0.x  subnet when you change your "Local IP address" to 192.168.0.1.   Be sure to use a computer that is wired to your router when you do this.  Also, be sure to click on "Save Settings", then wait (3 to 60 seconds) for the screen to refresh.  You will likely be disconnected from the router when you do this.  Do not worry about this.  Power down the router and your computer.
    Next, wait 30 seconds, then reboot router and computer.  Your Local IP address and the DHCP server range should now have the same subnet.

  • DHCP exclude address range option config on Instant 2.0

    Q:  DHCP exclude address range option config on Instant 2.0
    A: ​This article applies to Instant 4.2 and above.
    Before 4.2, Use exclude-address as a range option was not available.
    Since IAP is getting used as an Edge device, the features needs to be in compliance with industry standard. 
    From 4.2 onwards, IAP local DHCP server will support exclude IP address as a range.
    With this feature we are supporting the following
    A. exclude-address ip1
    B. exclude-address ip1 ip2
    Show dhcps command will show the excluded range and available range

    I found this on TCPIPGUIDE.com that supports my findings.
    "One difference between BOOTP and DHCP is that certain communications from the client to the server are unicast. The most noticeable instance of this is when a client tries to renew its lease with a specific DHCP server. Since it sends this request unicast, it can go to a DHCP server on a different network using conventional IP routing, and the relay agent does not need to be involved."

Maybe you are looking for