Help installing Debian

[vector-crumb]

Hello everyone:

I'm new at this forum (though I've been using it for various months now). I have been looking at posts which show you how to install a chrooted Debian environment on your Kindle and I thought I'd try it out. I've been following instructions on this page though http://www.turnkeylinux.org/blog/kindle-root . I have already jailbreaked my Kindle 5 Wifi, installed Usbnet, GUI Launcher and jbpatch. Then I created a virtual machine on Oracle VM VirtualBox on my Windows 7 64-bit Home Premium and ran a 32-bit Debian OS on it [the virtual machine]. After much fiddling about with the IP of my Kindle on the Windows Network and Sharing Center, I finally managed to ssh into my Kindle from Debian as root. I followed the instructions of obtaining the rsa and dss keys via dropbear, placed them into the corresponding files, exited usbnetwork mode, and using Notepad++ on windows, edited the config file to enable WIFI SSH. The thing is that when I try to ssh into my kindle through the Debian Root Terminal, I receive the connection has timed out error. I attempt the following IP's :

• 192.168.15.244 //the typical kindle ip
• 192.168.15.245 //the access ip I tried to establish on Windows
• 192.168.1.245 //one of the ip's under the "5-DCHP" on the ;711 page
• 192.168.1.160 //the ip that my kindle typically reports
• 192.168.2.1 //ip listed on the site
• 192.168.2.2 //ip listed on the site

If any anybody has any idea why it's so difficult for me to ssh into my kindle I would really appreciate some help.

P.S. Before anybody asks, I've got some basic knowledge on Linux, but I'm not to sure of more complex stuff, such as "setting up a chrooted environment on a Kindle"

[twobob]

what does your usbnet config file say...

[Kindle FAT root]/usbnet/etc/config

I followed the instructions of obtaining the rsa and dss keys via dropbear, placed them into the corresponding files

and are they in the authorized keys file - with root@(theIPorNAME) at the end? (pictured)

perhaps the networking thread is the best place of these questions and come back to this thread when you have debian specific issues...?

: )

Hope that helps

to be honest I connect via Wifi.

ssh root@kindleWifiIP

should at least get a whimper...

[knc1]

Why not just use the most popular native ssh client for Windows, PuTTy rather than go through all of that virtual machine bother?

[twobob]

linky. http://www.chiark.greenend.org.uk/~s.../download.html

[knc1]

Originally Posted by twobob

linky. http://www.chiark.greenend.org.uk/~s.../download.html

Nice, I forgot the link, thanks.

[vector-crumb]

Originally Posted by twobob

what does your usbnet config file say...

[Kindle FAT root]/usbnet/etc/config

I'll attach the config file.

and are they in the authorized keys file - with root@(theIPorNAME) at the end? (pictured)

I'm gonna do that right now. Thanks, I'd forgotten about that.

to be honest I connect via Wifi.

ssh root@kindleWifiIP

That's exactly what I'm trying to do right now

Just in case, here's the config file:

#!/bin/sh
#
# $Id: config 8742 2012-10-21 20:04:06Z NiLuJe $
#

# WARNING: Take note that we're essentially a shell script, se we absolutely *MUST* use UNIX line endings!
# WARNING: To avoid leaving your system in an undefined state,
#          do *NOT* modify this file while usb over ethernet is enabled!
#          (That means when the the auto enable feature is in use, too!)

# Tweak this to your liking (IPv4 only, no hostname aliases)
KINDLE_IP=192.168.15.244

# Allow SSH over WiFi
# NOTE: If you set this to true, the SSHD *WILL* check your passwords!
# Make sure you know your root password, or auth via shared keys!
USE_WIFI="true"

# Don't switch to Ethernet over USB, and only launch SSHD
# NOTE: Make sure you're able to properly login over SSH before enabling this...
# It's obviously only useful with WiFi devices, so leave to false on non-WiFi devices
USE_WIFI_SSHD_ONLY="false"

# Use OpenSSH instead of dropbear (somewhat faster login)
# NOTE: OpenSSH *WILL* check your passwords!
# Make sure you know your root password, or auth via shared keys!
USE_OPENSSH="false"

[twobob]

let me guess - you are trying to ssh to 192.168.15.244

rather then the IP in the setting page under ;711 ?

what ip you actually connecting to?

what commands exactly are you typing?

Cheers.

[vector-crumb]

Originally Posted by twobob

let me guess - you are trying to ssh to 192.168.15.244

I was trying to ssh into 192.168.15.245, which was the ip that I had configured in Windows. Must I change the config file ip to that ip?

rather then the IP in the setting page under ;711 ?

I also attempted that one(192.168.1.160).

what commands exactly are you typing?

ssh root@192.168.15.244
ssh root@192.168.15.245
ssh root@192.168.1.160

[knc1]

hmm... from 192.168.15.245 (or 244) to 192.168.1.160 requires you route the entire 192.168.0.0/16 address range.

I.E: A netmask of 255.255.0.0 for a /16 network.

Most likely you are only using a 255.255.255.0 netmask (for a /24 network).

[vector-crumb]

I'm using a netmask of 255.255.255.0, but I didn't really get what you meant by "/16" and "/24" networks...

[twobob]

16 and 24 refer the amount of subcomputers you can have.

the /16 would allow the range x.x.0.0

the /24 would allow x.x.x.0

its dull but well documented.

[vector-crumb]

Ok, so just to be clear, which netmask are you suggesting?

[knc1]

Originally Posted by vector-crumb

Ok, so just to be clear, which netmask are you suggesting?

Netmask == Those bits of the address which are all the same.

Netmask: and in bit notation:
255.000.000.000 /8
255.255.000.000 /16
255.255.255.000 /24
255.255.255.255 /32

Talking from 192.168.2.1 to 192.168.2.2 (for example) - the first three groups of 8 bits never change (the 192.168.2) -
so a 255.255.255.0 netmask would work.

Talking from 192.168.2.1 to 192.168.15.204 (for example) - only the first two groups of 8 bits never change (the 192.168) -
so a 255.255.0.0 netmask would work.

The above is the "old common usage" plus old and new syntax.

The new common usage allows for the division at any bit boundary, not just at boundaries of 8 bits (which is shown above).

Simple.
The real fun doesn't start until you start using 128 bit network addresses (IPv6) rather than the old 32 bit network addresses (IPv4).

GeekMaster is the only one here with enough Kindles to need IPv6 addressing in his workroom.

[vector-crumb]

So my best choice would be a /16 netmask, seeing as the possible IP's go up to 192.168.15.245? And in that case, after configuring the netmask as 255.255.0.0, what next? How would I go about connecting to my PC?

[twobob]

how about just using a more "usual" networking arrangement?

i.e 192.168.1.something for both...

See how you get on with that.

Then make it more complicated...