Hi, i have recently got turris omnia 2020. during initial setup i needed to change ip address of lan interface to 192.168.1.2. i changed it through luci and immediately after this change i couldnt connect through web interface on this new address (192.168.1.2). i thought no big deal i can just do quick factory reset since i havent change much yet. i did 3 led reset, then 5 led reset on LAN4, followed my 4 led reset with latest medkit image on usb flashdrive. behaviour was always the same. dhcp still works on the router and it assign my pc ip address and router is obviously sitting at 192.168.1.1. but when i use browser to go to 192.168.1.1 i get ERR_CONNECTION_REFUSED and no initial setup dialog. same with putty. root@192.168.1.1 port22 refusing connection even with (5 LEDs: Unsecure SSH on 192.168.1.1 (Omnia 2019 and newer) ) reset. any idea why i cant get back into the router?
Thank you
Make sure that your browser isn’t using HTTPS and hence tries to use tcp/443 (which isn’t enabled by default). Use HTTP on tcp/80 for the initial setup.
thanks. yes, i verified that im using http and connection still gets refused. i also have second older turris omnia and when i connect pc to it i imediatelly get into the web interface and ssh without problem so it shouldnt be issue with the pc or its firewalls. the new turris refuses all 192.168.1.1 connections no matter what i tried(rollback,factory reset, flashing memory with new image, unsecure ssh, flash from the internet). i havent tried the recovery shell through serial yet since i dont have the cables for it. also when i plug the wan i even get internet through it just fine. its so strange. i should get the initial setup dialog after factory reset right? is there a possibility that the factory resets and memory flashings are not going through? in the documentation they say that “Completion of the snapshot rollback process is indicated by turning all LEDs green for a moment” which happens for me and all LEDs go green in the end, just before they go to standard operation. only difference i can see from the documentation is that the LEDs never turn red during the rollback for me. any ideas how else can i debug this?
Is a serial connection an option in your case?
i will try it when i get the uart cable. i think i will try this tutorial Omnia - Turris Documentation. or is there some other good guide? im still kinda noob in linux. setting up the dhcp dealing tftp server seems bit scary. or can i just use the other omnia? dhcp is already working there.
No need to boot via TFTP. The serial connection will provide you with a shell similar to SSH. This will allow you to debug the network issues.
I think if anyway you are doing clean start you should try to reflash from clean medkit using the instructions from here: Omnia - Turris Documentation
i tried reflash from clean medkit using that documentation. no success. 192.168.1.1 is still refusing connection so i dont get initial setup dialog. maybe im doing something wrong but i tried both fat32, ext4 flash to front usb with the downloaded medkit. i have also tried adding medkit configuration file for ethernetless access and it didnt work. new wifi network was not created. i will try the serial connection next and if that doesnt work i will use hammer. im sure that one will finally get inside of the router.