LinuxQuestions.org - Networking Usign 1394 (IP over 1394)

- Programming (https://www.linuxquestions.org/questions/programming-9/)

- - Networking Usign 1394 (IP over 1394) (https://www.linuxquestions.org/questions/programming-9/networking-usign-1394-ip-over-1394-a-309500/)

Networking Usign 1394 (IP over 1394)

Hi,

I have written my own ohci 1394 driver and IP over 1394 layer (compliant to RFC 2734 ). I am trying to intergrate it with Linux networking layer.
What is observe is that
I am able to ping each device over 1394.
But when I am sendign an HTTP request nothign seems to be happening.
I have captured a log usign Ethereal on linux and what I see is
the ARP request is going correctly and I am gettign a correct ARP respose for it too.
Then a TCP request with [SYN] set from the browser side goes to the server side ,
now from the server side I get a correct TCP respose with the flags [SYN ] and [ACK] set.
That is it, to this the browser side is supposed to send an TCP with flag[ACK] .
But in my case nothing happens , the browser keeps sending the first request again and again.

Questions:
Do i need to enable anything if I use the networking layer of Linux of IP over 1394.
Since the first response is comign correctly what could be the issue while sending the second response.

Any pointer woudl really be helpful

Regards,
Sapna

can you ping across? is the routing table being populate dwith a route to the host?

Quote:

I am able to ping , and I have also captured the packets on ethereal. What i see is the ARP request are going fine and the respose for the ARP is also fine.
The first TCP request from the browser side is also correct and gets an [ACK] fromt he server side but the browser does nto send an [ACK] to this response ans keep send the first request again and again.

If you can ping accross the link, and recieve replies, then there is nothig wrong with the link. You networking stack works layers 1 - 4. Your web browser is a layer 7 protocol software and depends on the lower levels to work. If your web browser doesn't work, try a different browser, or verify that there is a route on the remote host to forward the packets to the destination. If the destination is the remote host, make sure that apache, or whatever server you're trying to access, is set up ro run on that port. Also check and see if you can ssh, telent, ftp, or smb connect to the remote host.