![]() With telnet, there is a similar error, but I don't remember what it was. Tried setting the username to root, nothing. I used putty, pointed it at 192.168.1.1, nothing. I was not able to access the router via ssh nor telnet. I had already read that I would need to set a root password before being able to do much else. This was straightforward, it didn't take the firmware the first time but on the second time, it flashed and rebooted. I installed OpenWRT on my EA4500 following the Wiki here: … ecommended. I am a Windows guy though so a lot of this is beyond my depth. ![]() I have some limited networking experience, a little Linux knowledge (I can get around and do basic things easily), I like to tinker. I apologize if I'm making a silly mistake.īackground - I am brand new to OpenWRT. I've been Googling and reading docs for a few hours, I need to go to sleep so I'm going to drop my question here and hope someone can help. ![]() I think my failsafe and normal partitions have somehow been kajigerred. Is there a way to force Windows to allow me to ssh over the ethernet cable without network access? Do I need a console cable/serial cable/another router? I would like to start over and do this correctly. Now all the configuration I have done is written to the failsafe partition (I think). Not sure if this is typical or not.Īfter flashing my EA4500 with a trunk build (which seems to be the only supported way to get OpenWRT on this device), I have no way to ssh into the router without using failsafe mode. I'll copy the text of the problem verbatim, below, but here's a summary.Īnother edit - my LAN/WAN jack LEDs are not lit up while attempting to access in normal mode, but in failsafe mode they are. If you run the command this way, when finished the system will drop you back to your local machine and close the remote connection.I also posted on the OpenWRT forum about this issue. This method of issuing commands is convenient, especially if you would like to run a command that takes a while to execute, but don't wish to stay around and wait for it to finish, as might be the case with a backup script. Without this flag, these commands will output an ever-growing string to the Terminal as they update their output. The "-t" flag is also required if you intend to run commands that require more interaction,such as "top" or similar monitoring services. Since sudo is often used when running commands in the Terminal, be sure you include the "-t" flag as shown in the command above, otherwise you will not be able to provide the administrative password to the remote system when prompted and it will be shown in the Terminal when typed instead of masked. If you need to perform multiple commands, you can do so by separating them with semicolons in the command string. To do this, simply provide the command in quotes following the ssh log-in command, and provide the "-t" flag to ensure proper interaction with the remote system is allowed, if needed: This approach is easy enough, but you can also combine these two commands so the SSH session will log in and run the specified command, and then exit so it will not maintain a connection with the remote server. ![]() Exit top and be dropped to the remote command line.At the command prompt, run "top" to view process activity on the remote system. ![]() Run the command "ssh to log in to the system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |