Hi Jan,

I have created a path against rtnet V0.9.2 that allows to route IP packets 
using the
source and the destination IP address.
It works fine in my application as I do not need the rtping command.
This command is the only one that does not have the rt device as argument, thus 
it
just picks the first entry that has the correct destination address.
If rtping was changed, the whole stuff could be improved a little bit by using
a better hash function for routing.
Currently, only the destination address is used for the hash function.
For having multiple devices with the same IP address on different devices, this 
means
that it has to be looped through the list of route entries for this hash.
A better approach could be to use a hash function that has source and 
destination
address as input. However, with this approach it is not possible to do a 
"mixed" access
i.e. routing with/without checking the source address.

There is a a define the enables the routing. However, this define is currently 
checked only in
the route_output routine as this is the only real time-critical.

It would be great to add this patch to the next version!

Regards

Mathias




-- 
Mathias Koehrer
[EMAIL PROTECTED]


Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren
ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig
und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer,
nur  44,85 €  inkl. DSL- und ISDN-Grundgebühr!
http://www.arcor.de/rd/emf-dsl-2

Attachment: rtnet.patch
Description: Binary data

Reply via email to