From owner-freebsd-net@freebsd.org Sat Jan 13 17:38:08 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49AEAE7520B for ; Sat, 13 Jan 2018 17:38:08 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D397A6E840 for ; Sat, 13 Jan 2018 17:38:07 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w0DHbjo8016004 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 13 Jan 2018 18:37:46 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: georg@bege.email Received: from [10.58.0.4] (dadv@[10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w0DHbfD8010979 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 14 Jan 2018 00:37:41 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Support for ATM bridging (RFC1483/2684) in FreeBSD? To: georg@bege.email, freebsd-net@freebsd.org References: <3032eab4-8c07-b701-83ca-d07ffd17ee11@bege.email> From: Eugene Grosbein Message-ID: <5A5A43E5.50902@grosbein.net> Date: Sun, 14 Jan 2018 00:37:41 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <3032eab4-8c07-b701-83ca-d07ffd17ee11@bege.email> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=4.2 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_24_48, LOCAL_FROM,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 2.0 DATE_IN_FUTURE_24_48 Date: is 24 to 48 hours after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: **** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 17:38:08 -0000 14.01.2018 0:27, Georg Bege wrote: >> It depends on hardware you have. Do you have some internal PCI ATM adapter or external device? > Thanks for your response. > Well I have come to the believe that no special hardware is required for > this, basically they somehow seem to route this via PPPoE (or at least > that's what I think). > Basically you establish an PPPoE connection and then you somehow must > acquire an virtual ATM device (which carries VCR/VCI.. and encapsulates > this) much like VDSL does with vlan tagging.... > > Im not sure if Im 100% correct, but for example I can establish the > internet connection with just an normal ADSL2+ Annex J compatible Modem > and PPPoE works too. > What I dont get without this bridging stuff is the IPTV stream, it seems > that on this bridged device an dhcp query is necessary in order to get > access to the multicast net. So, you already have ADSL2+ modem with ethernet interface acting as bridge for PPPoE traffic and you use FreeBSD to establish PPPoE session, right? And what is "IPTV stream" exactly? Is it just IP multicast somehow encapsulated into VCI or something else?