252
edits
Router - DLINK 320B: Difference between revisions
→Notes: updating, references to ancient pre-Z1 modems
(→Default Settings: added section on how to poke the hole etc) |
(→Notes: updating, references to ancient pre-Z1 modems) |
||
|
==Notes==
*AAISP ships these devices for use as straight ethernet modems. Although they are capable of working as (buggy) routers, AA pre-configures them to work in bridge mode only, that is, in simple PPPoE modem-only mode, not operating as routers.
*If you reset them to factory settings using the pin-in-hole technique, then with their factory defaults they <b>will not work at all</b> as straight PPPoE ethernet modems. Their configuration <b>must</b> be altered before use. Ask [https://www.aaisp.net.uk/support.html AA support] for help with this or see instructions below.
*No per-user or per-line login or password configuration is required. ISP account or line login and password info is configured in your <i>router</i>, the DLink modem doesn’t need these values.
*They do support 1500 MTU (unlike the [[Router - ZyXEL_P660R-D1]]).
*Their web interface is quite insecure and in ‘router’ mode they have various critical security bugs, which is why we do
*Chipset: The currently shipping DSL-320B-Z1 units (at the time of writing, December 2017), and those shipped from approx 2015 onwards, use an old but capable MediaTek
*Incorrect manufacturer’s defaults: The default settings shown in the router’s web admin user interface show defaults that are quite unsuitable. It is important to enable the ‘bitswap’ option for best reliability and performance in most cases. (See [http://forum.kitz.co.uk/index.php?topic=13296.0 discussion of bitswap].) This default seems so odd that perhaps this is just a bug in the DLink software and the bitswap feature really defaults to ‘enabled’. (Needs a volunteer to do reliability testing to compare the two cases.)
=== Initial setup using web admin i/f for the DSL-320B-Z1 ===
(Referring to the DSL-320B-Z1.)
<p>▼
After a reset to factory settings you will need to make the following changes using the web admin user interface (factory default http://192.168.1.1, your own ip address set to something suitable in that same /24 subnet, username=admin, password=admin)
‘ADVANCED’ (top horiz navigation bar) > Advanced ADSL (lhs vertical navigation list)▼
<dt>‘SETUP’ (top horiz navigation bar) > Bridge Mode</dt><dd>
<ul>
<li>1483 Bridged IP LLC - Note: PPPoEoEoA + RFC1483[=RFC2684] Bridged+VC_MUX does not seem to work with BTW</li></ul></dd></dl>
The default settings shown in the router’s web admin user interface show defaults that are quite unsuitable. It is important to enable the ‘bitswap’ option for best reliability and performance in most cases. (See [http://forum.kitz.co.uk/index.php?topic=13296.0 discussion of bitswap].) This default seems so odd that perhaps this is just a bug in the DLink software and the bitswap feature really defaults to ‘enabled’. (Needs a volunteer to do reliability testing to compare the two cases.) These settings need to be configure as follows:
<dl>
<dt>
▲
<ul>
<li>ANNEX A/I/J/L/M</li>
<li>Bitswap -
<li>SRA -
''Performance tip for long lines:'' If you have an extremely long phone line (>60 dB downstream attenuation) and you can use ADSL2+, it is worthwhile experimenting with setting the DSL mode/standard option to ‘ADSL 2’ (only) in the above list of options, that is, taking ADSL2+ out of the list of allowed standards, as opposed to allowing the modem to use ADSL2+, to see if this restriction gives a performance improvement. It will be a long process to get a meaningful comparison with take many restarts and many tests to confirm any possible performance difference between allowing and disallowing ADSL2+. If in any doubt enable ADSL2+ ie ADSL1/ADSL2/ADSL2+ ‘auto’ mode where the modem will use ADSL2+ (which can support much higher best-case speeds than ADSL2) if the exchange DSLAM or MSAN supports ADSL2+ too.
| |||