Amine El hedadi wrote:
Hi jan;
What about rt_ip_route_output()? Doesn't it exactly do what you need? It
fills a dest_route structure which then contains a pointer to the output
rtdev. Take a look at rt_udp_sendmsg() for a usage example.
That's ok, rt_ip_route_output() give a pointer to the output rtdev , but
only in the case when we add the multicast adress to route table :
# rtroute add 239.0.0.2 01:00:5e:00:00:01 dev rteth0 , that work well,
But in the case of multicat, we can calculate the mac address from the IP
address without using routing table.
So i have added a conditions test before the call of the
"rt_ip_route_output()" in udp_sendmsg function
if the dist address is multicast i calculate the mac adresse and i locate the
rtdev by the local address (saddr).
Well, I would prefer some solution that actually creates such a routing
table entry. Not yet sure how this may look like. Either we have to
distribute this setup via RTcfg to the stations or some socket ioctl or
sockopt has to be introduced to create the routing table entry on
demand. The advantage: this avoids the additional check in the
transmission path for both multicast and unicast packets.
So nowday Im able to recive and send mulicast packets with rtnet .Im testing
it now and i will send you a first realise of my patch soon.
PS : i have only enabled the multicast support for the two NICs ,8139too et
e100.
Great, looking forward!
Jan
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
RTnet-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rtnet-developers
