olsr.org-开源

  • k7_137511
    了解作者
  • 634.6KB
    文件大小
  • org-开源
    文件格式
  • 0
    收藏次数
  • VIP专享
    资源类型
  • 0
    下载次数
  • 2022-04-13 06:57
    上传日期
olsrd是优化链接状态路由(OLSR,RFC3626)协议的实现。 该实现可通过使用可加载插件来扩展。 有关更多信息,请访问http://www.olsr.org。 这个sf.net页面已经过时了! 请访问www.olsr.or
olsrd-0.5.6.tar.gz
内容介绍
BASIC MULTICAST FORWARDING PLUGIN FOR OLSRD by Erik Tromp (erik.tromp@nl.thalesgroup.com, erik_tromp@hotmail.com) Version 1.5.3 1. Introduction --------------- The Basic Multicast Forwarding Plugin floods IP-multicast and IP-local-broadcast traffic over an OLSRD network. It uses the Multi-Point Relays (MPRs) as identified by the OLSR protocol to optimize the flooding of multicast and local broadcast packets to all the hosts in the network. To prevent broadcast storms, a history of packets is kept; only packets that have not been seen in the past 3-6 seconds are forwarded. 2. How to build and install --------------------------- Download the olsr-bmf-v1.5.3.tar.gz file and save it into your OLSRD base install directory. Change directory (cd) to your OLSRD base install directory. At the command prompt, type: tar -zxvf ./olsr-bmf-v1.5.3.tar.gz then type: make build_all followed by: make install_all Next, turn on the possibility to create a tuntap interface (see also /usr/src/linux/Documentation/networking/tuntap.txt): mkdir /dev/net # if it doesn't exist already mknod /dev/net/tun c 10 200 Set permissions, e.g.: chmod 0700 /dev/net/tun To configure BMF in OLSR, you must edit the file /etc/olsrd.conf to load the BMF plugin. For example, add the following lines: LoadPlugin "olsrd_bmf.so.1.5.3" { # No PlParam entries required for basic operation } 3. How to run ------------- After building and installing OLSRD with the BMF plugin, run the olsrd daemon by entering at the shell prompt: olsrd Look at the output; it should list the BMF plugin, e.g.: ---------- LOADING LIBRARY olsrd_bmf.so.1.5.3 ---------- OLSRD Basic Multicast Forwarding (BMF) plugin 1.5.3 (Feb 24 2008 17:58:02) (C) Thales Communications Huizen, Netherlands Erik Tromp (eriktromp@users.sourceforge.net) Checking plugin interface version: 5 - OK Trying to fetch plugin init function: OK Trying to fetch parameter table and it's size... Sending parameters... "NonOlsrIf"/"eth0"... NonOlsrIf: OK Running plugin_init function... OLSRD Basic Multicast Forwarding (BMF) plugin: opened 5 sockets ---------- LIBRARY olsrd_bmf.so.1.5.3 LOADED ---------- 4. How to check if it works --------------------------- Enter the following command on the command prompt: ping 224.0.0.1 All OLSR-BMF hosts in the OLSR network should respond. For example, assume we have three hosts, with IP addresses 192.168.151.50, 192.168.151.53 and 192.168.151.55. On host 192.168.151.50 we enter the following ping command: root@IsdbServer:~# ping 224.0.0.1 PING 224.0.0.1 (224.0.0.1) 56(84) bytes of data. 64 bytes from 192.168.151.50: icmp_seq=1 ttl=64 time=0.511 ms 64 bytes from 192.168.151.53: icmp_seq=1 ttl=64 time=4.67 ms (DUP!) 64 bytes from 192.168.151.55: icmp_seq=1 ttl=63 time=10.7 ms (DUP!) 64 bytes from 192.168.151.50: icmp_seq=2 ttl=64 time=0.076 ms 64 bytes from 192.168.151.53: icmp_seq=2 ttl=64 time=1.23 ms (DUP!) 64 bytes from 192.168.151.55: icmp_seq=2 ttl=63 time=1.23 ms (DUP!) 64 bytes from 192.168.151.50: icmp_seq=3 ttl=64 time=0.059 ms 64 bytes from 192.168.151.53: icmp_seq=3 ttl=64 time=2.94 ms (DUP!) 64 bytes from 192.168.151.55: icmp_seq=3 ttl=63 time=5.62 ms (DUP!) 64 bytes from 192.168.151.50: icmp_seq=4 ttl=64 time=0.158 ms 64 bytes from 192.168.151.53: icmp_seq=4 ttl=64 time=1.14 ms (DUP!) 64 bytes from 192.168.151.55: icmp_seq=4 ttl=63 time=1.16 ms (DUP!) We can see the response from the originating host (192.168.151.50) (it is normal behaviour for hosts sending multicast packets to receive their own packets). We can also see the responses by the other hosts (correctly seen as DUPlicates by ping). Note: when using an older version of ping than the standard from iputils-20020927, as found in most current Linux distributions, you may want to test BMF by specifying the output interface to the ping command: ping -I bmf0 224.0.0.1 Older versions of 'ping' (e.g. as found in iputils-20020124) may bind to the autoselected source address, which may be incorrect. Since BMF re-uses one of the existing IP addresses for the "bmf0" network interface, the older-version ping command may 'autobind' to the wrong interface. See also the note in the iputils-20020927/RELNOTES file: "* Mads Martin J�rgensen <mmj@suse.de>: ping should not bind to autoselected source address, it used to work when routing changes. Return classic behaviour, option -B is added to enforce binding." 5. How does it work ------------------- In the IP header there is room for only two IP-addresses: * the destination IP address (in our case either a multicast IP-address 224.0.0.0...239.255.255.255, or a local broadcast address e.g. 192.168.1.255), and * the source IP address (the originator). For optimized flooding, however, we need more information. Let's assume we are the BMF process on one host. We will need to know which host forwarded the IP packet to us. Since OLSR keeps track of which hosts select our host as MPR (see the olsr_lookup_mprs_set(...) function), we can determine if the host that forwarded the packet, has selected us as MPR. If so, we must also forward the packet, changing the 'forwarded-by' IP-address to that of us. If not, we do not forward the packet. Because we need more information than fits in a normal IP-header, the original packets are encapsulated into a new IP packet. Encapsulated packets are transported in UDP, port 50698. The source address of the encapsulation packet is set to the address of the forwarder instead of the originator. Of course, the payload of the encapsulation packet is the original IP packet. For an exact specification of the encapsulation format, refer to paragraph 10 below. For local reception, each received encapsulated packets is unpacked and passed into a tuntap interface which is specially created for this purpose. There are other flooding solutions available that do not use encapsulation. The problem with these solutions is that they cannot prevent duplicates of forwarded packets to enter the IP stack. For example, if a host is receiving flooded (unencapsulated, native IP) packets via two MPR hosts, there is no way to stop the reception of the packets coming in via the second MPR host. To prevent this, BMF uses a combination of encapsulated flooding and local reception via a tuntap interface. Here is in short how the flooding works (see also the BmfEncapsulatedPacketReceived(...) function; details with respect to the forwarding towards non-OLSR enabled hosts are omitted): On all OLSR-enabled interfaces, setup reception of packets on UDP port 50698. Upon reception of such a packet: If the received packet was sent by myself, drop it. If the packet was recently seen, drop it. Unpack the encapsulated packet and send a copy to myself via the TunTap interface. If I am an MPR for the host that forwarded the packet to me, forward the packet to all OLSR-enabled interfaces *including* the interface on which it was received. 6. Advanced configuration ------------------------- All configuration of BMF is done via the "LoadPlugin" section in the /etc/olsrd.conf file. The following gives an overview of all plugin parameters that can be configured: LoadPlugin "olsrd_bmf.so.1.5.3" { # Specify the name of the BMF network interface. # Defaults to "bmf0". PlParam "BmfInterface" "mybmf0" # Specify the IP address and mask for the BMF network interface. # By default, the IP address of the first OLSR interface is copied. # The default prefix length is 32. PlParam "BmfInterfaceIp" "10.10.10.234/24" # Enable or disable the flooding of local broadcast packets # (e.g. packets with IP destination 192.168.1.255). Either "yes" # or "no". Defaults to "yes". PlParam "DoLocalBroadcast" "no" # Enable or disable the capturing packets on the OLSR-enabled # interfaces (in promiscuous mode). Either "yes" or "no". Defaults # t
评论
    相关推荐
    • Weather Report .NET
      基于Google Weather API的程序。支持中文,英文,德文。.NET3.5做的,但是,由于Google问题,不知道是否在内地可以使用?无论怎么样,可以测试下。...国外下载地址:http://www.box.net/shared/d6ct9jlpyf
    • .net远程
      使用http管道的.net远程
    • .net Excel NPOI
      很多人可能对NPOI还很陌生,别担心,通过本教程你将对NPOI有进一步的认识和理解 http://tonyqus.sinaapp.com/npoi-1-2-1%e6%95%99%e7%a8%8b
    • aspx后门.net
      密码:upx8 原文网址:http://upx8.com/article.asp?id=275
    • system.net.http.dll
      system.net.http.dll文件 2016 版本2.2.22.0 186K DDL文件
    • .net学习资料
      .net插件框架。ado.nethttp协议,wcf,webapi,依赖注入,并发,死锁等等
    • .NET HTTP 请求服务接口
      .NET 常用的 HTTP 请求服务的方法 类
    • System.Net.Http.Formatting
      System.Net.Http.Formatting
    • Rss.Net类库
      开源项目Rss.Net 类库http://www.rssdotnet.com
    • System.Net.Http.dll下载
      System.Net.Http.dll下载