Telnet Problems

Hi All,

I’m currently writing a network driver based around the example PCnet
code for an x86 system.

The driver appears to be working fine and I can ping and ftp data
between the QNX6.1 Patch A system and a Windows 98 system.

However, I have a problem with Telnet. It manifests itself when I
connect to the QNX machine. I can log in fine and do some basic stuff ls
etc., but when I run a command that will generate a large number of IP
packets the windows telnet session “appears” to hang. But, this session
has not truly hung as I can still send commands to the QNX machine
(shutdown etc).

The problem seems to be that the QNX machine is sending invalid IP
frames back to the Windows box.


Any Ideas?

Does it happen with other drivers? Have you
verified that what is being sent to the driver is
what is in fact being put on the wire?

-seanb

Dave Edwards <nobody@home.com> wrote:
: Hi All,

: I’m currently writing a network driver based around the example PCnet
: code for an x86 system.

: The driver appears to be working fine and I can ping and ftp data
: between the QNX6.1 Patch A system and a Windows 98 system.

: However, I have a problem with Telnet. It manifests itself when I
: connect to the QNX machine. I can log in fine and do some basic stuff ls
: etc., but when I run a command that will generate a large number of IP
: packets the windows telnet session “appears” to hang. But, this session
: has not truly hung as I can still send commands to the QNX machine
: (shutdown etc).

: The problem seems to be that the QNX machine is sending invalid IP
: frames back to the Windows box.


: Any Ideas?

Hi Sean,

I think that I have traced this one to my hardware. The device itself
cannot deal with fragmented IOV’s particularly if they have an odd
number of bytes.

Defragmenting the IOV seems to sort out the problem, although it might
be related to my big stack IP problem.

Dave




Sean Boudreau wrote:

Does it happen with other drivers? Have you
verified that what is being sent to the driver is
what is in fact being put on the wire?

-seanb

Dave Edwards <> nobody@home.com> > wrote:
: Hi All,

: I’m currently writing a network driver based around the example PCnet
: code for an x86 system.

: The driver appears to be working fine and I can ping and ftp data
: between the QNX6.1 Patch A system and a Windows 98 system.

: However, I have a problem with Telnet. It manifests itself when I
: connect to the QNX machine. I can log in fine and do some basic stuff ls
: etc., but when I run a command that will generate a large number of IP
: packets the windows telnet session “appears” to hang. But, this session
: has not truly hung as I can still send commands to the QNX machine
: (shutdown etc).

: The problem seems to be that the QNX machine is sending invalid IP
: frames back to the Windows box.


: Any Ideas?

I’ve seen the same problem crop up after an upgrade to 4.25. If I
telnet in and run sin ver, the output hangs. If I pipe the output
through more, it does not hang.

—Thom

PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25L Feb 15 2001
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24V Feb 18 2000
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.eide eide 4.25A Feb 09 2000
//1/bin/Dev32 Dev32 4.23G Oct 04 1996
//1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Net Net 4.25C Aug 30 1999
//1/bin/Net.ether82595 Net.ether825 4.26C Aug 30 1999
//1/bin/Net.ether82595 Net.ether825 4.26C Aug 30 1999
//1/bin/Net.ether82595 Net.ether825 4.26C Aug 30 1999
//1/*/usr/ucb/Socket Socket 4.25H Jul 30 1999
//1/bin/Dosfsys Dosfsys 4.23E Jan 21 1997
//1/bin/cron cron 4.23B Oct 30 1997

Dave Edwards wrote:

Hi Sean,

I think that I have traced this one to my hardware. The device itself
cannot deal with fragmented IOV’s particularly if they have an odd
number of bytes.

Defragmenting the IOV seems to sort out the problem, although it might
be related to my big stack IP problem.

Dave




Sean Boudreau wrote:

Does it happen with other drivers? Have you
verified that what is being sent to the driver is
what is in fact being put on the wire?

-seanb

Dave Edwards <> nobody@home.com> > wrote:
: Hi All,

: I’m currently writing a network driver based around the example
PCnet : code for an x86 system.

: The driver appears to be working fine and I can ping and ftp data :
between the QNX6.1 Patch A system and a Windows 98 system.

: However, I have a problem with Telnet. It manifests itself when I :
connect to the QNX machine. I can log in fine and do some basic stuff
ls : etc., but when I run a command that will generate a large number
of IP : packets the windows telnet session “appears” to hang. But,
this session : has not truly hung as I can still send commands to the
QNX machine : (shutdown etc).

: The problem seems to be that the QNX machine is sending invalid IP
: frames back to the Windows box.


: Any Ideas?