Any updates here?
Eric
On Tue, Mar 15, 2011 at 10:09 PM, Lee Eric openlinuxsou...@gmail.com wrote:
I forget to mention something, the NIC duplex mode is half duplex I
think that's not normal. So is there any way to change that?
Thanks.
Eric
On Tue, Mar 15, 2011 at 8:41 PM, Lee Eric
Thanks mate. mTCP really works very well.
Eric
On Mon, Mar 14, 2011 at 6:06 AM, Michael B. Brutman
mbbrut...@brutman.com wrote:
The mTCP DHCP client writes output to STDOUT and to the MTCPCFG file,
which is pointed to by an environment variable. It's a simple matter of
programming/scripting
I forget to mention something, the NIC duplex mode is half duplex I
think that's not normal. So is there any way to change that?
Thanks.
Eric
On Tue, Mar 15, 2011 at 8:41 PM, Lee Eric openlinuxsou...@gmail.com wrote:
Thanks mate. mTCP really works very well.
Eric
On Mon, Mar 14, 2011 at
cordat...@aol.com wrote:
An alternative is to use Mike Brutman's mTCP DHCP program.
This is of course true, but there is another alternative . . .
So to sum up: if your application program uses the right
version of WATTCP then you don't need to do anything,
run the program and it will
The mTCP DHCP client writes output to STDOUT and to the MTCPCFG file,
which is pointed to by an environment variable. It's a simple matter of
programming/scripting to convert the output from either one into
something that looks like a static WATTCP configuration. I've tested my
DHCP client
