"Jennings, Richard R" wrote:
>
> Greetings all,
> I have been able to get RTnet version 0.9.0 up and running
> with one exception. The full realtime network rt_echo_client
> module gets the following error even after doing the "route
> solicit" as shown in the docs:
>
> rt_ip_route_output() route not found daddr=010215ac saddr=00000000 oif=0
> sendto()=-113
>
> I changed the hardcoded IP address to match my network.
> I also verified the ARP was happening correctly between the
> two RTnet controllers using tcpdump and ethereal.
>
> Has anyone got rt_echo_client working correctly? Is there
> some trick I missed?
>
Hi Rich,
I had exactly that problem too ...until I did the route solicit on
*both* machines. Then it worked, but I never really understood why the
2nd route solicit was needed. Maybe Dave knows.
Best regards,
Ian
> Thanks,
> Rich
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Richard R. Jennings
> Embedded Software Engineer - The Boeing Company
> Flight Simulation Technology / Advanced Avionics Center - St. Louis
> Computational & Image Generation Group
> (314)234-0460 FAX (314)232-7972
> [EMAIL PROTECTED]
>
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> ---
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
