Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: shoey on January 13, 2018, 04:45:43 PM
-
Hi,
Been happily using DSL stats for a while with this router, however I have updated the firmware to the 5.13 version V5.13(AAXA.7)C0 which is the latest release.
Now none of the telnet commands work, instead of the busybox header once logged in i now just see ZySh> and none of the existing commands now work.
Any ideas other than going back firmware versions.
-
I have seen the same problem on a vmg 3925. it was fine till upgrading with the latest firmware. In the end we rolled it back to an earlier version. busybox had disapperaed..
-
Yeah i think i will have to roll back as well.
-
I was running 5.11(AAXA.4)C0 which was Nov 16, and 5.13(AAXA.7)C0 is Dec 17 going to try 5.13(AAXA.5)C0 Jul 17
-
Very peculiar. :-\
I have a ZyXEL VMG1312-B10D and it is using the V5.13(AAXA.5)C0 firmware.
Before you attempt to roll-back, I will suggest that you perform a reset to factory defaults and power-cycle the device. Once re-booted, reconfigure it and do not re-load any backup configuration file.
I have a suspicion that the device has just got very confused, as all firmware prior to V5.13(AAXA.5)C0 had the ROM-D device as /dev/mtd3 (/dev/mtdblock3) but with the latest firmware, the ROM-D device has been moved to the next partition, /dev/mtd4 (/dev/mtdblock4).
-
Hi burakkucat,
I havn't rolled back did a factory reset, and am back online. However when i telnet to the router and login as admin i am still greated with the following screen.
VMG1312-B10D login: admin
Password:
ZySH>
And i still cant access any of the xdslctl info, is there something else i need to do, as my sync speed has improved with the latest firmware, but as i am about to upgrade to vdsl, i would still like to be using my PI to run dslstats.
-
I really don't know what is happening. Are you sure you have a VMG1312-B10D? (Sorry if that is a silly question but it had to be asked.)
I normally access my modem/router via ssh but for the following experiment I also enabled telnet access. This is what I see when I access the device as admin, supervisor and root firstly by ssh (port 22) and then by telnet (port 23) --
[Duo2 tmp]$ ssh admin@ap
admin@ap's password:
BusyBox v1.20.1 (2017-04-20 00:36:56 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
$ ls
data fw zcfg_config.json
$ Connection to ap closed.
[Duo2 tmp]$ ssh supervisor@ap
supervisor@ap's password:
BusyBox v1.20.1 (2017-04-20 00:36:56 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
$ ls
data fw zcfg_config.json
$ Connection to ap closed.
[Duo2 tmp]$ ssh root@ap
root@ap's password:
BusyBox v1.20.1 (2017-04-20 00:36:56 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# ls
data fw zcfg_config.json
# Connection to ap closed.
[Duo2 tmp]$ telnet ap
Trying 192.168.1.254...
Connected to ap.
Escape character is '^]'.
VMG1312-B10D login: admin
Password:
BusyBox v1.20.1 (2017-04-20 00:36:56 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
$ ls
data fw zcfg_config.json
$ Connection closed by foreign host.
[Duo2 tmp]$ telnet ap
Trying 192.168.1.254...
Connected to ap.
Escape character is '^]'.
VMG1312-B10D login: supervisor
Password:
BusyBox v1.20.1 (2017-04-20 00:36:56 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
$ ls
data fw zcfg_config.json
$ Connection closed by foreign host.
[Duo2 tmp]$ telnet ap
Trying 192.168.1.254...
Connected to ap.
Escape character is '^]'.
VMG1312-B10D login: root
Password:
BusyBox v1.20.1 (2017-04-20 00:36:56 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# ls
data fw zcfg_config.json
# Connection closed by foreign host.
[Duo2 tmp]$
I'm familiar with the ZyXEL Shell and can invoke it from the command line --
[Duo2 tmp]$ ssh root@ap
root@ap's password:
BusyBox v1.20.1 (2017-04-20 00:36:56 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# zysh
ZySH> ?
enable - Raise the privilege level for a CLI session
exit - Close an active terminal session
history - Display or clear CLI history
show - <N/A>
tcpdump - text based packet capture utility
traceroute - monitor each routed node during whole routing path to <host>
ZySH> exit
# ls
data fw zcfg_config.json
# Connection to ap closed.
[Duo2 tmp]$
I'm puzzled by what you are experiencing. ???
-
I only have access to the admin user, i don't know the password for the supervisor or the root user.
That's defiantly the right router, it was fine when it was on the 5.11 versions of the firmware and i just upgraded to the latest. Is there a command to get out of zysh?
-
Is there a command to get out of zysh?
The documented command is "exit". You could also try using <Ctrl-D>.
-
I have the same issue after upgrading to 5.13. A factory reset didn't change anything.
-
Looking at the firmware documentation, there is a mention of a change to the CLI....
Modifications in V5.13(AAXA.7)b1
[Feature Modification]
1. [eITS #170100670] allow port forwarding rule to be from any WAN
2. [eITS #170300570] Enhance OPAL Privilege feature
3. [eITS #170600099] Add FTP in the SP Domain management services
4. Support CLI interface
-
agreed. a friend's vmg3925 lost busybox on the latest firmware regardless of what we tried etc.. the only way to resolve it was to roll back.
-
This is beginning to look like ZyXEL are determined to lock down their routers in future so ordinary users are unable to mess around with them. I suspect all new routers will be the same. Not really sure why they need to do this, could it be that to get their routers approved by BT in future they need to do this?
Stuart
-
exit just closes the terminal session, i did email zyxel the support guy was like "Really they have removed that" hes going to talk to the developers and get back to me.
-
I've just looked on the Zyxel website again. There's 2 versions of the 5.13 firmware:
- 5.13(AAXA.7)C0 released on 25/12/17
- 5.13(AAXA.5)C0 released 20/7/17
The 'feature' to add the new CLI was included in the work for the AAXA.7 release (b1).
I've just loaded 5.13(AAXA.5)C0 and as expected busybox is still present. This would explain why people using "5.13" could be seeing differing results.
To me, if you were making a fundamental change like this it would be worthy of a whole new version number to avoid confusion. Clearly Zyxel don't think so! :)
-
Rolling back to 5.13(AAXA.5)C0 works.
-
I just updated my Zyxel VMG1312-B10D to the current firmware, v5.13(AAXA.7)C0, released in December.
Now, on logging in to the box with telnet or ssh, I find the available commands no longer include "xdslctl" or any of the other common adsl commands. Consequently, when DSLstats logs in and executes "xdslctl info --stats", it gets back no data.
Nor does there seem to be any way to invoke a shell that might make other commands available. This change to the firmware was not documented in the release notes and there appears to be no CLI reference manual available either.
One other user has encountered the same behaviour and has posted at https://homeforum.zyxel.com/ without getting a useful reply.
I have opened a support ticket with Zyxel and we'll see if that produces anything. Meanwhile, does anyone here know how to make the VMG1312-B10D work again with DSLstats?
-
. . . does anyone here know how to make the VMG1312-B10D work again with DSLstats?
Downgrade the firmware to V5.11(AAXA.4)C0 is my immediate suggestion.
-
Shoey, did you ever receive the reply you were promised from Zyxel support?
I have opened a ticket with them today on this issue. Nothing so far.
-
I have had this reply from Zyxel tech support:
"For security reasons the CLI based on Linux was exchange through a Sandbox. That is why those commands are not there anymore. Our RD is working on a feature request for the xdsl features and will implement them as soon as possible."
I assume that the phrase "was exchange through a Sandbox" means something like "the CLI has been placed in a sandbox" where it can no longer be reached.
This is the world in which we live, where fears about 'security' become more important than functionality. They overlook the fact that this will force people like us to stay with an old version of the firmware and so not get any of their future security updates.
For now, it's back to 5.13(AAXA.5)C0 for me.
-
I have had this reply from Zyxel tech support:
"For security reasons the CLI based on Linux was exchange through a Sandbox. That is why those commands are not there anymore. Our RD is working on a feature request for the xdsl features and will implement them as soon as possible."
This makes no sense at all. Zyxel have just released a new firmware for the VMG1312-B10A and that still has full access to the shell. It seems very odd they've implemented on the D model only.
Just checked on Zyxel's UK website and I now can't see any firmware for the D model available for download.
-
This makes no sense at all. Zyxel have just released a new firmware for the VMG1312-B10A and that still has full access to the shell. It seems very odd they've implemented on the D model only.
I shall point that out to them.
Just checked on Zyxel's UK website and I now can't see any firmware for the D model available for download.
Yes, they have managed to hide it so it cannot be found by looking up the model number. I had to ask Zyxel support where it had gone and they sent me this link:
https://www.zyxel.com/support/DownloadLandingSR.shtml?c=gb&l=en&kbid=M-02263&md=VMG1312-B10D
It's also available by FTP here: ftp://ftp.zyxel.com/VMG1312-B10D/
-
anoggin,
The only response i had was they spoke to the developers and the response was it was all locked out due to security risks.
I did ask if they would consider adding xdslctl to the safe list of commands, and their response was that they were open to looking into it but with no firm commitment either way.
I guess we'll just have to wait an see.