Hi Jan, thanks for your response. I agree, the main part is not too compilcated to solve. I see the most tricky part in the rtcfg directory as even the calls from rtroute must take care of this...
I will have a closer look to this next week. Regards Mathias ----- Original Nachricht ---- Von: Jan Kiszka <[EMAIL PROTECTED]> An: "M. Koehrer" <[EMAIL PROTECTED]> Datum: 26.05.2006 15:48 Betreff: Re: [RTnet-users] Issue with multiple rt NICs / routing > M. Koehrer wrote: > > Hi everybody, > > > > I just switch over to the latest version of rtnet. Before I worked fairly > long > > with the "historic" 0.6.0 with some patches. > > > > I have found one issue that worked with the old version but does not work > with > > the latest version: > > I am using two eepro100 adapters as two real time network devices. > > I want to access two non-rtnet embedded devices that have both the same > fix IP address. > > > > In previous versions of rtnet the routing was done using the source and > the > > destination address, now only the destination address is in use for > routing. > > That means, that it is not possible in my setup to distinguish between > > the two embedded devices. > > In the previous version, I set a different IP address to each of the NICs > and this > > allowed me to access both embedded devices (the source address was > relevant). > > > > > > What can I do? I looked into the code and found out, that this issue > > is not a trivial one as a extension of the routing (including API > interface) > > has to be done. > > Ok, I see your problem and I agree that a solution is not trivial but > also not too complicated. In fact, this source routing check has been > "optimised" out during the revision of IPv4-routing. Typical RTnet > setups do not require this, but some do, and we should not exclude them. > > I currently have in mind to re-introduce the related checks to > rt_ip_route_output, but make this optional. Just needs a wrapping macro > (to switch the number of arguments), an extension of all > rt_ip_route_output invocations (passing INADDR_ANY when unsure), and of > course the additional test against the source address itself. I don't > think further quirks are hidden (famous last words...). > > Mathias, if you could already spend a bit time on this, I would add > missing bits and merge it into trunk before 0.9.3. Unfortunately, my > time is limited. > > Jan > > -- 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 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642 _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
