Hi,
I have to bring up a communication between a LXRT-sender ( hosted on 131.114.24.2) and a non-real time receiver ( 131.114.24.228 , now with ethereal installed to check the traffic ).
As i understand, i don't need TDMA ( my lan has only this 2 pc ); so I'm trying to use nomac.
Of course, if you *have to* use a non-rt station on one side, you cannot use TDMA. But then RTnet may only give you improved latency in case you cannot precisely predict how much and how often the non-rt box transmits data. Installing RTnet can then even be a risk with respect to the determinism of other real-time applications running on that box (packet reception runs in rt-context at high priority).
To use NoMAC might be an option in case you are looking for a way to transmit both data coming from the rt and the non-rt domain on your RTnet box. Then you need some demultiplexing part on your non-rt box for the encapsulated non-rt data (see RTmac specification for the protocol). If this all makes sense, is a different topic. NoMAC has been added foremost as a template for new RTmac disciplines aside TDMA.
My trouble is the configuration.
This is what i do:
- bring down eth0 ( and the linux driver );
- insmod rtai_rtdm , rtnet , rt_natsemi ( the rt NIC driver ) , rtmac , nomac ( rt_loopback too.. ) ;
- rtifconfig rteth0 up 131.114.24.2 netmask 255.255.255.0 ;
- on the receiver machine: run ping 131.114.24.2 and have a response ( and the new entry is added automatically in rtroute with the correct MAC) ;
Now the two machines can ping one to each other, but the sending fails ( only send_rt fails, bind_rt() and connect_rt() don't return any errors ). the error returned by send_rt() is: NO SUCH FILE OR DIRECTORY .
I'm quite sure the code is correct ( I compared with thte examples )
Can someone help me? which mistake i made?
If the destination address you use for send_rt (i.e. the one passed via connect_rt) is actually listed by rtroute, send_rt should not fail. However, I'm not yet able to track down the return code you mentioned. Is it really -2 (ENOENT)? This value is only returned upon route or protocol deletion or by RTcfg. It should not show up via send_rt (I'm refering to version 0.8.1).
Jan
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ RTnet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rtnet-users
