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?
Non-official IPs like 192.168.x.x are typically not forwarded by routers. Check the configuration of your WLAN router. You may also use network sniffers like tcpdump or Ethereal to see which packet is sent and which not.
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.
rtroute add 0.0.0.0 netmask 0.0.0.0 gw 192.168.1.1
This creates a default route as you might know it from standard Linux.
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.
Well, TDMA is also some kind of traffic shaper, and with TDMA-V2 we will even be able to assign real-time bandwidth to certain users (e.g. applications). But what you seem to be looking for is already available with the standard kernel. I'm not an expert about this topic, I just read that it is there.
Is this feasible? Can I also do some control on the incoming traffic as well? like dedicated buffer control for different socket for example.
No, at least the system load incoming traffic causes is uncontrollable. And that is exactly why you loose determinism when attaching an RTnet system to a non-RTnet network.
Jan
smime.p7s
Description: S/MIME Cryptographic Signature
