Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 4116 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DHCP bug, static IP assigned to mac address handed to other device

RaveNet
Finding an ongoing bug in dhcp server where an IP is statically assigned to an existing device mac address and live on network is handed off to other devices which of course then won't connect due to IP conflict.  Still happens with 9.301 and is quite annoying


This thread was automatically locked due to age.
Parents
  • 0
    Not a bug.  Static Mappings are not reservations.  From the in-line help/admin guide:

    Note – To avoid an IP address clash between regularly assigned addresses from the DHCP pool and those statically mapped make sure that the latter are not in the scope of the DHCP pool. For example, a static mapping of 192.168.0.200 could result in two systems receiving the same IP address if the DHCP pool is 192.168.0.100 – 192.168.0.210.


    Assign static mapping addresses from outside the configured pool.
    __________________
    ACE v8/SCA v9.3

    ...still have a v5 install disk in a box somewhere.

    http://xkcd.com
    http://www.tedgoff.com/mb
    http://www.projectcartoon.com/cartoon/1
  • 0 in reply to Scott_Klassen
    Not a bug.  Static Mappings are not reservations.  From the in-line help/admin guide:



    Assign static mapping addresses from outside the configured pool.


    Should not have to assign from outside the pool.  The dhcp server should do two things before assigning an address
    1: ping to make sure it's not already live, which my understanding is sophos/Astaro UTM is supposed to do but is not
    2: check to make sure it's not pre-assigned/reserved in existing pool

    I've used other products, such as the Novell Netware DHCP server from 10+ years ago and it did not have this problem.  This is a bug.
Reply
  • 0 in reply to Scott_Klassen
    Not a bug.  Static Mappings are not reservations.  From the in-line help/admin guide:



    Assign static mapping addresses from outside the configured pool.


    Should not have to assign from outside the pool.  The dhcp server should do two things before assigning an address
    1: ping to make sure it's not already live, which my understanding is sophos/Astaro UTM is supposed to do but is not
    2: check to make sure it's not pre-assigned/reserved in existing pool

    I've used other products, such as the Novell Netware DHCP server from 10+ years ago and it did not have this problem.  This is a bug.
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?