Re: Raw TCP/IP library?
- From: "Peter Duniho" <NpOeStPeAdM@xxxxxxxxxxxxxxxx>
- Date: Fri, 17 Nov 2006 23:54:44 -0800
"Massimo" <barone@xxxxxxxxx> wrote in message
news:OCFLd1sCHHA.4256@xxxxxxxxxxxxxxxxxxxxxxx
[...]
The main reason is because I'll need to actually talk with the modem in
the production code, so I'm trying to get a grip on how to handle it, by
using a simulated client that talks with the modem by a serial port. I can
of course wait for the actual hardware to be available, but I'd really
like to be able to do some tests by now. But in order to do that, I need a
TCP/IP stack to run over a serial line.
I'm not sure that's true. That is, such a thing already exists (for
example, this is essentially what the DUN stuff does), but it doesn't allow
you to test the part of the code you seem to want to test.
It seems to me that if you want to test managing the GPRS hardware itself,
you need to actually write the network adapter driver itself. That is, the
component that allows Windows to create a TCP/IP adapter through a GPRS
modem.
If you have something that already implements the TCP/IP stack over a serial
line, then by the time your application can interact with it, it already
looks like TCP/IP.
Personally, I'm not sure I see the value in doing what you want to do. That
is, I'm guessing GPRS dial-up network drivers already exist (so there's no
need to do it yourself for the purpose of getting the actual functionality),
and it's very likely that the hard parts of actually controlling the
hardware (actually getting the serial port open, managing the configuration
of the port, translating that into something that looks like TCP/IP to the
client software, etc) are going to be very different on the actual device
than under a Windows test platform.
But, assuming you really believe this is important, from your description it
sounds to me as though you are signing up to write a network adapter driver.
In any case, no...I believe the answer to your question is that there is not
any support for such a thing in .NET, not in the way you appear to be asking
for. Obviously, you could interact with an existing TCP/IP adapter using
..NET, once it's been connected by Windows. But I'm pretty sure .NET doesn't
include any of the actual TCP/IP management functionality within it. All
that is in the lower-level network drivers, and even if .NET did handle the
TCP/IP protocol stuff itself, I doubt that the raw details would be
accessible to a .NET program.
Pete
.
- Follow-Ups:
- Re: Raw TCP/IP library?
- From: Massimo
- Re: Raw TCP/IP library?
- References:
- Re: Raw TCP/IP library?
- From: Peter Duniho
- Re: Raw TCP/IP library?
- From: Massimo
- Re: Raw TCP/IP library?
- Prev by Date: Re: Trace.WriteLine(object value) - causes "System.InvalidOperationException: Collection was modified; enumeration operation may not execute."
- Next by Date: Re: Accessing value of a Variable in parent from custom control
- Previous by thread: Re: Raw TCP/IP library?
- Next by thread: Re: Raw TCP/IP library?
- Index(es):
Relevant Pages
|