TMDSICE3359: new DHCP request after cable unplug

Hi, 

Would you please share what software (Linux, RTOS) you are using and what version? Thank you.

Hi Ron,

I'm sorry my fault:

• PRU-ICSS-EthernetIP_Adapter_01.00.03.04
• bios_6_73_00_12
• ndk_3_40_01_01

Thank you and best regards,
Stefam

Hi Ron,

do you have any updates for this question?

Thank you and regards,
Stefan

Stefan,

I could see the symptom from my end too, let me check further to see how much effort it would take to re-enable DHCP.

Regards,
Garrett

Hi Stefan,

I have unlocked this thread.  Will you please share the latest status?

Thanks,
Brad

Hi Brad,

there are no news to this issue. Nothing changed as the above mentioned threads cover other topics and I worked other problems

Problem:

• Unplug+Plug of ethernet cable doesn't trigger a new DHCP request
• but if this happens ACD (IP conflict detection) has to work properly:
  • wait for the new IP
  • probe with the new IP

Best regards,
Stefan

Stefan,

The NC_setLinkHook() allows you to specify a callback function related to link events. I think we should utilize that capability to adjust the DHCP behavior.  One option could be to kill the DHCP client with ServiceKill() when the callback is called with arg=0 (link down).  Correspondingly you could restart the DHCP client with ServiceSpawn() when the callback is called with arg=1 (link up).

I'm inquiring internally to see if there are any more specific recommendations related to this implementation, but you might try experimenting along these lines while we're waiting for further guidance.

Best regards,
Brad

Stefan,

The NDK team pointed me to this post on restarting DHCP:

https://e2e.ti.com/support/legacy_forums/embedded/tirtos/f/355/p/439972/1580355#1580355

The only thing different about how I'm suggesting you do it is that you remove the client after a link-down event and that you (re-)add the client after a link-up event.

Best regards,
Brad