[cgl_discussion] tipc getting started. problem with /dev/tipc

Guo, Min min.guo at intel.com
Tue May 27 18:05:00 PDT 2003


Actually, there are no /dev/tipc in current release, 
you can use 
int fd = socket (AF_TIPC, SOCK_TIPC,0);
to create the fd you need.

Thanks
Guo Min 
The content of this email message solely contains my own personal views,
and not those of my employer.


-----Original Message-----
From: Randy Macleod [mailto:macleodr at nortelnetworks.com]
Sent: Wednesday, May 28, 2003 1:49 AM
To: mika at osdl.org; cgl_discussion at lists.osdl.org
Subject: [cgl_discussion] tipc getting started. problem with /dev/tipc


Hi,
   I'm quite interested in and impressed by TIPC.


I'm having trouble getting some example code to run due to
the /dev/tipc "driver".

I've downloaded both the sourceforge version of tipc.
I compiled the kernel loadable module
( using from 0.94) and can install it like:

node1:
/sbin/insmod tipc.o eth0=1 udp=4711 zone=1 subnetwork=1 processor=1

node2:
/sbin/insmod tipc.o eth0=1 udp=4711 zone=1 subnetwork=1 processor=2

node 2 dmesg output:

-----> TIPC: Compiled at May  8 2003 15:34:30 starting...
-----> TIPC: Own Address = <1.1.2>
-----> TIPC: Bearer type <ethernet> registered
-----> TIPC: Bearer instance <ethernet:eth0> enabled
-----> TIPC/UDP: Using system id 4711
-----> TIPC: Bearer type <udp> registered
-----> TIPC/UDP: Joined multicast group on interface lo
-----> TIPC/UDP: Joined multicast group on interface eth0
-----> TIPC/UDP: Joined multicast group on interface vmnet8
-----> TIPC/UDP: Multicast listener socket on address:port = 225.0.1.103:55555
-----> TIPC/UDP: Unicast listener socket on port 55555
-----> TIPC: Bearer instance <udp:udp> enabled
-----> TIPC: Socket adaptation started.
-----> Established link <1.1.2:eth0-1.1.1:eth0> on Network A
-----> Established standby link <1.1.2:udp-1.1.1:udp> on Network C


In trying to run the example code in the 0.94 manual
connless_[client | server].c

I see that the client fails because there is no /dev/tipc.
Is this to be created manually with mknod and if so does
it have to be done after the module is inserted or before?
What should the command line arguements be?

mknod /dev/tipc c 30 99

failed.

Is there better (working) example code and/or beginner documentation available?
Does the Bitkeeper code only work with the 2.5 kernel stream?

I'm using Redhat 8.0:
 > uname -a
Linux somehost 2.4.18-19.8.0 #1 Thu Dec 12 05:39:29 EST 2002 i686 i686 i386 
GNU/Linux
 > gcc --version
gcc (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7)

Help!


TIA,

// Randy MacLeod

_______________________________________________
cgl_discussion mailing list
cgl_discussion at lists.osdl.org
http://lists.osdl.org/mailman/listinfo/cgl_discussion




More information about the cgl_discussion mailing list