Frederico Silva

Hello, I'd appreciate those, - [ ] azure - Microsoft Azure - [ ] aws - Amazon Web Services - [ ] gcp - Google Cloud Platform Thanks in advance!

Hi @dikhan do you have any work done on this subject or any ideas how to approach it?

Thank you for pointing me in the right direction. I'll try to have a look on that later this week.

Thank you @Flarna It only happens in a specific network+os configuration it seems, need to dig deeper.

I had no time yet to try to understand what is going on, the problem still happens after updating to the latest: ``` ├── @opentelemetry/[email protected] ├── @opentelemetry/[email protected] ├── @opentelemetry/[email protected] ├──...

I can't reproduce right now. I'll close it and reopen when/if I have more information. Thank you

Using [debug](https://github.com/visionmedia/debug) allows logging when acts as a library. How do you like it?

Hi, any those storages will require _selectAddress to be an asynchronous. How are you thinking about exposing this to the user? (parameter on server config?)

Maybe, one could abstract those requirements in some kind of provider. That implements the selectAddress on an async fashion. That will handle storage/backend scenarios. Actual range/static/random may even be different...

Have a look on my fork, I've extracted the [_getLease ](https://github.com/fredericosilva/node-dhcp/blob/master/lib/dhcp.js#L209) to have a single place where _selectAddress is called. On [_selectAddress](https://github.com/fredericosilva/node-dhcp/blob/master/lib/dhcp.js#L229) I'm testing if a selectAddress exists on the...