Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 6 subscribers
  • Views 2892 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

Static entry bug?

Dave Curr

You have a static entry configured in the DHCP scope of subnet A. You move the client to subnet B, and make it static from the 'DHCP leases' tab using the 'use an existing host' option. The outcome is that the host record now contains the IP from subnet B, but when the DHCP OFFER is sent to the client, the IP address is correct, but the default gateway is from the network configured on the original static entry, subnet A. As such, the client has a DG it can't reach. The behaviour is consistent. 

if you create a new host for management via DHCP, you can't save it if the address is not in the chosen DHCP range - you get (e.g.) "IP 192.168.1.150 is not in network 192.168.2.0/24 of the chosen interface."

is this intended behaviour or a bug?



This thread was automatically locked due to age.
Parents
  • 0

    Yes, That's a bug within the GUI.

    If you try to add the new IP/MAC to existing host, the IP for this host is changed, but not the DHCP Server/Scope/Subnet.

    If you open the network object afterwards, you are unable to save until you correct this error.

     


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • 0 in reply to dirkkotte

    Thanks - does this get reported to Sophos by some mechanism?

  • 0 in reply to Dave Curr

    Someone has to open a support-ticket.

    This is possible for a customer with platinum-support or a partner.

    This Needs a lot of time (money).

    Or we have luck and a sophos staff member will read this post and solve this problem for us.

     

     


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • 0 in reply to dirkkotte

    Actually, that makes sense now. The USB installer bug (where you have to manually mount the USB drive before installing) is at least 5 years old (it bit me the first time I installed). I've found another bug where when I edit any of my wireless networks, it automatically changes everything back to the very first wireless network i created (name, SSID and password) and wipes out the one I was editing. The one it changes them back to doesn't actually exist any more either.

    This begs the question - if they aren't using us as beta testers, what is the value to Sophos in giving UTM away for free to home users? 

Reply
  • 0 in reply to dirkkotte

    Actually, that makes sense now. The USB installer bug (where you have to manually mount the USB drive before installing) is at least 5 years old (it bit me the first time I installed). I've found another bug where when I edit any of my wireless networks, it automatically changes everything back to the very first wireless network i created (name, SSID and password) and wipes out the one I was editing. The one it changes them back to doesn't actually exist any more either.

    This begs the question - if they aren't using us as beta testers, what is the value to Sophos in giving UTM away for free to home users? 

Children
No Data
Unfiltered HTML