as promised, the IPv4 routing system of RTnet has been revised. You can find the testing version in the CVS. We are still lacking a documentation of the mechanisms (e.g. hash key generation and tweaking), but this will follow soon. So far a short overview:
o Routing is performed using two hash tables: the host routing and the network routing table. o Host routes describe direct links to known host targets by specifying the output device and the destination device address. RTcfg automatically creates the required entries during set-up. o Optional network routes (--enable-net-routing) define gateways which can be used to reach a distant network or host. Gateways are then resolved through the host routing table. o Resolution order: host routes --[not found]--> network routes --[found]--> host routes o To act as a gateway, a RTnet node has to be compiled with --enable-router. o If the loopback device is loaded, routes for every local IP address are automatically created now (some ported software may require this feature).
At this chance, the management tools has been revised, too. rtifconfig now only displays device related information [1]. The interface to the routing system has been moved to the new tool rtroute [2]. There is furthermore another brand-new tool called rtping - guess what it does?
Also the /proc interface has moved. You will now find any information under /proc/rtnet. Some modules like tdma and rtcfg still have to be extended to provide more /proc output.
Obviously, a lot of files have been touched over the last weeks. But all changes are tested and seem to be stable, please give it a try. We are planning to release a new version not before mid of May, so there should be enough time for further testing...
Greetings, Jan
PS: Has anyone experiences in creating man pages? Is he/she probably interested in writing such pages for the RTnet management tools? Contributions are very welcome!
[1] Exemplary output of rtifconfig: rteth0 Medium: Ethernet Hardware address: 00:80:AD:91:E3:4A IP address: 10.0.0.1 Broadcast address: 10.255.255.255 UP BROADCAST RUNNING MTU: 1500
rtlo Medium: Local Loopback
IP address: 127.0.0.1
UP LOOPBACK RUNNING MTU: 1500[2] Exemplary output of rtroute: Host Routing Table Hash Destination HW Address Device 01 127.0.0.1 00:00:00:00:00:00 rtlo 01 10.0.0.1 00:00:00:00:00:00 rtlo 03 10.0.0.3 00:50:FC:46:2C:2F rteth0 05 10.0.0.5 00:50:FC:59:C1:5B rteth0 08 10.0.0.8 00:80:AD:75:D3:34 rteth0 3F 10.255.255.255 FF:FF:FF:FF:FF:FF rteth0
Network Routing Table Hash Destination Mask Gateway 00 192.168.0.0 255.255.255.0 10.0.0.5
------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
