View Single Post
Old 06-05-2014, 03:15 PM   #6
rkomar
Wizard
rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.
 
Posts: 2,986
Karma: 18343081
Join Date: Oct 2010
Location: Sudbury, ON, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633
It sounds like your device could be getting different IP addresses from the DHCP server each time it starts up the WiFi connection. If you were using the wrong IP address on the PC, that would explain the "No route to host" error messages.

If you get the sh_ivtool package from the Developer section and install it to /mnt/ext1/system/bin, edit the applications/sshd_start.app script to uncomment the "#SH_IVTOOL=.." line, then sshd should pop up a dialog saying what IP address and port that it is listening to. That way, you know what address to point scp/ssh at on your PC.

I'm also adding the same functionality to the utelnetd package. I should have that download ready shortly after this.
rkomar is offline   Reply With Quote