LEBRETON, Julien wrote: > I check that there is no packet leaving rteth2 by looking at my NIC interface > and the destination host. > When I ping 152.157.1.2 my input NIC's receive data (data led is flashing) > but the data led of my output NIC (rteth2) isn't flashing.. Ok it is not > relevant. > Another way to check is to look at the destination box. I have captured > packet on his interface. But no packet arrived. > > And I have noticed something odd.. > On my windows box, I can ping any machine even those that do not exist.. > > ping 152.157.1.2 => I have a reply > ping 152.157.1.56 => I have a reply (but no machine with this IP address) > ping 153.156.25.24 => I have a reply.. this is very odd..
Check where those replies come from. Then start over with much less routing entries on both sides to understand the effect of each rule better. > > > I change of subject. I try to develop my application of router/concentrator > using socket API. Or rather RTnet API beacause I want to test latency on real > time. Separate topic, so please start a new thread. > I'm not sur that you are the good person who can answer me but perhaps > someone on the mailing list can help me. > I try to explain my step. > > On the windows box, I have a program wich send UDP packet on the network (I > can specify address and one port). It was created with linux API socket > (socket, bind, sendto...). for example, I can send packet to > 151.157.3.3:15000 or 151.157.3.4:15000... > > So on my board, I try to develop an application for receiving these packets > on the input interfaces and sending them to the destination host via the > fourth interface. > > In my main() function, > I have created 3 rt_dev_socket for each of my input interfaces. > I have bound this socket with the respective address of the NIC and a port (I > use the same port for each one). > And then I have created and start a real time task with rt_task_create and > rt_task_start (I pass a function round_trip to this function) > > In my round_trip() function, > I have initialize a struct sockaddr_in for my destination box. > after that, I get into an infinite while loop. > In this loop, I have initialized an fd_set variable (with FD_SET) for all my > input socket (I have created in main function). > Then, I call select function, and test if my socket are readable with > FD_ISSET. There is no select support in RTnet yet. Recent Xenomai does support it, but the (tiny) patch to enable RTnet to use it is not yet merged. > > But if I send data from my windows box to 151.157.3.3:15000 => ok that works > fine. > If I send data from my windows box to 151.157.3.4:15000 => that does not > work. > In fact, my first socket (bound to 151.157.3.3) is all the time readable but > never the other.. > > So I'm blocked. > So, I hope I have been clear in my explanations.. > If you have any suggestions or ideas.. I'm taker. Again, start with digging into the routing, start with simpler routing scenarios, and only enhance them once those simple approaches work. Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
