A Dimarts 27 Març 2007 13:10, M. Koehrer va escriure: > Hi Leo, > > I did something similar. > My approach is not really beautiful but I works nice. > I call rtroute solicit in a sh-loop: > > for (( i=0; i<255; i++)); do > rtroute solicit 192.168.1.$i dev rteth0 > done > > This is fairly fast and works! > However, a "smoother" way to do that (directly in rtroute) would be > actually better... > > You can see the routing list by calling rtroute without arguments.
thanks Mathias, it really works nice. Maybe adding some parameters in the rtconf file with the number of nodes, or something similar would be better. To think it. Regards, Leo > > > Hi, > > > > I have modified the rtnet script adding a notdma option to have a > > configuration without tdma. > > > > All is working but I have a doubt. My configuration is having my eth0 as > > 192.168.1.3 and other node with 192.168.1.4. I add manually: > > rtroute solicit 192.168.1.4 dev rteth0 > > > > Howeber I thought if I would like to have a more generic approach to add > > all > > > > the nodes of a subnet with: > > > > ulises:/usr/local/rtnet# sbin/rtroute add 192.168.1.0 netmask > > 255.255.255.0 gw > > 192.168.1.3 > > > > but I have this message: > > ioctl: Inappropriate ioctl for device > > > > so the doubt is if I have an heterogeneous net have I to add each node > > specifically or could I to add it generally? > > > > Regards, > > > > Leo ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
