That string doesn't seem to exist in the B030SP06_unlocked firmware. However there is a line starting:
<WANPTMLinkConfig Enable="1"
which seems to confirm that the PTM interface is active at present.
In /var/curcfg.xmlI I only have a WANDSLLinkConfig Enable="1" and WANPTMLinkConfig Enable is absent, I guess this is consistent with a single sync. Out of interest I will do some tests to try to change the WANxxxLinkConfigs in this file.
That makes sense and is something I really should have thought of myself
FTTC is an 'ethernet' connection, while all variations of adsl are ATM. A different beast entirely.
I've reinstalled the HG612 with B030SP06_unlockedgui-nobtagent firmware and checked the memory usage (all values are kB)
Used Free Shared Buffers Cached
---- ---- ------ ------- ------
Not connected, with GUI: 22428 6328 0 2188 6480
Not connected, GUI killed: 21840 6904 0 2188 6484
Connected, with GUI 22844 5900 0 2244 6700
Connected, GUI killed 22220 6524 0 2244 6704
In all cases remote devices failed to receive internet data. So the problem isn't the presence of the GUI as such, nor would it seem to be a memory issue.
Having killed the GUI, I'd like to try restarting it, but I'm not sure how to do that. The command appears to be /bin/web, but however I execute that command it doesn't work.
[*** Sorry about the formatting - it looked OK on preview]
Very odd indeed... That is certainly the correct command.
Can you check the MD5 sum of the firmware image matches this: 7e4d07f0c7e9264342a5c6b5f97b4663
The current config is stored in /var/curcfg.xml.
The curcfg.xml file looks identical to a saved config file. Don't go to any trouble but do you know have any idea how curcfg.xml is used?
I ask as I wonder on whether AnnexM might be added as a valid dsl type. AnnexM is available via xdslcmd configure or start with "--mod m" or for all --mod dlt2pmv" and works. It would be nice save that config but as very few use annex m it is not worth much effort achieving it.
I suspect curcfg.xml is created during the boot process either from the 'config blocks' in the flashmem or /etc/defaultcfg.xml if those are blank, but I can't say for sure. It does occur to me that it's probably the source for the save config option, so I suppose it stands to reason that they would be identical.
As it happens I
do know where to set that option in the config
It showed up in the initial diff I ran against the default configs as it's one of the things which has changed between B0280SP10 and B030SP06.
Look for a line which starts '<WANDSLInterfaceConfig'. Near the end is 'ConfigMode' which contains a list of modulation options.
Unfortunately I don't know if an option for Annex M exists in the cli binary. However I will take a look and get back to you on that as soon as I can.