Hi Alain:
I've been able to get two UML guests to communicate via TIPC, but it took a
little bit of digging to figure out how to do it. Here are the notes that I
made for myself:
Ethernet interface basics for UML
---------------------------------
o to create a virtual "eth0" device at invocation time
§ (host) ./vmlinux ... eth0=mcast[,<MAC>]
§ the interface can be used to communicate with other UML sessions;
however none of the simulated packets actually go off-host,
so you can't screw up users on your real network
§ specifying a unique MAC address for each interface (of the form
xx:xx:xx:xx:xx:xx) is optional,
but is probably a good idea to ensure things go where they should
(if no MAC address is specified UML uses FE:FD:00:00:00:00,
unless you also specify an IP address for the interface)
o the interface is inactive by default, so you must manually enable it
§ (uml) ifconfig eth0 up
o (optional) mark device as promiscuous
§ (uml) ifconfig eth0 promisc
§ you only need to do this if you have multiple interfaces on the same
multicast group (see below);
for example, when testing duplicate node address detection logic;
this lets TIPC's Ethernet receive routine know that it needs to filter out
incoming messages
that weren't intended for the interface, since UML currently doesn't do
this properly
o if you want an Ethernet interface to have an IP address (not needed for TIPC),
you'll have to add that to the "ifconfig" arguments (see the man page for
ifconfig)
or at invocation time (see UML text for details)
o if you want multiple Ethernet interfaces you need to specify a second ethX
argument
and make sure it uses a different multicast group id than the first one
(which uses 1102 as the default)
§ (host) ./vmlinux ... eth0=mcast,<MAC1>,,1102 eth1=mcast,<MAC2>,,1103
· this creates a pair of Ethernet interfaces that "talk" on separate lines
§ you MUST specify different group ids or you'll end up with both your
interfaces
talking on the same virtual Ethernet segment (sometimes useful in testing
error handling)
o TIPC link troubleshooting guide:
§ did you remember to enable your bearers using "tipc-config -be"?
§ did you remember to enable your Ethernet interfaces using "ifconfig"?
§ did you configure your interfaces with unique MAC addresses?
§ did you configure your interfaces with compatible multicast group ids?
§ is your host's firewall blocking packets sent to multicast groups?
· you may need to reconfigure firewall to allow traffic on 1102:udp,
1103:udp, etc.
(or just disable the firewall completely)
Hope this helps!
Regards,
Al
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of GOULNIK
ALAIN
Sent: Friday, September 21, 2007 10:01 AM
To: [email protected]
Subject: [tipc-discussion] TIPC & UML
Hi,
I'm running TIPC 1.7.4 on a UML linux 2.6.20 kernel on two different
instance on the same host (this host being a 2.6.14 Linux kernel). The two UML
instances can ping each other thanks to tun/tap.
In standalone mode, I can run the TIPC demo program but unfortunately
the two TIPC nodes does not find any neighbors and does not seem to communicate.
Maybe it's more an UML question, but I was wondering if this
configuration look possible according to you or if you have experienced problem
working with TIPC & UML.
Thanks for your answers.
Al.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
