- TDI Client and the transports (v4 and v6) raw devices
- Posted by Florent on September 12th, 2005
When using \device\RawIp6\[#protocol] are there any special extended
attributes to
specify to be able to open it with protocol 4 (v4 in v6) or 6 (v6 in v6)?
Whenever I try protocol 4 or 41, it fails with NT_STATUS 0xc0000010 (invalid
device request), while a random protocol number like 31 opens it.
255 also opens it, but what exactly does it mean to use protocol 255, which
is
defined in the MSIPv6 research stack as RAW_PROTOCOL? I can't see to be able
to
use TdiBuildSendDatagram on a transport address initialized with protocol
255.
If anyone can shed some light on this, I can't find any documentation.
Thanks
Similar Posts
- Can security devices harm DVDs and electronic devices? (Video & DVD) by curious@nospam.com
- Watchguard / Safenet Client and Cisco VPN Client Compatible? (Routers) by Patrick Dunnigan
- Typical client-to-client throughput through Linksys WAG54G router ? (Networking) by Lorenzo Sandini
- Re: Scribe Email Client 1.87-test3 Development - A cross platformemail client. (Software & Applications) by Mike
- Windows server, Unix client, connection refused on client connect. (Programming) by Dan C

