mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: skinbits@substancia.com
To: linux-kernel@vger.kernel.org
Subject: TCP/IP receive packet problem
Date: Tue, 15 May 2001 19:53:33 +0100	[thread overview]
Message-ID: <20010515195333.B1095@substancia.com> (raw)

We are doing the project to implement IP communication over a SCSI bus.
 
So far we have a working communication between the to computers, we can
ping from both computers. Traceroute only works from one computer to
the other and we can't understand why. We are thinking a lot on the 
issue but we haven't found the solution and worst, we haven't found the 
problem.
  
The problem, readingthe ipgrab logs, is that a UDP packet is sent to the
other host with TTL of 1. It passes all our system (is received by the
sym53c8xx driver, send to snh driver, then scsinet and then we
use netif_rx to send the packet to the TCP/IP stack). Now the TCP/IP
should response with a ICMP packet of host unreachebla. But, this packet
is never sent.

Another strange thing is that we change the SCSI ID's, in the computer
were traceroute works, it stop working, and starts working in the
other...

We have checked all parts of the system to see if the packet is correct
(it is), if the TCP/IP dosen't drop because of congestion (It dosen't).

If we use only ICMP (ping) there is no problem. If we use anything else
(UDP,TCP) it dosen't work...

We are using kernel 2.4.4 with a modified sym53c8xx target mode
driver from kernel 2.4.0 and some drivers made by us.
     
If you need more info check http://www.ccjfaro.org/~skinbits/ipoverscsi.
The code is in there and you can download it. There is also some ipgrab
(http://ipgrab.sourceforge.net) traces that shows what I tryed to
explain. You can also send me mail...

Pedro Semeano

                 reply	other threads:[~2001-05-15 19:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010515195333.B1095@substancia.com \
    --to=skinbits@substancia.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®