[OpenWrt-Devel] [PATCH 2/4] lantiq: base-files: drop the dsl tone settings

Daniel Golle daniel at makrotopia.org
Thu Dec 3 04:46:05 EST 2015


On Thu, Dec 03, 2015 at 09:07:22AM +0100, Andre Heider wrote:
> Hi,
> On Wed, Dec 2, 2015 at 10:07 PM, Daniel Schwierzeck
> <daniel.schwierzeck at gmail.com> wrote:
> > I think the removal of the tone setup in r46920 should be reverted. It
> > is still the only way to exactly control which pilot tones are sent by
> > the DSL firmware. I would not trust the default setting of the
> > dsl_cpe_control daemon. Especially in Germany you may not send a V43
> > tone on a Deutsche Telekom port according to 1TR112 specification, only
> > B43 is allowed.
> works for me, but then I'm not an expert on DSL internals.
> On the other side, how do vendor firmwares handle that? It's been some
> time I looked at one, but I don't remember seeing a dsl tone setting.

Usually by differentiating firmware by target markets.
Ie. depending on where you buy the device, you end up with different
xDSL settings, similar to how allowed wifi channels are handled by most
vendors as well.
T-Com-land has always been a bit special in many regards and there
are only very few xDSL-cabable devices being sold on the streets.
VDSL2 made things a bit easier and if you are on a VDSL2 port, things
may just work regardless.
However, ADSL2+ is still being used as well, especially in rural areas,
and depending on the condition of last-mile copper-pair also as a
fall-back whenever the line is too bad for VDSL2.

I reckon in order to support such things nicely in OpenWrt, we'll need
something like by-country-by-carrier config templates, so users will
only have to select their carrier+ISP and enter their credentials.

In technically more advanced areas of the world, law-makers have
decided to enforce a clean separation of access-network-infratructure
(xDSL, DOCSIS, GPON, ...) and ISP services.
In those markets a user will have to select her access-network as well
as ISP, as all combinations on both layers are possible.
Having a schema to cover-them-all would be nice, this is as far as I
got for now:

infrastructure-specific parameters:
 * xDSL tones and annex
 * 802.1Q VLAN(s) for VDSL
 * MTU
 * infrastructure may provide IPTV (multicast) or VoIP services
   idenpendently of the ISP chosen.

isp-specific parameters:
 * 802.1Q VLAN(s) for VDSL may differ for ISPs as well
 * layer-2 management protocol: DHCP, PPPoE, PPPoL2TP, ...
 * authentication mode: CHAP/PAP for PPP-based, 802.1X, ...
 * addressing mode: v4-only, dual stack, DS-lite, ...
 * multicast mode
 * DNSsec?
 * IPsec?
 * IP mobility?
 * ...


openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list