Multiple instances of dhcp6c causing no ipv6 address



  • Sometimes when my dhcp lease is renewed or my modem power cycles or I need to reload an interface for some reason I end up with a duplicate dhcp6c process. This results in my WAN interface not getting an ipv6 address until I ssh into the router and kill all dhcp6c processes, then trigger dhcp to start over on my WAN interface.

    While not causing me down time, its starting to annoy me that this is becoming my daily ritual. Is there any way to prevent the duplicate dhcp6c processes? It seems like the old process is not getting killed correctly.

    EDIT - Should note I am using the 2.3.4-RELEASE build on an sg-4860



  • @jassmith:

    Sometimes when my dhcp lease is renewed or my modem power cycles or I need to reload an interface for some reason I end up with a duplicate dhcp6c process. This results in my WAN interface not getting an ipv6 address until I ssh into the router and kill all dhcp6c processes, then trigger dhcp to start over on my WAN interface.

    While not causing me down time, its starting to annoy me that this is becoming my daily ritual. Is there any way to prevent the duplicate dhcp6c processes? It seems like the old process is not getting killed correctly.

    EDIT - Should note I am using the 2.3.4-RELEASE build on an sg-4860

    Is this a production system? If it's not critical that it's stable release code, you might want to consider trying 2.4 beta. There are differences in how the processes are managed and you might find it behaves better.



  • Unfortunately yes this is a production system. I have enabled Reject Leases From: 192.168.100.1 as my modem (surfboard) apparently does that when it loses connection. I haven't seen it happen in a couple days, but we're still in the 4 day window.


Log in to reply