Hello Howard, > It seems that I can only RTPing local interface and If I added a host route > entry for my WLAN gateway, it seems reachable using RTPing - Is this true? I > am wonderring if I did right.
this is ok. > Can a normal TCP/IP host respond back the RTping? Since RTping AFAIK sends standard ICMP ping packets, every IP stack supporting ICMP should send a response. > However it still seem that I > can not reach the outside even though I added some net route entry? Is there a > option to add a default gateway entry in RTRouting table same as route in > Linux? How did you try to reach the outside? > So in RTnet, the protocol has to be Realtime UDP/IP protocol (or raw socket > API) to communicate with outsdie machine (those non-RTnet machines)? You should not directly communicate with non real-time machines using the RTnet API. > If I want to use regular TCP/IP socket communication, does that means I have > to use LXRT and user space interface? after the start up of the standalone > RTNET machine, ( I did it mannually, seem only the local loop works for RT) > How can I make the regular linux TCP networking work, I tried to use ifconfig > to bring up the rteth0 interface and add some route as well. It seems I can > not reach the outside world - some filter warning. To communicate with machines outside your real-time network, you should configure the non real-time virtual nic "vnic0" in linux using ifconfig. This virtual nic is provided by RTmac and encapsulates your non real-time linux communication for sending it over the real-time network. For linux the virtual nic is just like a usual network card. Have a look at the PDF file attached to this email. Best regards, Hans-Peter -- Hans-Peter Bock, Dipl.-Ing. - http://www.isw.uni-stuttgart.de/ ISW - Universit�t Stuttgart, Seidenstra�e 36, 70174 Stuttgart http://www.isw.uni-stuttgart.de/seminare/STF/STF04_Fokus.pdf
RTnet - VNIC.pdf
Description: Adobe PDF document
signature.asc
Description: Digital signature
