I would love to have a Native LabVIEW DHCP server

[danny_t]

Working in the telecoms industry at several different companies and for many products I need to be able to provide a test station with  DHCP functionalitly in order to be able to communicate with units under test. I have seen a posts on LAVA and the NI forurms that say I am not alone in this.

Currently I achieve this using third part products, typically with command line call using the system_exe. I mainly use tftpd, but it would be nice to have such functionality build into LabVIEW.

cheers

Dannyt

[PhillipBrooks]

I started looking at writing a server serveral years ago, but lack of time and availability of alternatives resulted in little more than learning about the protocol (worth knowing about).

[Darren]

Any idea that has received less than 8 kudos within 8 years after posting will be automatically declined.

[பரத்_குமார்(bharathkumar)]

Hello,

I am not able to kudo it. I needed this, consider it for future programmers. Now any workaround for DHCP Sere in LabVIEW?

[wiebe@CARYA]

You can't kudo a declined idea.

It seems to me this should be in a library.

There's nothing NI has to do to make this happen.

From what I'm reading (here for instance), it shouldn't be that hard to get a LabVIEW DHCP server up and running. A complete feature set might not be that easy but I've seen more intimidating specs.

[பரத்_குமார்(bharathkumar)]

Hello wiebe,

Thanks for the information provided, I read the DHCP Protocol Link.

I am having difficulty understanding on one thing, How is the message format sent/Recieved.JSON String or Byte Array of unsingened int with length. Please understand the client side program on hardware is not available.

[wiebe@CARYA]

>How is the message format sent/Recieved.JSON String or Byte Array of unsingened int with length.

It's not clear to me what you mean.

Also, I didn't read the spec.

Also, maybe post this on the normal forum. It's off topic here.

[பரத்_குமார்(bharathkumar)]

Hello Weibe,

The message packet has following fields for all, DHCP DISCOVER,DHCP OFFER,DHCPRQUEST,DHCP ACKNOWLEDGE Messages.

Like hytpe means hardware type.

My only doubt is, will followig message packet be framed as JSON STRING or unsigned 8 bit integer array as dhown in code proect example.

 0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     op (1)    |   htype (1)   |   hlen (1)    |   hops (1)    |
   +---------------+---------------+---------------+---------------+
   |                            xid (4)                            |
   +-------------------------------+-------------------------------+
   |           secs (2)            |           flags (2)           |
   +-------------------------------+-------------------------------+
   |                          ciaddr  (4)                          |
   +---------------------------------------------------------------+
   |                          yiaddr  (4)                          |
   +---------------------------------------------------------------+
   |                          siaddr  (4)                          |
   +---------------------------------------------------------------+
   |                          giaddr  (4)                          |
   +---------------------------------------------------------------+
   |                                                               |
   |                          chaddr  (16)                         |
   |                                                               |
   |                                                               |
   +---------------------------------------------------------------+
   |                                                               |
   |                          sname   (64)                         |
   +---------------------------------------------------------------+
   |                                                               |
   |                          file    (128)                        |
   +---------------------------------------------------------------+
   |                                                               |
   |                          options (variable)                   |
   +---------------------------------------------------------------+

for all d

[wiebe@CARYA]

That is a binary data structure. So, byte array.

Note that it doesn't make a difference if the array is U8 or I8. It's flattened data. Might as well use a string, as a string is required by the TCP\UPD send functions anyway.