I could use some input on what is stopping our linux box, TIPC 1.7.5, from talking to our vxWorks 6.2 box, TIPC 1.3.x. I've captured an ethernet trace of the problem, attached. The linux box (tipc 1.1.1) cannot establish the link with the vxWorks board (which has two processors, TIPC addresses 1.1.21 and 1.1.22). From what I can tell the neighbot discovery appears correct but then the link activation is failing. It looks like the linux side is trying to activate but there is no response from the vxworks processors besides the link resets.

Thanks,
Brad

Horvath, Elmer wrote:
Hi Brad,

The TIPC that was out with VxWorks 6.2 used an older version numbering
scheme.  That version is closer to the TIPC 1.3.x numbering used in the
open source version of TIPC.

I would suggest upgrading the VxWorks 6.2 to use TIPC 1.7.5.

But even if you do not upgrade, you should be able to establish links
between the linux box and the VxWorks box.

You won't be able to use a number of features:
- stream sockets
- multi-cast
- tipcConfig / tipc-config

Good luck on your endeavours.

Elmer
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brad
Stephens
Sent: Tuesday, March 11, 2008 3:50 PM
To: [email protected]
Subject: [tipc-discussion] TIPC version in vxWorks 6.2

I'm working on getting TIPC 1.7.5 on a linux box talking with a vxWorks
board running vxWorks 6.2.  I understand that the TIPC version on
vxWorks 6.2 is described as version 1.2.  I had heard that this was an
"old" versioning mechanism and that it is actually based on TIPC 1.5.x.

Is this the case?
Thanks,
Brad

Attachment: tipc17-13.pcap
Description: Binary data

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Reply via email to