From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Package updates in progress Date: Mon, 12 Apr 2021 11:21:56 +0100 Message-ID: <07030E10-1819-4684-9F12-5959AAC247E3@ipfire.org> In-Reply-To: <65B38DCA-31D2-479D-95E1-48267205C270@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8742687894560351623==" List-Id: --===============8742687894560351623== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 11 Apr 2021, at 23:30, Jon Murphy wrote: >=20 > Hi Adolf >=20 > Thank you for looking. >=20 >> It seems like the original creater now has the repository in Bitbucket (At= lassian) and to get access to the downloads you have to have an account with = atlassian. Without the account you can't even see what is available. ie is th= ere a version 1.11 or not. >=20 > I just tried to login to BitBucket to see mdns-repeater but BitBucket won= =E2=80=99t allow it! Grrrrrr! I see this message: > "We can't let you see this page > To access this page, you may need to log in with another account. You can a= lso return to the previous page or go back to your dashboard." >=20 >=20 > And thank you for posting the notes from the kennylevinsen fork. One of th= e problems may be the same thing I just came across. >=20 >> The first is most interesting. Say you have two networks bound together wi= th site-to-site tunnels, repeating mDNS over the tunnel... And there are Chro= mecasts, or Apple TV's at both ends. Even if you had firewall rules to block = traffic, the devices would still show up (albeit be defective) on the opposit= e network. >=20 >=20 > I turned off ALL of my firewall rules but with mdns-repeater running via /e= tc/rc.d/init.d/mdns-repeater start and with mdns-repeater green0 blue0 set, I= can still see and access everything from BLUE to GREEN. =20 >=20 > Stopping via /etc/rc.d/init.d/mdns-repeater stop causes everything to got b= ack to normal (no access from BLUE to GREEN). It like mdns-repeater allows a= n easy path from BLUE to GREEN. =20 >=20 > I=E2=80=99m still testing this to be sure. >=20 > I wonder if anyone else is using mdns-repeater=E2=80=A6 I am :) It has been working fine so far. >=20 > Jon >=20 >> On Apr 11, 2021, at 4:53 PM, Adolf Belka wrote: >>=20 >> Hi Jon, >>=20 >>=20 >> On 11/04/2021 21:09, Jon Murphy wrote: >>> Hey Adolf! >>> Can mdns-repeater (add-on) be added to the list? >>> [root(a)ipfire ~]# mdns-repeater -h >>> mDNS repeater (version 1.10) >>> Copyright (C) 2011 Darell Tan >>> I think version 1.10 (the current IPFire add-on version) is a few years o= ld. There may be a version 1.11. >> Current version is 1.10. It was created as an addon in Jan 2018. It seems = like the original creater now has the repository in Bitbucket (Atlassian) and= to get access to the downloads you have to have an account with atlassian. W= ithout the account you can't even see what is available. ie is there a versio= n 1.11 or not. >>=20 >> There is a version 1.11 in a forked repository (kennylevinsen/mdns-repeate= r) but whether that is worth having or not I can't tell. It was created in De= c 2016 and had 6 commits since then but no new release. It was forked from th= e geekman version from Sep 2011 but as it is now in Bitbucket I can't find an= ything more out about it. >>=20 >> This is what was listed as the changes for the 1.11 kennylevinsen fork:- >>=20 >> -------------------------------------------------------- >> Blacklist feature added (16 blacklisted subnets allowed). >> Socket limit increased to 16 sockets, moved to #define. >>=20 >> The first is most interesting. Say you have two networks bound together wi= th site-to-site tunnels, repeating mDNS over the tunnel... And there are Chro= mecasts, or Apple TV's at both ends. Even if you had firewall rules to block = traffic, the devices would still show up (albeit be defective) on the opposit= e network. >>=20 >> The new blacklist flag allows you to filter such devices out by specifying= their subnet (or individual addresses, although having such "private" device= s on their own subnet might be a good idea). >>=20 >> Example: >> # Repeat mDNS packets between eth1 and vti0, while ignoring packets from 1= 72.20.20.0/24 >> mdns-repeater -b 172.20.20.0/24 eth1 vti0 >> -------------------------------------------------------- >>=20 >> So the question is do these additions warrant an update to this forked rep= ository. >>=20 >> Regards, >> Adolf >>=20 >>=20 >>> I haven=E2=80=99t located the "official" website so I am not sure=E2=80=A6 >>> I can help test. >>> Jon >>>> On Apr 11, 2021, at 9:02 AM, Adolf Belka > wrote: >>>>=20 >>>> Hi all, >>>>=20 >>>> For information I am working on the following package updates:- >>>> cups >>>> cups-filters >>>> expat >>>> glib >>>> lua >>>> meson >>>>=20 >>>> I will hold submitting the patches until after Core Update 156 is releas= ed for testing. >>>>=20 >>>> Regards, >>>>=20 >>>> Adolf. >=20 --===============8742687894560351623==--