Hi,
the following configuration is present:
RTOS 6.2A target (x86) in an own network segment with 10Mbit Ethernet
(10.1.1.x).
This network segment is connected to an other segment (192.168.10.x) with
100MBit Ethernet via gateway.
The target is running the tiny TCP/IP Stack.
Problem:
When i use phindows or produce heavy network load to and from the target at
the same time (e.g. FTPing), all network connections to the target stop. No
new connects are possible. Pinging the target runs into timeout. A ping from
the target to an other host says: ‘sendto: No buffer space available’.
When the target is located in the same network segment as the host no
problems occur. With the full TCP/IP stack no problems occur.
Has anybody an idea about this behaviour?
Thanks
Oliver Weber
What network driver are you using with the tiny stack?
chris
Oliver Weber <Oliver.Weber@soft-gate.de> wrote:
Hi,
the following configuration is present:
RTOS 6.2A target (x86) in an own network segment with 10Mbit Ethernet
(10.1.1.x).
This network segment is connected to an other segment (192.168.10.x) with
100MBit Ethernet via gateway.
The target is running the tiny TCP/IP Stack.
Problem:
When i use phindows or produce heavy network load to and from the target at
the same time (e.g. FTPing), all network connections to the target stop. No
new connects are possible. Pinging the target runs into timeout. A ping from
the target to an other host says: ‘sendto: No buffer space available’.
When the target is located in the same network segment as the host no
problems occur. With the full TCP/IP stack no problems occur.
Has anybody an idea about this behaviour?
Thanks
Oliver Weber
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
I’ve had this problem too. It turns out that my network driver was not
getting an interrupt indicating data had been sent. For my case it was
faulty hardware. For me it appeared as though the transmit data buffer had
filled up, and the driver was not getting any interrupts. I changed the
interrupt it uses and it works much better.
Kevin
“Oliver Weber” <Oliver.Weber@soft-gate.de> wrote in message
news:aoh5i0$30c$1@inn.qnx.com…
Hi,
the following configuration is present:
RTOS 6.2A target (x86) in an own network segment with 10Mbit Ethernet
(10.1.1.x).
This network segment is connected to an other segment (192.168.10.x) with
100MBit Ethernet via gateway.
The target is running the tiny TCP/IP Stack.
Problem:
When i use phindows or produce heavy network load to and from the target
at
the same time (e.g. FTPing), all network connections to the target stop.
No
new connects are possible. Pinging the target runs into timeout. A ping
from
the target to an other host says: ‘sendto: No buffer space available’.
When the target is located in the same network segment as the host no
problems occur. With the full TCP/IP stack no problems occur.
Has anybody an idea about this behaviour?
Thanks
Oliver Weber
I use tulip driver for a ‘DC21142/3 PCI/CardBus 10/100 Mbit Ethernet Ctlr’
from Digital Equipment Corporation.
Oliver
“Chris McKillop” <cdm@qnx.com> schrieb im Newsbeitrag
news:aohm6i$b3s$1@nntp.qnx.com…
What network driver are you using with the tiny stack?
chris
Oliver Weber <> Oliver.Weber@soft-gate.de> > wrote:
Hi,
the following configuration is present:
RTOS 6.2A target (x86) in an own network segment with 10Mbit Ethernet
(10.1.1.x).
This network segment is connected to an other segment (192.168.10.x)
with
100MBit Ethernet via gateway.
The target is running the tiny TCP/IP Stack.
Problem:
When i use phindows or produce heavy network load to and from the target
at
the same time (e.g. FTPing), all network connections to the target stop.
No
new connects are possible. Pinging the target runs into timeout. A ping
from
the target to an other host says: ‘sendto: No buffer space available’.
When the target is located in the same network segment as the host no
problems occur. With the full TCP/IP stack no problems occur.
Has anybody an idea about this behaviour?
Thanks
Oliver Weber
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Oliver Weber <Oliver.Weber@soft-gate.de> wrote:
I use tulip driver for a ‘DC21142/3 PCI/CardBus 10/100 Mbit Ethernet Ctlr’
from Digital Equipment Corporation.
Definatly sounds like an interrupt issue. Is your card sharing an interrupt
with any other devices? You might want to try using the card in another
slot in your machine. Are you running slogger on your QNX box? If so, does
anything show up in the output of sloginfo?
chris
Oliver
“Chris McKillop” <> cdm@qnx.com> > schrieb im Newsbeitrag
news:aohm6i$b3s$> 1@nntp.qnx.com> …
What network driver are you using with the tiny stack?
chris
Oliver Weber <> Oliver.Weber@soft-gate.de> > wrote:
Hi,
the following configuration is present:
RTOS 6.2A target (x86) in an own network segment with 10Mbit Ethernet
(10.1.1.x).
This network segment is connected to an other segment (192.168.10.x)
with
100MBit Ethernet via gateway.
The target is running the tiny TCP/IP Stack.
Problem:
When i use phindows or produce heavy network load to and from the target
at
the same time (e.g. FTPing), all network connections to the target stop.
No
new connects are possible. Pinging the target runs into timeout. A ping
from
the target to an other host says: ‘sendto: No buffer space available’.
When the target is located in the same network segment as the host no
problems occur. With the full TCP/IP stack no problems occur.
Has anybody an idea about this behaviour?
Thanks
Oliver Weber
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
\
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
There no messages about network / driver errors in the system log. I tried
to change IRQ for the card. Not working. The used irq is not shared with any
other device.
I dont believe its an irq problem because:
- Everythings works fine with the full TCP/IP Stack. The connection
sometimes slows down but never breaks.
- There are no problems, when there is no gateway between target and host.
Oliver
“Chris McKillop” <cdm@qnx.com> schrieb im Newsbeitrag
news:aon9ji$rng$1@nntp.qnx.com…
Oliver Weber <> Oliver.Weber@soft-gate.de> > wrote:
I use tulip driver for a ‘DC21142/3 PCI/CardBus 10/100 Mbit Ethernet
Ctlr’
from Digital Equipment Corporation.
Definatly sounds like an interrupt issue. Is your card sharing an
interrupt
with any other devices? You might want to try using the card in another
slot in your machine. Are you running slogger on your QNX box? If so,
does
anything show up in the output of sloginfo?
chris