/etc/config/network | Thales IoT Developer Community
September 20, 2017 - 11:41am, 17249 views
Hi,
I accidentally mess up the network file and now I'm not able to connect to the ehs6t-LAN modem. Is there a factory reset (will the factory reset back the network file)?
Or I able to connect via serial port through PC and using the some command to setup the network or reset via AT command can solve this?
Cheers
Thx,
I follow procedure you described and successfully upload file you sent. But update process takes to much time. Currently it spent more then half an hour. Is that ok? How much time update usually takes?
Regards
Hi,
Now I have access to terminal with http but no telnet. I saw ssh but I would like to use telnet because I use it on other terminals. Is it posibile to add telnet somehow?
Edin
Hello,
EHS6 LAN terminal is on a market for quite some time already. And there have been OpenWrt version update during this time. I have sent you the latest version but it is possible that you had an older one before. Telnet is switched off on purpose for security reasons in recent versions.
According to our documentation the Telnet connection can be opened only if no root login password is configured. In case a root login password exists, access to the embedded Linux system is only possible via SSH. And new terminals have the password set in the factory.
Please compare the OpenWrt version of the recovered terminal with the other ones.
Best regards,
Bartłomiej
Hi again,
I followed procedure as you described for 'factory reset' for EHS6T-LAN but I didn't get http://192.168.1.1 for firmware update. Usually I have got but on one device did not.
Do you know what is the problem? Any solution?
Regards
Hello,
Have you configured the static IP from the same subnet on your PC for the interface and still can't access the address? Maybe the terminal did not switch to the firmware flashing ****. In such a case it may be available on the previously configured address if it was before the update attempt. So you may try more *****. Or maybe the problem is related to the web browser you use. You may try with some other.
Regards,
Bartłomiej
Hi,
I have set proper ip on pc interface. That is ip from 192.168.1.0/24 because terminal should have 192.168.1.1. I used advanced network scanner to discover IPs on lan but no terminal ip. Also, I set up dhcpd in case that terminal use dhcp for assigning ip but no results. Also, I tried with different browsers (chrome and MS Edge). I tried to ping terminal but lot of packets have lost (more then 85percent). SSH and Telnet are rejected. In mean time I discover same problem with one more terminal so I have two with similar error. In second terminal I have nothing even ping. Is there ability to update firmware via serial input? May be that will work. Or you have another solution?
Regards
Hello,
I would disable dhcpd because in this recovery **** the terminal does not support DHCP. That PING statistics are interesting - it looks as if there was some answer sometimes. Or maybe it is the case that the terminal did not switch into the recovery ****. Maybe you should experiment a bit with timing. Via serial interface you have the direct access to the module and you would only be able to update the module's firmware but not OpenWrt unfortunately. The LAN interface is the only way.
Regards,
Bartłomiej
Hi,
I tried on different ways but nothing. I wrote loop for accessing but no results. May be to try firmware update via serial. Can you tell me how to do that? I do not have any other ideas.
Regards
Hello,
Module is only used as a ****m in this solution and has no influence on OpenWrt system and LAN access to it. So there is no point in updating it's firmware if the module is working correctly - it replies to AT commands on ASC0 interface.
If you are unable to force the terminal to switch to a firmware flashing **** on LAN maybe you could try to connect to it on the previously set IP with a manual configuration on the PC side also. If nothing works you may need to contact your distributor.
Regards,
Bartłomiej
Hey, We accidentaly switched the network to vlan and we are not able to connect to 192.168.1.1. please help to reset to factory defaults Our modem is ELS61T E2
Thanks,
Mihai