|
Well, unfortunately, I couldn't get any answer on the msdn forums, so
I'll give it a shot here.
Real question at the bottom.
---------------------------------------------------------------------------------------------
What new functionality is added to this feature in Windows XP Service
Pack 2?
Restricted traffic over raw sockets
Detailed description
A very small number of Windows applications make use of raw IP sockets,
which provide an industry-standard way for applications to create
TCP/IP packets with fewer integrity and security checks by the TCP/IP
stack. The Windows implementation of TCP/IP still supports receiving
traffic on raw IP sockets. However, the ability to send traffic over
raw sockets has been restricted in two ways:
· TCP data cannot be sent over raw sockets.
· UDP datagrams with invalid source addresses cannot be sent over
raw sockets. The IP source address for any outgoing UDP datagram must
exist on a network interface or the datagram is dropped.
---------------------------------------------------------------------------------------------
I have built a simulation of a MultiFunctionDisplay(MFD) in C# and have
been very impressed with the results. The only issue I am having, is
that the actual hardware sends out UDP packets on 2 network interfaces.
The issue is that all the packets have a source address of the 1st
interface. I would like to do this in the simulator as well. I have
read the above description and would just like to make sure there is no
ambiguity. Is it that the source address must be that of the interface
it is being sent from or an interface on the host machine that is
sending it.
If what I would like to do is not possible, that is disappointing.
Does anyone know of any possible work arounds?
Thanks.
| 
