Changes between Version 136 and Version 137 of Startup

Timestamp:

02/04/12 19:14:26 (12 years ago)

Author:

woelke

Comment:

--

Startup

@@ -7 +7 @@
 
 === Tables (IPv4 | IPv6)===
-The following tables can be found under the path ''/proc/net/''.The ipv6 tables show the same content like the ipv4 tables. But they are only available if you configure and compile your own Linux-Kernel. For more details see [wiki:Kernel here].
+The following tables can be found under the path ''/proc/net/''.The IPv6 tables show the same content like the IPv4 tables. But they are only available if you configure and compile your own Linux-Kernel. For more details see [wiki:Kernel here].
 * igmp | igmp6
- * This table shows the multicast group subscriptions of your system for every interface. The multicast group addresses are written in hexadecimal and network byte order (only for IPv4). For example an ip address like FEDCBA98 means 152.186.220.254. The mcproxy subscribe a multicast group on the upstream interface for every subscription heard on the downstream side. This can be seen in the igmp table.
+ * This table shows the multicast group subscriptions of your system for every interface. The multicast group addresses are written in hexadecimal and network byte order (only for IPv4). For example an IP address like FEDCBA98 means 152.186.220.254. The mcproxy subscribe a multicast group on the upstream interface for every subscription heard on the downstream side. This can be seen in the igmp table.
 * ip_mr_vif | ip6_mr_vif
  * This table shows interfaces which are registered to forward multicast traffic. These interfaces are identified by an virtual interface index (vif). All interfaces used by the mcproxy registered here.
@@ -21 +21 @@
 }}}
 
-  RP-Filter::  The Reverse Path Filter check the source IP of each packet received on an interface against the routing table. If the best route for the source IP address does not use the same interface that the packet was received on the packet is dropped. If the multicast path is not similar to the ip path, the flag musst be turned off. This is imported for the multicast client and for the mcproxy itself and can be done in the following file:
+  RP-Filter::  The Reverse Path Filter check the source IP of each packet received on an interface against the routing table. If the best route for the source IP address does not use the same interface that the packet was received on the packet is dropped. If the multicast path is not similar to the IP path, the flag must be turned off. This is imported for the multicast client and for the mcproxy itself and can be done in the following file:
 {{{
  /proc/sys/net/ipv4/conf/<interface>/rp_filter
@@ -97 +97 @@
  eth2 ==> eth3
 }}}
-Because you cannot run the mcproxy more than one time (see MRT-Flag). In this example we used a tunnel interface as second downstream. This is legitimate but you musst ensure that the tunnel support multicast. An normal ip2ip tunnel doesn't support this (use a [http://www.linuxdoc.org/HOWTO/Adv-Routing-HOWTO/lartc.tunnel.gre.html gre] or tap tunnel). 
+Because you cannot run the mcproxy more than one time (see MRT-Flag). In this example we used a tunnel interface as second downstream. This is legitimate but you must ensure that the tunnel support multicast. An normal ip2ip tunnel doesn't support this (use a [http://www.linuxdoc.org/HOWTO/Adv-Routing-HOWTO/lartc.tunnel.gre.html gre] or tap tunnel). 
 
 === 3. Hierarchization ===
 [[Image(szenarios2b.png, 160px, right)]]
-You can concatenate multicast proxies and create a shared tree. But If you use IPv4 and the multicast path is not similar to the ip path, you have to turn off the rp_filter (see RP-Filter). The mcproxy can do it automatically with the following command:
+You can concatenate multicast proxies and create a shared tree. But If you use IPv4 and the multicast path is not similar to the IP path, you have to turn off the rp_filter (see RP-Filter). The mcproxy can do it automatically with the following command:
 {{{
  sudo mcproxy -f -c <configfile>