Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 17 replies
  • Subscribers 31 subscribers
  • Views 34397 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

Not working auto-renew at DHCP

FoW

In a test lab, I was trying change ISP (Disconnect ISP1 cable and connect ISP2 cable).

It does not working. XG Firewall does not receive new IP. Need a manual edit for interface.

Why don't you to provide automatic renew?

test ver. is XG Firewall 16.01.1



This thread was automatically locked due to age.
  • 0

    I have this issue too on XG105 (SFOS 16.05.5 MR-5)

    It is surprisingly simple to replicate and it is frustrating it still exists.

  • 0 in reply to Nicholas Wilson

    Hi Nicholas , 

    Could you raise the service request for the same with support@sophos.com and please share with us the Case# .

  • +1

    Hi, 

     

    I try with the version 17.1.1 MR-1 and it is still not fix... 

     

    I got this answer :

     

    As to the RFC, I am not at all suggesting the other vendors are not following RFC; in all likelyhood, they are following it just fine. One of the key words in the RFC is "SHOULD":
    https://www.ietf.org/rfc/rfc2131.txt

    3.7 When clients should use DHCP

       A client SHOULD use DHCP to reacquire or verify its IP address and
       network parameters whenever the local network parameters may have
       changed; e.g., at system boot time or after a disconnection from the
       local network, as the local network configuration may change without
       the client's or user's knowledge.


    SHOULD doesn't necessarily mean MUST. So where some vendors may choose to do so, others don't necessarily have to.

    As to whether or not this is a bug, our DEV team has confirmed that this behaviour is expected, and by design; there's no avenue for Support to push back on them to fix this (since it's working as designed, there's nothing to 'fix').

  • 0 in reply to Maxime Cote Dube

    I have two ISPs services and both fail to automatically renew the IP address when using XG, but work in the UTM.

    Also the XG interfaces fail to renew the IPv6 address and lockup or fail to pass traffic until the interface is opened and saved.

    This issue has been reported a number of times for each release of XG. Very frustrating when you an external link failure and restoration.

    Ian

  • 0

    Due to this policy, the sum of our business we missed in a few years will be 100K USD.

    This is not rare case. ISP of the South Korea provide multiple DHCP range for personal customer. And even personal customers receive multiple public IP streams from multiple network pools. Because in South Korea, personal customers receive gigabit internet at a low cost with a fiber-optic modem.

  • +1

    I tried the auto-renew DHCP on the last version 17.5.1 and it is still not working.

     

    No choice, I have to choose another product and I decided to go with Meraki for my 26 warehouses. 

  • 0 in reply to Maxime Cote Dube

    Even if you have WAN link manager enabled and the link fails the auto-renew does not work. Maybe someone in the marketing team should tell the DEV team to be adventurous and ignore should and convert it to MUST.

    Now if the argument is based on definitions why does so much of the XG ignore definitions. Roll on v18, maybe this will be improved anymore reliable?

    Ian

    Of course threes a further issue and you cannot do remote management or access to reset the interface. Not a very well thought out argument and support should be pushing dev to fix this failure.