SixXS::Sunset 2017-06-06

ecmh sends no data to the upstream interface
[de] Shadow Hawkins on Monday, 28 February 2005 07:06:23
Hi, i have a problem while using ecmh. If i send multicast data ecmh does not forward this traffic to the upstream interface, receiving multicast data works fine. I've startet echm with "-i 6in4 -v -p". The statistics looks like this: Interface: eth0 Index number : 2 MTU : 1500 Interface Type : Ethernet (1) Link-local address : fe80::204:75ff:fe97:ccfb Global unicast address : 2001:6f8:1368::1 MLD version : v2 Packets received : 8701 Packets sent : 7156 Bytes received : 946726 Bytes sent : 3647825 ICMP's received : 9 ICMP's sent : 2 Interface: eth1 Index number : 3 MTU : 1500 Interface Type : Ethernet (1) Link-local address : :: Global unicast address : :: MLD version : none Packets received : 12212 Packets sent : 19 Bytes received : 8769391 Bytes sent : 1400 ICMP's received : 0 ICMP's sent : 19 Interface: 6in4 Index number : 5 MTU : 1280 Interface Type : sit (776) Link-local address : fe80::c0a8:1 Global unicast address : 2001:6f8:900:48d::2 MLD version : v2 Packets received : 12120 Packets sent : 9 Bytes received : 8510618 Bytes sent : 804 ICMP's received : 2 ICMP's sent : 9 *** Interface Dump (end - 3 interfaces) eth0 is my lan. eth1 is another lan and also the connection to the ipv4 router. 6in4 is my connection to sixxs. Routes look like this: 2001:6f8:900:48d::/64 via :: dev 6in4 metric 256 mtu 1280 advmss 1220 2001:6f8:1368::/64 dev eth0 metric 256 mtu 1500 advmss 1220 2001:6f8:1368:1::/64 dev eth1 metric 256 mtu 1500 advmss 1220 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220 fe80::/64 via :: dev 6in4 metric 256 mtu 1280 advmss 1220 ff00::/8 dev 6in4 metric 255 mtu 1280 advmss 1220 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220 default via 2001:6f8:900:48d::1 dev 6in4 metric 1024 mtu 1280 advmss 1220 (I've compiled ecmh static using a Debian 3.1)
ecmh sends no data to the upstream interface
[ch] Jeroen Massar SixXS Staff on Monday, 28 February 2005 15:53:09
You should not specify the -i option when the upstream is another ecmh. The upstream option is only when the upstream is a full multicast router, thus one doing PIM and other tricks. When such a machine sees ecmh's MLD query it will not act as a router anymore and as such will not allow your local ecmh to join any groups. Note also that ecmh can only distribute data inside a domain of ecmh's, but not to a PIM capable router. This will be solved in the next version though.
ecmh sends no data to the upstream interface
[de] Shadow Hawkins on Tuesday, 01 March 2005 01:28:15
Thank you for your answers! This explains many and answers most of my questions. Sorry for "bothering" you with my last two eMails. I haven't read your Answer here until now.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker