OK, the ADSL configuration doesn't need an extra line at all, it's the same as the fibre version. Here a few tips on how I did mine - do the first few steps (backup current configuration and do the text dump) whilst still on line -
As mentioned by 11110_110, make a back up of your existing configuration in case things go wrong.
Login using
http://192.168.1.254/expert_user.html and then go to >Advanced Setup>Management>Settings>Backup then click <Backup Settings> this will prompt you to save to the default backupsettings.conf and save it in an appropriate folder.
Now enter
http://192.168.1.254/dumpcfgdynamic.cmd in the browser and press enter, this should give you the mdm text dump of the config.
Select all and copy it to a plain text file using a plain text editor (eg. Notepad), you can choose a name maybe textconfig.txt - it doesn't have to have the extension .conf . By using the .txt extension you can make sure that when saved you can readily open it in a plain text editor. Don't use Word or similar, it will introduce various formatting code that will mess up the configuration file.
Personally, I delete the leading space before <?xml version="1.0"?> and the space, blankline and size info immediately after </DslCpeConfig> before saving. Then make a copy of this file to play around with and edit, call it say wanpingconfig.txt if that's what you are going to create.
Look for the line </WANPPPConnection> you'll find it towards the end of the file. You then need to insert the following lines immediately before this line. In my ADSL version it's immediately after <X_SAGEM_COM_PPPoA_Rspping_enable>FALSE</X_SAGEM_COM_PPPoA_Rspping_enable>
Insert
<X_BROADCOM_COM_FirewallException instance="1">
<Enable>TRUE</Enable>
<FilterName>ICMP</FilterName>
<Protocol>ICMP</Protocol>
</X_BROADCOM_COM_FirewallException>
<X_BROADCOM_COM_FirewallException nextInstance="2" ></X_BROADCOM_COM_FirewallException>
so this section of the file should now read -
<X_SAGEM_COM_PPPoA_Rspping_enable>FALSE</X_SAGEM_COM_PPPoA_Rspping_enable>
<X_BROADCOM_COM_FirewallException instance="1">
<Enable>TRUE</Enable>
<FilterName>ICMP</FilterName>
<Protocol>ICMP</Protocol>
</X_BROADCOM_COM_FirewallException>
<X_BROADCOM_COM_FirewallException nextInstance="2" ></X_BROADCOM_COM_FirewallException>
</WANPPPConnection>
Save the file.
Now, because uploading new settings causes the modem/router to reboot, it's advisable to do this offline so if there's an error in the file and it's not uploaded, the 2704n still reboots, so you are losing sync during this process, not a good idea on troublesome ADSL lines. So login tothe 2704n, click Disconnect on the Home page to drop the PPP session, wait about 30 seconds and power off the 2704n. Wait about another 30 seconds and then unplug it from the line. (Leave it unplugged from the line until your new config is loaded and the 2704n has finished rebooting).
Once unplugged from the line, you can power up the 2704n and login as expert_user. Go to >Advanced Setup>Management>Settings>Update.
First try a test with the original unedited "textconfig.txt" file which should upload without a problem. Browse to that file and click <Update Settings>
If the file is accepted it will tell you it's updating and will take about 2 minutes. If it fails, check the file for the spaces and lines that should have been deleted.
If OK, once this has completed, login again as expert_user and again go to >Advanced Setup>Management>Settings>Update but this time browse to your "wanpingconfig.txt" and click <Update Settings>. If it fails, check the file for errors.
If OK, once complete login to it and then connect the line to regain sync and PPP session.
You can do a quick check that it will respond to pings using the following command
http://users.plus.net/@gateway_custom?debug-ip=yes If the diagnostic check completes with the last line containing your IP address, voilà. You should now be able to set up a BQM.
For anyone that tries this, let us know how you got on.
if I change the config madly... change the MTU to 1492 (for ADSL users) ?
