Obtaining option 43 from DHCP

Angus

unread,

Oct 29, 2009, 12:58:29 PM10/29/09

to

I want my network application to be able to retrieve the option 43
string set by a DHCP server.

I have so far found DhcpRequestParams but it requires certain version
of Windows and I wanted to find something generic if possible. Is
there a standard way to get this information?

Paul Russell

unread,

Oct 29, 2009, 11:51:01 PM10/29/09

to

try rawsockets

--
thanks
.paul

/*++

Paul Russell

--*/

"Angus" <angus...@gmail.com> wrote in message
news:cf148b7c-7571-4f8d...@p35g2000yqh.googlegroups.com...

Angus

unread,

Oct 30, 2009, 9:45:18 AM10/30/09

to

On 30 Oct, 03:51, "Paul Russell" <spam_msftone_f...@hotmail.com>
wrote:

> try rawsockets
>
> --
> thanks
> .paul
>
> /*++
>
> Paul Russell
>
> --*/
>

> "Angus" <anguscom...@gmail.com> wrote in message

>
> news:cf148b7c-7571-4f8d...@p35g2000yqh.googlegroups.com...
>
>
>
> > I want my network application to be able to retrieve the option 43
> > string set by a DHCP server.
>
> > I have so far found DhcpRequestParams but it requires certain version
> > of Windows and I wanted to find something generic if possible. Is

> > there a standard way to get this information?- Hide quoted text -
>
> - Show quoted text -

This comment on wikipedia dissuades me:
When Microsoft released Windows XP in 2001 with raw socket support
implemented in the Winsock interface, the media criticized Microsoft
asserting that raw sockets are only of use to hackers to perform TCP
reset attacks. Three years after the Windows XP release, Microsoft
silently limited Winsock's raw socket support in a non-removable
hotfix and offered no further support or workarounds for applications
that used them.

Also see:
http://seclists.org/nmap-hackers/2005/4

Paul Russell

unread,

Oct 31, 2009, 8:00:51 PM10/31/09

to

Rawsockets are still supported.

Further, DhcpRegisterParamChange goes back to W2k so not sure your point /
statement on OS limitations.

That is generic enough for you no?

--
thanks
.paul

/*++

Paul Russell

--*/

"Angus" <angus...@gmail.com> wrote in message
news:73f78283-5332-4c7e...@o10g2000yqa.googlegroups.com...

Paul Russell

unread,

Oct 31, 2009, 10:23:20 PM10/31/09

to

Keep in mind, DHCP is UDP based and that is fully supported in RAW socket
mode.

You simply need to follow the general rules for addressing.

--
thanks
.paul

/*++

Paul Russell

--*/

"Paul Russell" <spam_msf...@hotmail.com> wrote in message
news:70D8F87F-5CA0-4B61...@microsoft.com...

Angus

unread,

Nov 3, 2009, 12:04:16 PM11/3/09

to

On 1 Nov, 02:23, "Paul Russell" <spam_msftone_f...@hotmail.com> wrote:
> Keep in mind, DHCP is UDP based and that is fully supported in RAW socket
> mode.
>
> You simply need to follow the general rules for addressing.
>
> --
> thanks
> .paul
>
> /*++
>
> Paul Russell
>
> --*/
>

> "Paul Russell" <spam_msftone_f...@hotmail.com> wrote in message

>
> news:70D8F87F-5CA0-4B61...@microsoft.com...
>
> > Rawsockets are still supported.
>
> > Further, DhcpRegisterParamChange goes back to W2k so not sure your point /
> > statement on OS limitations.
>
> > That is generic enough for you no?
>
> > --
> > thanks
> > .paul
>
> > /*++
>
> > Paul Russell
>
> > --*/
>

Any pointers on how to get started? Do I need to make a request to
the DHCP Server? Reason I ask is because by the time my program runs,
the computer will have already completed the startup IP address (DHCP)
process.

So do I need to send another request to the DHCP server for
information? Any pointers would be most appreciated.