UDPRecv Only sees RAW packets with UDPBind

[MrBeatnik <palebluecreations@…>]

Hi,

The UDP Functions seem to only look at raw packets.
Under certain circumstances, the raw packets are not picked up, however if listening on NDIS bindings, packets can be received. It would be nice if we could specifiy what to bind to when listening with UDPBind().

In particular, I am attempting to listen for a packet in Windows PE (PE3 - Windows 7). I can't find anywhere that says that PE isn't supported? However, it would still be a nice feature in other versions of Windows.

I have two autoit scripts.
One sends packets, the other listens.
If both scripts are run on Windows XP machines, the data is received. However if the listening script is run on Windows PE, then it is never received by the script.

On the Windows PE machine:
If I run wireshark on the port, I can see the data being received.
If I run a tool in PE and switch to NDIS sniffing (IPTools - ​http://erwan.l.free.fr/), I can see the data being received.

This seems to be a limitation in the UDP functions where it only binds to RAW and allows us no choice? NOTE This does not affect sending via UDP - Sending in PE works fine, it is just receive that has the problem.

[MrBeatnik <palebluecreations@…>]

This is the receiving script - listening for UDP packets.

[MrBeatnik <palebluecreations@…>]

This is the sending script. Need to change IP address.

[MrBeatnik <palebluecreations@…>]

The debug information shows:
Environment = 3.3.0.0 Compiled under WIN_VISTA X86

[MrBeatnik <palebluecreations@…>]

This problem also shows with 3.3.1.1

[Nutster]

Windows PE has only some drivers, including network drivers, enabled. To prevent Windows PE from being used as a server, most listeners, including UDF, are not enabled under Windows PE.

See ​http://technet.microsoft.com/en-us/library/cc766093(WS.10).aspx for information.

So in summary, this is an operating system limitation, not an AutoIt limitation, so we can't change this behaviour.