Hi all, i am trying multicast using mcproxy in bridge mode, in script I added pinstance A: "eth2" ==> "br-lan"; but getting error as failed to add interface. Does anyone have an idea to debug, please reply? Regards Aditya
On Wednesday, 16 September 2015 at 19:39:11 UTC+5:30 Sebastian Wölke wrote: > Hello Debarun, > > I started to investigate the issue and I realized it consumes more time > than I have at the moment. > I will work on it in the near future, but I can't do it now. > > Regards > sebastian > > > On Tuesday, September 15, 2015 at 9:43:26 AM UTC+2, Debarun Roychowdhury > wrote: >> >> Hi Sebastian, >> >> Any did you get the chance to investigate this issue? Any lead that we >> can follow? Its a bit urgent :-( >> >> Regards >> Debarun >> >> On Monday, September 14, 2015 at 12:10:05 PM UTC+5:30, Debarun >> Roychowdhury wrote: >>> >>> Hi Sebastian, >>> >>> Thank you for your reply. >>> >>> I have attached the following files: >>> mcproxy.conf -> configuration file for mcproxy >>> memleak_log.txt -> log of free memory, recorded after every 60 >>> seconds. >>> >>> There were no groups joined. The LAN and WAN have configured and the >>> board is booted up. The board is in idle condition. >>> >>> >>> >>> *root@OpenWrt:/# cat /proc/net/ip_mr_cache Group Origin Iif >>> Pkts Bytes Wrong Oifsroot@OpenWrt:/#* >>> >>> When mcproxy is killed, there is no further memory leak. >>> The mcproxy version being used is 1.1.0.y . >>> >>> It will be of great help if you can kindly provide us with some lead >>> towards this issue. >>> >>> Thanks and Regards >>> Debarun >>> >>> >>> On Sunday, September 13, 2015 at 5:08:22 AM UTC+5:30, Sebastian Wölke >>> wrote: >>>> >>>> Hello Debarun, >>>> >>>> sorry for the late answer. I can investigate the issue on monday. >>>> Could you send me your configuration file and could you describe me your >>>> network condition? Do you have many different groups, or do you have the >>>> same problem with just one group? >>>> >>>> Regards >>>> Sebastian >>>> >>>> >>>> On Saturday, September 12, 2015 at 9:20:00 PM UTC+2, Debarun >>>> Roychowdhury wrote: >>>>> >>>>> Hi Sebastian, >>>>> >>>>> Any update regarding this issue? >>>>> >>>>> Thanks and Regards, >>>>> Debarun >>>>> >>>>> On Thursday, September 10, 2015 at 5:54:57 PM UTC+5:30, Debarun >>>>> Roychowdhury wrote: >>>>>> >>>>>> Hi Sebastian, >>>>>> >>>>>> Hope you are doing well. >>>>>> >>>>>> I want to consult with you regarding an issue. With mcproxy running >>>>>> in my system I am observing a memleak. When I kill mcproxy , the leak is >>>>>> no >>>>>> longer observed. I tried mcproxy version 1.1.0 without any modification >>>>>> to >>>>>> the original source code, and I was able to see the memleak in that case >>>>>> as >>>>>> well. >>>>>> >>>>>> This issue is similar to the issue I found over the internet: >>>>>> https://forum.openwrt.org/viewtopic.php?id=59247 >>>>>> >>>>>> Please let me know if you have any solution related to this >>>>>> memleak issue. >>>>>> >>>>>> Thanks and Regards >>>>>> Debarun >>>>>> >>>>>> On Thursday, August 20, 2015 at 3:14:19 AM UTC+5:30, Sebastian Wölke >>>>>> wrote: >>>>>>> >>>>>>> Hello Debarun, >>>>>>> >>>>>>> the multicast router part (the group menagement of the domain - >>>>>>> querier) is handled by Mcproxy and the listener part (joining/leaving >>>>>>> groups on the upstream) is handled by the operating system. Thereby is >>>>>>> file >>>>>>> mld_receiver.cpp part of the multicast router part. It parses all >>>>>>> membership messages and sends these messages (indirect over the proxy >>>>>>> instance) to the querier (querier.cpp/hpp >>>>>>> <https://github.com/mcproxy/mcproxy/blob/master/mcproxy/src/proxy/querier.cpp> >>>>>>> >>>>>>> <https://github.com/mcproxy/mcproxy/blob/master/mcproxy/src/proxy/querier.cpp>) >>>>>>> >>>>>>> of the downstream, where the messages have been received. >>>>>>> >>>>>>> Regards, >>>>>>> Sebastian >>>>>>> >>>>>>> On Tuesday, August 18, 2015 at 7:51:17 AM UTC+1, Debarun >>>>>>> Roychowdhury wrote: >>>>>>>> >>>>>>>> Hi Sebastian, >>>>>>>> >>>>>>>> Thank you for your mail. I have implemented the same and now I >>>>>>>> am able to run mcproxy using both the configuration files and General >>>>>>>> Query >>>>>>>> is being sent out for both IGMP and MLD. >>>>>>>> >>>>>>>> I have one query. In bridge mode I see the IPv6 multicast data >>>>>>>> packets are being flooded to all interfaces even if I have not joined >>>>>>>> the >>>>>>>> IPv6 multicast group. But for IGMP it is working fine, I receive the >>>>>>>> packets only after joining the group. >>>>>>>> >>>>>>>> Can you let me know whether the join/leave is handled by mcproxy >>>>>>>> or by linux. I checked the mld_receiver.cpp file. I found its parsing >>>>>>>> the >>>>>>>> type of message and calling the "m_proxy_instance->add_msg()" function >>>>>>>> with >>>>>>>> appropriate arguments. What does it actually do? >>>>>>>> >>>>>>>> Regards >>>>>>>> Debarun >>>>>>>> >>>>>>>> On Saturday, August 8, 2015 at 2:24:48 AM UTC+5:30, Sebastian Wölke >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> ok, I have assumed the following: >>>>>>>>> The modifed proxy works fine in the IGMP only mode and in the MLD >>>>>>>>> only mode. >>>>>>>>> If you run both modes at the same time the proxy crashes. >>>>>>>>> Right? >>>>>>>>> >>>>>>>>> I think the proxy.cpp file looks quite good, you just duplicated >>>>>>>>> and renamed all necessary member variables of the class proxy. >>>>>>>>> >>>>>>>>> But I think you have forgot the following: >>>>>>>>> In the line >>>>>>>>> m_proxy_instances.insert(...); >>>>>>>>> >>>>>>>>> m_proxy_instance is a map with the table_number as key. You might >>>>>>>>> make the table_number global. I think your key has the value 1 for >>>>>>>>> the IMGP >>>>>>>>> instance as well as for the MLD instance (this would result in an >>>>>>>>> undefined >>>>>>>>> behaviour). >>>>>>>>> >>>>>>>>> I hope this fixes your error. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Sebastian >>>>>>>>> >>>>>>>>> On Friday, July 24, 2015 at 9:31:54 AM UTC+1, Debarun Roychowdhury >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> We have a device which can act in router mode as well as bridge >>>>>>>>>> mode. There is a specification which requires to send IGMPv2 and >>>>>>>>>> MLDv2 >>>>>>>>>> General Query in bridge mode. Also the specification requires that >>>>>>>>>> in >>>>>>>>>> gateway mode the device should not proxy.I have the following >>>>>>>>>> queries: >>>>>>>>>> >>>>>>>>>> 1. The version of mcproxy being used in the distribution is >>>>>>>>>> 1.1.0.y . From mcproxy website we found that till version 0.1.4 >>>>>>>>>> there was >>>>>>>>>> support for generation of IGMPv2 General Query. From 1.0.0 sending >>>>>>>>>> of >>>>>>>>>> IGMPv2 General Query is not supported , only IGMPv3 general query >>>>>>>>>> can be >>>>>>>>>> sent. Similarly for MLD ,from version 1.1.0 sending of MLDv2 General >>>>>>>>>> Query >>>>>>>>>> is supported only, and not MLDv1. But from the specification we need >>>>>>>>>> to >>>>>>>>>> send IGMPv2 query and MLDv2 query. What do you suggest we do to >>>>>>>>>> satisfy >>>>>>>>>> this requirement? The latest mcproxy source has support for sending >>>>>>>>>> MLDv2 >>>>>>>>>> general query but not IGMPv2 general query. Do we need to port the >>>>>>>>>> feature >>>>>>>>>> from older version to support sending of IGMPv2 general query? >>>>>>>>>> >>>>>>>>>> 2. In the specification it is specified that the device should >>>>>>>>>> not perform IGMPv2/3 proxy in the gateway mode. Can you please >>>>>>>>>> suggest any >>>>>>>>>> changes in code/configuration to prevent mcproxy from performing >>>>>>>>>> IGMP proxy? >>>>>>>>>> >>>>>>>>>> 3. Can you suggest any changes in the configuration of mcproxy to >>>>>>>>>> make it run in bridge mode? The requirement is to send IGMPv2 and >>>>>>>>>> MLDv2 >>>>>>>>>> General Query for snooping. >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> Debarun Roychowdhury >>>>>>>>>> >>>>>>>>> -- You received this message because you are subscribed to the Google Groups "Multicast Proxy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/multicast-proxy/db6e152b-4926-49af-be15-3cec425d2ae8n%40googlegroups.com.
