Hello, Jan and Hans.

Thanks a lot for the answer and helps. I will have a further look
about the vnic etc.

>Since RTping AFAIK sends standard ICMP ping packets, every IP stack support=
>ing ICMP should send a response.
>
>
>> However it still seem that I=20
>> can not reach the outside even though I added some net route entry? Is th=
>ere a=20
>> option to add a default gateway entry in RTRouting table same as route in=
>=20
>> Linux?
>
>How did you try to reach the outside?

I have installed RTAI/RTNET on 192.168.1.101, which connects to 192.168.1.1 (
a WLAN router to the outside world) and another laptop also on the lan 
(192.168.1.100 via hifi)

by using "rtroute solicit 192.168.1.1" dev rteth0, now I can rtping 
192.168.1.1.

I have anoter machine in my lab which run Redhat 7.2 (142.104.x.x)
so I add another net route " rtroute add 142.0.0.0 netmask 255.0.0.0 dev 
192.168.1.1  "
then I use RTPing 142.104.x.x and there is no response back.

Are there anything missing or did I do something wrong?

As said, is there a way that I can add a net route entry to all non-local
hosts by using rtroute, such as routing all traffic to my default gateway
192.168.1.1 via the interface rteth0.


I am thinking to do a prelimary experiments about network traffic control in 
RTAI kenel, for example, to creat two RT tasks with seperate RTsocket
and control the outgoing traffic for each of them for example, 100kbits for 
the first one and 200kbits for the 2nd one? have anybody tried this using 
RTNET, I think I need to change some internal RTNET things to do that.
do not understand that much now.

Is this feasible? Can I also do some control on the incoming traffic as well?
like dedicated buffer control for different socket for example.

Thanks a lot.

Regards,

Howard.

>
>
>> So in RTnet, the protocol has to be Realtime UDP/IP protocol (or raw sock=
>et=20
>> API) to communicate with outsdie machine (those non-RTnet machines)?
>
>You should not directly communicate with non real-time machines using the R=
>Tnet API.
>
>
>> If I want to use regular TCP/IP socket communication, does that means I h=
>ave=20
>> to use LXRT and user space interface? after the start up of the standalon=
>e=20
>> RTNET machine, ( I did it mannually, seem only the local loop works for R=
>T)
>> How can I make the regular linux TCP networking work, I tried to use ifco=
>nfig=20
>> to bring up the rteth0 interface and add some route as well. It seems I c=
>an=20
>> not reach the outside world - some filter warning.
>
>To communicate with machines outside your real-time network, you should con=
>figure 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 virt=
>ual nic is just like a usual network card.
>
>Have a look at the PDF file attached to this email.
>
>
>Best regards, Hans-Peter
>--=20
>Hans-Peter Bock, Dipl.-Ing. - http://www.isw.uni-stuttgart.de/
>ISW - Universit=E4t Stuttgart, Seidenstra=DFe 36, 70174 Stuttgart
>http://www.isw.uni-stuttgart.de/seminare/STF/STF04_Fokus.pdf
>
>Yes, you can set up so-called network routes, see README.routing.
>Switch on the respective feature and use rtroute again, now providing a
>network address and mask as destination.
>




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
RTnet-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to