connecting via ssh

connecting via ssh

[Bruce Noblick]

This may be a very basic question but I haven't figured out how to get ssh to connect with my linux box.

I tried to get my ip address but the information I got seemed to be only valid for the local machine.  I have a router to which all of my computers are connected so I thought my addresses should be on a 192.168.1 subnetwork but the only addresses I saw were on a 127.0 subnetwork.

I used to know how to get this information for my windows box but I have recycled a large number of brain cells since then and don't even remember how to do that right now.  Would I be able to just use a hostname? As a footnote, I have given hostnames of trashcan, paperweight and boatanchor to my computers.  So what I am trying to do is connect my paperweight to my trashcan, grin.

As mentioned in the discussions earlier, I found a teraterm program and thought I was telling it the right stuff but the closest I got was a "connection refused" message from one address.  All other guesses timed out.

Thanks much.

Bruce Noblick 

Re: connecting via ssh

[Tyler Littlefield]

what you may need to do is:
route add default gw <your gateway>
then ifconfig <interface, usually eth0> up <ip address>


Thanks,
Tyler Littlefield
email: tyler@tysdomain.com
web: tysdomain-com
Visit for quality software and web design.
skype: st8amnd2005

----- Original Message ----- 
From: "Bruce Noblick" <brunobrook@columbus.rr.com>
To: "speakup info" <speakup@braille.uwo.ca>
Sent: Saturday, October 18, 2008 8:50 PM
Subject: connecting via ssh


> This may be a very basic question but I haven't figured out how to get ssh 
> to connect with my linux box.
>
> I tried to get my ip address but the information I got seemed to be only 
> valid for the local machine.  I have a router to which all of my computers 
> are connected so I thought my addresses should be on a 192.168.1 
> subnetwork but the only addresses I saw were on a 127.0 subnetwork.
>
> I used to know how to get this information for my windows box but I have 
> recycled a large number of brain cells since then and don't even remember 
> how to do that right now.  Would I be able to just use a hostname? As a 
> footnote, I have given hostnames of trashcan, paperweight and boatanchor 
> to my computers.  So what I am trying to do is connect my paperweight to 
> my trashcan, grin.
>
> As mentioned in the discussions earlier, I found a teraterm program and 
> thought I was telling it the right stuff but the closest I got was a 
> "connection refused" message from one address.  All other guesses timed 
> out.
>
> Thanks much.
>
> Bruce Noblick
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: connecting via ssh

[Tony Baechler]

Bruce Noblick wrote:
> This may be a very basic question but I haven't figured out how to get ssh to connect with my linux box.
>
>   
First, I know this is obvious, but are you sure that the openssh server 
is installed on your Linux machine?  If using Debian, do "aptitude -q 
install openssh-server" before anything else or of course you won't be 
able to connect.

> I tried to get my ip address but the information I got seemed to be only valid for the local machine.  I have a router to which all of my computers are connected so I thought my addresses should be on a 192.168.1 subnetwork but the only addresses I saw were on a 127.0 subnetwork.
>   



Is your router using dhcp?  In other words, do you have the dhcp server 
in your router turned on?  Also, what does "ifconfig" and 
"/etc/network/interfaces" say?  The "ifconfig" command should show you 
your address, gateway and netmask.  /etc/network/interfaces has this 
information for automatic setup on boot.  By default, you're probably 
trying to use dhcp.  The good thing is that you're almost guaranteed 
that you'll get a valid ip address assuming your router is working and 
provides a dhcp server.  The bad thing is that the address could change 
every time, making it difficult to find what address it uses.  For 
example, our Linksys router assigns dhcp addresses starting at 
192.168.0.100.  If I connect from different machines with dhcp, my 
address might be 192.168.0.103 or anything between 100 and 149.  That's 
why static addresses are better, but they require manual setup.  If you 
look at /etc/network/interfaces, it probably says something about dhcp.  
I suggest reading the interfaces (5) man page or I can send you a sample 
of mine.  Then it's just a matter of connecting to the static address 
you assign, such as 192.168.1.5 or whatever via ssh.

Re: connecting via ssh

[Bruce Noblick]

Thanks, Tony,

I was able to get the static IP address working.  Thankfully my years of 
experience on mainframes with front end processors controlling their network 
came in handy for something, grin, even though it has no other current 
relevance.

I am using ubuntu which says that it is "debian-derived" or something like 
that so I thought I would try the aptitude -q command you suggested and it 
did run and it appeared to be functional.  I got lost in the maze of 
categories of packages and names of packages and haven't yet found the 
openssh-server package.  I wasn't sure if that was the best approach with 
ubuntu either so I wanted to confirm that here before I allowed it to do any 
updates or downloads.  I didn't have a good recovery plan if things went 
weird since I don't know linux very well yet.

Thanks for your patience.

Enjoy the day!
Bruce

.
----- Original Message ----- 
From: "Tony Baechler" <tony@baechler.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, October 19, 2008 6:23 AM
Subject: Re: connecting via ssh


> Bruce Noblick wrote:
>> This may be a very basic question but I haven't figured out how to get 
>> ssh to connect with my linux box.
>>
>>
> First, I know this is obvious, but are you sure that the openssh server is 
> installed on your Linux machine?  If using Debian, do "aptitude -q install 
> openssh-server" before anything else or of course you won't be able to 
> connect.
>
>> I tried to get my ip address but the information I got seemed to be only 
>> valid for the local machine.  I have a router to which all of my 
>> computers are connected so I thought my addresses should be on a 
>> 192.168.1 subnetwork but the only addresses I saw were on a 127.0 
>> subnetwork.
>>
>
>
>
> Is your router using dhcp?  In other words, do you have the dhcp server in 
> your router turned on?  Also, what does "ifconfig" and 
> "/etc/network/interfaces" say?  The "ifconfig" command should show you 
> your address, gateway and netmask.  /etc/network/interfaces has this 
> information for automatic setup on boot.  By default, you're probably 
> trying to use dhcp.  The good thing is that you're almost guaranteed that 
> you'll get a valid ip address assuming your router is working and provides 
> a dhcp server.  The bad thing is that the address could change every time, 
> making it difficult to find what address it uses.  For example, our 
> Linksys router assigns dhcp addresses starting at 192.168.0.100.  If I 
> connect from different machines with dhcp, my address might be 
> 192.168.0.103 or anything between 100 and 149.  That's why static 
> addresses are better, but they require manual setup.  If you look at 
> /etc/network/interfaces, it probably says something about dhcp.  I suggest 
> reading the interfaces (5) man page or I can send you a sample of mine. 
> Then it's just a matter of connecting to the static address you assign, 
> such as 192.168.1.5 or whatever via ssh.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ NOD32 3539 (20081021) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
> 

Re: connecting via ssh

[Kerry Hoath]

I'd run
apt-get install openssh

and answer yes to the question about installing packages. Usually works for 
me.
Regards, Kerry.

----- Original Message ----- 
From: "Bruce Noblick" <brunobrook@columbus.rr.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, October 26, 2008 8:44 PM
Subject: Re: connecting via ssh


> Thanks, Tony,
>
> I was able to get the static IP address working.  Thankfully my years of 
> experience on mainframes with front end processors controlling their 
> network came in handy for something, grin, even though it has no other 
> current relevance.
>
> I am using ubuntu which says that it is "debian-derived" or something like 
> that so I thought I would try the aptitude -q command you suggested and it 
> did run and it appeared to be functional.  I got lost in the maze of 
> categories of packages and names of packages and haven't yet found the 
> openssh-server package.  I wasn't sure if that was the best approach with 
> ubuntu either so I wanted to confirm that here before I allowed it to do 
> any updates or downloads.  I didn't have a good recovery plan if things 
> went weird since I don't know linux very well yet.
>
> Thanks for your patience.
>
> Enjoy the day!
> Bruce
>
> .
> ----- Original Message ----- 
> From: "Tony Baechler" <tony@baechler.net>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Sunday, October 19, 2008 6:23 AM
> Subject: Re: connecting via ssh
>
>
>> Bruce Noblick wrote:
>>> This may be a very basic question but I haven't figured out how to get 
>>> ssh to connect with my linux box.
>>>
>>>
>> First, I know this is obvious, but are you sure that the openssh server 
>> is installed on your Linux machine?  If using Debian, do "aptitude -q 
>> install openssh-server" before anything else or of course you won't be 
>> able to connect.
>>
>>> I tried to get my ip address but the information I got seemed to be only 
>>> valid for the local machine.  I have a router to which all of my 
>>> computers are connected so I thought my addresses should be on a 
>>> 192.168.1 subnetwork but the only addresses I saw were on a 127.0 
>>> subnetwork.
>>>
>>
>>
>>
>> Is your router using dhcp?  In other words, do you have the dhcp server 
>> in your router turned on?  Also, what does "ifconfig" and 
>> "/etc/network/interfaces" say?  The "ifconfig" command should show you 
>> your address, gateway and netmask.  /etc/network/interfaces has this 
>> information for automatic setup on boot.  By default, you're probably 
>> trying to use dhcp.  The good thing is that you're almost guaranteed that 
>> you'll get a valid ip address assuming your router is working and 
>> provides a dhcp server.  The bad thing is that the address could change 
>> every time, making it difficult to find what address it uses.  For 
>> example, our Linksys router assigns dhcp addresses starting at 
>> 192.168.0.100.  If I connect from different machines with dhcp, my 
>> address might be 192.168.0.103 or anything between 100 and 149.  That's 
>> why static addresses are better, but they require manual setup.  If you 
>> look at /etc/network/interfaces, it probably says something about dhcp. 
>> I suggest reading the interfaces (5) man page or I can send you a sample 
>> of mine. Then it's just a matter of connecting to the static address you 
>> assign, such as 192.168.1.5 or whatever via ssh.
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>> __________ NOD32 3539 (20081021) Information __________
>>
>> This message was checked by NOD32 antivirus system.
>> http://www.eset.com
>>
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: connecting via ssh

[Bruce Noblick]

Thanks to all,

It is now working.

I now have a choice.  When I get tired of orca's voice, I can connect from 
my windows box so that I can get tired of its voice too, grin.

Thanks again for all the help.

Enjoy!

----- Original Message ----- 
From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, October 26, 2008 8:05 AM
Subject: Re: connecting via ssh


> I'd run
> apt-get install openssh
>
> and answer yes to the question about installing packages. Usually works 
> for me.
> Regards, Kerry.
>
> ----- Original Message ----- 
> From: "Bruce Noblick" <brunobrook@columbus.rr.com>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Sunday, October 26, 2008 8:44 PM
> Subject: Re: connecting via ssh
>
>
>> Thanks, Tony,
>>
>> I was able to get the static IP address working.  Thankfully my years of 
>> experience on mainframes with front end processors controlling their 
>> network came in handy for something, grin, even though it has no other 
>> current relevance.
>>
>> I am using ubuntu which says that it is "debian-derived" or something 
>> like that so I thought I would try the aptitude -q command you suggested 
>> and it did run and it appeared to be functional.  I got lost in the maze 
>> of categories of packages and names of packages and haven't yet found the 
>> openssh-server package.  I wasn't sure if that was the best approach with 
>> ubuntu either so I wanted to confirm that here before I allowed it to do 
>> any updates or downloads.  I didn't have a good recovery plan if things 
>> went weird since I don't know linux very well yet.
>>
>> Thanks for your patience.
>>
>> Enjoy the day!
>> Bruce
>>
>> .
>> ----- Original Message ----- 
>> From: "Tony Baechler" <tony@baechler.net>
>> To: "Speakup is a screen review system for Linux." 
>> <speakup@braille.uwo.ca>
>> Sent: Sunday, October 19, 2008 6:23 AM
>> Subject: Re: connecting via ssh
>>
>>
>>> Bruce Noblick wrote:
>>>> This may be a very basic question but I haven't figured out how to get 
>>>> ssh to connect with my linux box.
>>>>
>>>>
>>> First, I know this is obvious, but are you sure that the openssh server 
>>> is installed on your Linux machine?  If using Debian, do "aptitude -q 
>>> install openssh-server" before anything else or of course you won't be 
>>> able to connect.
>>>
>>>> I tried to get my ip address but the information I got seemed to be 
>>>> only valid for the local machine.  I have a router to which all of my 
>>>> computers are connected so I thought my addresses should be on a 
>>>> 192.168.1 subnetwork but the only addresses I saw were on a 127.0 
>>>> subnetwork.
>>>>
>>>
>>>
>>>
>>> Is your router using dhcp?  In other words, do you have the dhcp server 
>>> in your router turned on?  Also, what does "ifconfig" and 
>>> "/etc/network/interfaces" say?  The "ifconfig" command should show you 
>>> your address, gateway and netmask.  /etc/network/interfaces has this 
>>> information for automatic setup on boot.  By default, you're probably 
>>> trying to use dhcp.  The good thing is that you're almost guaranteed 
>>> that you'll get a valid ip address assuming your router is working and 
>>> provides a dhcp server.  The bad thing is that the address could change 
>>> every time, making it difficult to find what address it uses.  For 
>>> example, our Linksys router assigns dhcp addresses starting at 
>>> 192.168.0.100.  If I connect from different machines with dhcp, my 
>>> address might be 192.168.0.103 or anything between 100 and 149.  That's 
>>> why static addresses are better, but they require manual setup.  If you 
>>> look at /etc/network/interfaces, it probably says something about dhcp. 
>>> I suggest reading the interfaces (5) man page or I can send you a sample 
>>> of mine. Then it's just a matter of connecting to the static address you 
>>> assign, such as 192.168.1.5 or whatever via ssh.
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>> __________ NOD32 3539 (20081021) Information __________
>>>
>>> This message was checked by NOD32 antivirus system.
>>> http://www.eset.com
>>>
>>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ NOD32 3557 (20081026) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
> 

Re: connecting via ssh

[Tyler Littlefield]

grab openssh-krb5 rather than openssh, though.

Thanks,
Tyler Littlefield
email: tyler@tysdomain.com
web: tysdomain-com
Visit for quality software and web design.
skype: st8amnd2005

----- Original Message ----- 
From: "Bruce Noblick" <brunobrook@columbus.rr.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, October 26, 2008 6:19 PM
Subject: Re: connecting via ssh


> Thanks to all,
>
> It is now working.
>
> I now have a choice.  When I get tired of orca's voice, I can connect from 
> my windows box so that I can get tired of its voice too, grin.
>
> Thanks again for all the help.
>
> Enjoy!
>
> ----- Original Message ----- 
> From: "Kerry Hoath" <kerry@gotss.net>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Sunday, October 26, 2008 8:05 AM
> Subject: Re: connecting via ssh
>
>
>> I'd run
>> apt-get install openssh
>>
>> and answer yes to the question about installing packages. Usually works 
>> for me.
>> Regards, Kerry.
>>
>> ----- Original Message ----- 
>> From: "Bruce Noblick" <brunobrook@columbus.rr.com>
>> To: "Speakup is a screen review system for Linux." 
>> <speakup@braille.uwo.ca>
>> Sent: Sunday, October 26, 2008 8:44 PM
>> Subject: Re: connecting via ssh
>>
>>
>>> Thanks, Tony,
>>>
>>> I was able to get the static IP address working.  Thankfully my years of 
>>> experience on mainframes with front end processors controlling their 
>>> network came in handy for something, grin, even though it has no other 
>>> current relevance.
>>>
>>> I am using ubuntu which says that it is "debian-derived" or something 
>>> like that so I thought I would try the aptitude -q command you suggested 
>>> and it did run and it appeared to be functional.  I got lost in the maze 
>>> of categories of packages and names of packages and haven't yet found 
>>> the openssh-server package.  I wasn't sure if that was the best approach 
>>> with ubuntu either so I wanted to confirm that here before I allowed it 
>>> to do any updates or downloads.  I didn't have a good recovery plan if 
>>> things went weird since I don't know linux very well yet.
>>>
>>> Thanks for your patience.
>>>
>>> Enjoy the day!
>>> Bruce
>>>
>>> .
>>> ----- Original Message ----- 
>>> From: "Tony Baechler" <tony@baechler.net>
>>> To: "Speakup is a screen review system for Linux." 
>>> <speakup@braille.uwo.ca>
>>> Sent: Sunday, October 19, 2008 6:23 AM
>>> Subject: Re: connecting via ssh
>>>
>>>
>>>> Bruce Noblick wrote:
>>>>> This may be a very basic question but I haven't figured out how to get 
>>>>> ssh to connect with my linux box.
>>>>>
>>>>>
>>>> First, I know this is obvious, but are you sure that the openssh server 
>>>> is installed on your Linux machine?  If using Debian, do "aptitude -q 
>>>> install openssh-server" before anything else or of course you won't be 
>>>> able to connect.
>>>>
>>>>> I tried to get my ip address but the information I got seemed to be 
>>>>> only valid for the local machine.  I have a router to which all of my 
>>>>> computers are connected so I thought my addresses should be on a 
>>>>> 192.168.1 subnetwork but the only addresses I saw were on a 127.0 
>>>>> subnetwork.
>>>>>
>>>>
>>>>
>>>>
>>>> Is your router using dhcp?  In other words, do you have the dhcp server 
>>>> in your router turned on?  Also, what does "ifconfig" and 
>>>> "/etc/network/interfaces" say?  The "ifconfig" command should show you 
>>>> your address, gateway and netmask.  /etc/network/interfaces has this 
>>>> information for automatic setup on boot.  By default, you're probably 
>>>> trying to use dhcp.  The good thing is that you're almost guaranteed 
>>>> that you'll get a valid ip address assuming your router is working and 
>>>> provides a dhcp server.  The bad thing is that the address could change 
>>>> every time, making it difficult to find what address it uses.  For 
>>>> example, our Linksys router assigns dhcp addresses starting at 
>>>> 192.168.0.100.  If I connect from different machines with dhcp, my 
>>>> address might be 192.168.0.103 or anything between 100 and 149.  That's 
>>>> why static addresses are better, but they require manual setup.  If you 
>>>> look at /etc/network/interfaces, it probably says something about dhcp. 
>>>> I suggest reading the interfaces (5) man page or I can send you a 
>>>> sample of mine. Then it's just a matter of connecting to the static 
>>>> address you assign, such as 192.168.1.5 or whatever via ssh.
>>>> _______________________________________________
>>>> Speakup mailing list
>>>> Speakup@braille.uwo.ca
>>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>>
>>>> __________ NOD32 3539 (20081021) Information __________
>>>>
>>>> This message was checked by NOD32 antivirus system.
>>>> http://www.eset.com
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>> __________ NOD32 3557 (20081026) Information __________
>>
>> This message was checked by NOD32 antivirus system.
>> http://www.eset.com
>>
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: connecting via ssh

[Kerry Hoath]

Why?
that'll pull in a whole pile of kerborose dependancies which you probably 
don't need.


----- Original Message ----- 
From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, October 27, 2008 9:22 AM
Subject: Re: connecting via ssh


> grab openssh-krb5 rather than openssh, though.
>
> Thanks,
> Tyler Littlefield
> email: tyler@tysdomain.com
> web: tysdomain-com
> Visit for quality software and web design.
> skype: st8amnd2005
>
> ----- Original Message ----- 
> From: "Bruce Noblick" <brunobrook@columbus.rr.com>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Sunday, October 26, 2008 6:19 PM
> Subject: Re: connecting via ssh
>
>
>> Thanks to all,
>>
>> It is now working.
>>
>> I now have a choice.  When I get tired of orca's voice, I can connect 
>> from my windows box so that I can get tired of its voice too, grin.
>>
>> Thanks again for all the help.
>>
>> Enjoy!
>>
>> ----- Original Message ----- 
>> From: "Kerry Hoath" <kerry@gotss.net>
>> To: "Speakup is a screen review system for Linux." 
>> <speakup@braille.uwo.ca>
>> Sent: Sunday, October 26, 2008 8:05 AM
>> Subject: Re: connecting via ssh
>>
>>
>>> I'd run
>>> apt-get install openssh
>>>
>>> and answer yes to the question about installing packages. Usually works 
>>> for me.
>>> Regards, Kerry.
>>>
>>> ----- Original Message ----- 
>>> From: "Bruce Noblick" <brunobrook@columbus.rr.com>
>>> To: "Speakup is a screen review system for Linux." 
>>> <speakup@braille.uwo.ca>
>>> Sent: Sunday, October 26, 2008 8:44 PM
>>> Subject: Re: connecting via ssh
>>>
>>>
>>>> Thanks, Tony,
>>>>
>>>> I was able to get the static IP address working.  Thankfully my years 
>>>> of experience on mainframes with front end processors controlling their 
>>>> network came in handy for something, grin, even though it has no other 
>>>> current relevance.
>>>>
>>>> I am using ubuntu which says that it is "debian-derived" or something 
>>>> like that so I thought I would try the aptitude -q command you 
>>>> suggested and it did run and it appeared to be functional.  I got lost 
>>>> in the maze of categories of packages and names of packages and haven't 
>>>> yet found the openssh-server package.  I wasn't sure if that was the 
>>>> best approach with ubuntu either so I wanted to confirm that here 
>>>> before I allowed it to do any updates or downloads.  I didn't have a 
>>>> good recovery plan if things went weird since I don't know linux very 
>>>> well yet.
>>>>
>>>> Thanks for your patience.
>>>>
>>>> Enjoy the day!
>>>> Bruce
>>>>
>>>> .
>>>> ----- Original Message ----- 
>>>> From: "Tony Baechler" <tony@baechler.net>
>>>> To: "Speakup is a screen review system for Linux." 
>>>> <speakup@braille.uwo.ca>
>>>> Sent: Sunday, October 19, 2008 6:23 AM
>>>> Subject: Re: connecting via ssh
>>>>
>>>>
>>>>> Bruce Noblick wrote:
>>>>>> This may be a very basic question but I haven't figured out how to 
>>>>>> get ssh to connect with my linux box.
>>>>>>
>>>>>>
>>>>> First, I know this is obvious, but are you sure that the openssh 
>>>>> server is installed on your Linux machine?  If using Debian, do 
>>>>> "aptitude -q install openssh-server" before anything else or of course 
>>>>> you won't be able to connect.
>>>>>
>>>>>> I tried to get my ip address but the information I got seemed to be 
>>>>>> only valid for the local machine.  I have a router to which all of my 
>>>>>> computers are connected so I thought my addresses should be on a 
>>>>>> 192.168.1 subnetwork but the only addresses I saw were on a 127.0 
>>>>>> subnetwork.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Is your router using dhcp?  In other words, do you have the dhcp 
>>>>> server in your router turned on?  Also, what does "ifconfig" and 
>>>>> "/etc/network/interfaces" say?  The "ifconfig" command should show you 
>>>>> your address, gateway and netmask.  /etc/network/interfaces has this 
>>>>> information for automatic setup on boot.  By default, you're probably 
>>>>> trying to use dhcp.  The good thing is that you're almost guaranteed 
>>>>> that you'll get a valid ip address assuming your router is working and 
>>>>> provides a dhcp server.  The bad thing is that the address could 
>>>>> change every time, making it difficult to find what address it uses. 
>>>>> For example, our Linksys router assigns dhcp addresses starting at 
>>>>> 192.168.0.100.  If I connect from different machines with dhcp, my 
>>>>> address might be 192.168.0.103 or anything between 100 and 149. 
>>>>> That's why static addresses are better, but they require manual setup. 
>>>>> If you look at /etc/network/interfaces, it probably says something 
>>>>> about dhcp. I suggest reading the interfaces (5) man page or I can 
>>>>> send you a sample of mine. Then it's just a matter of connecting to 
>>>>> the static address you assign, such as 192.168.1.5 or whatever via 
>>>>> ssh.
>>>>> _______________________________________________
>>>>> Speakup mailing list
>>>>> Speakup@braille.uwo.ca
>>>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>>>
>>>>> __________ NOD32 3539 (20081021) Information __________
>>>>>
>>>>> This message was checked by NOD32 antivirus system.
>>>>> http://www.eset.com
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Speakup mailing list
>>>> Speakup@braille.uwo.ca
>>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>>
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>> __________ NOD32 3557 (20081026) Information __________
>>>
>>> This message was checked by NOD32 antivirus system.
>>> http://www.eset.com
>>>
>>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: connecting via ssh

[Tyler Littlefield]

it does not need a bunch of depends. Seems as if it's no longer supported, 
though.

Thanks,
Tyler Littlefield
email: tyler@tysdomain.com
web: tysdomain-com
Visit for quality software and web design.
skype: st8amnd2005

----- Original Message ----- 
From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, October 26, 2008 6:32 PM
Subject: Re: connecting via ssh


> Why?
> that'll pull in a whole pile of kerborose dependancies which you probably 
> don't need.
>
>
> ----- Original Message ----- 
> From: "Tyler Littlefield" <tyler@tysdomain.com>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Monday, October 27, 2008 9:22 AM
> Subject: Re: connecting via ssh
>
>
>> grab openssh-krb5 rather than openssh, though.
>>
>> Thanks,
>> Tyler Littlefield
>> email: tyler@tysdomain.com
>> web: tysdomain-com
>> Visit for quality software and web design.
>> skype: st8amnd2005
>>
>> ----- Original Message ----- 
>> From: "Bruce Noblick" <brunobrook@columbus.rr.com>
>> To: "Speakup is a screen review system for Linux." 
>> <speakup@braille.uwo.ca>
>> Sent: Sunday, October 26, 2008 6:19 PM
>> Subject: Re: connecting via ssh
>>
>>
>>> Thanks to all,
>>>
>>> It is now working.
>>>
>>> I now have a choice.  When I get tired of orca's voice, I can connect 
>>> from my windows box so that I can get tired of its voice too, grin.
>>>
>>> Thanks again for all the help.
>>>
>>> Enjoy!
>>>
>>> ----- Original Message ----- 
>>> From: "Kerry Hoath" <kerry@gotss.net>
>>> To: "Speakup is a screen review system for Linux." 
>>> <speakup@braille.uwo.ca>
>>> Sent: Sunday, October 26, 2008 8:05 AM
>>> Subject: Re: connecting via ssh
>>>
>>>
>>>> I'd run
>>>> apt-get install openssh
>>>>
>>>> and answer yes to the question about installing packages. Usually works 
>>>> for me.
>>>> Regards, Kerry.
>>>>
>>>> ----- Original Message ----- 
>>>> From: "Bruce Noblick" <brunobrook@columbus.rr.com>
>>>> To: "Speakup is a screen review system for Linux." 
>>>> <speakup@braille.uwo.ca>
>>>> Sent: Sunday, October 26, 2008 8:44 PM
>>>> Subject: Re: connecting via ssh
>>>>
>>>>
>>>>> Thanks, Tony,
>>>>>
>>>>> I was able to get the static IP address working.  Thankfully my years 
>>>>> of experience on mainframes with front end processors controlling 
>>>>> their network came in handy for something, grin, even though it has no 
>>>>> other current relevance.
>>>>>
>>>>> I am using ubuntu which says that it is "debian-derived" or something 
>>>>> like that so I thought I would try the aptitude -q command you 
>>>>> suggested and it did run and it appeared to be functional.  I got lost 
>>>>> in the maze of categories of packages and names of packages and 
>>>>> haven't yet found the openssh-server package.  I wasn't sure if that 
>>>>> was the best approach with ubuntu either so I wanted to confirm that 
>>>>> here before I allowed it to do any updates or downloads.  I didn't 
>>>>> have a good recovery plan if things went weird since I don't know 
>>>>> linux very well yet.
>>>>>
>>>>> Thanks for your patience.
>>>>>
>>>>> Enjoy the day!
>>>>> Bruce
>>>>>
>>>>> .
>>>>> ----- Original Message ----- 
>>>>> From: "Tony Baechler" <tony@baechler.net>
>>>>> To: "Speakup is a screen review system for Linux." 
>>>>> <speakup@braille.uwo.ca>
>>>>> Sent: Sunday, October 19, 2008 6:23 AM
>>>>> Subject: Re: connecting via ssh
>>>>>
>>>>>
>>>>>> Bruce Noblick wrote:
>>>>>>> This may be a very basic question but I haven't figured out how to 
>>>>>>> get ssh to connect with my linux box.
>>>>>>>
>>>>>>>
>>>>>> First, I know this is obvious, but are you sure that the openssh 
>>>>>> server is installed on your Linux machine?  If using Debian, do 
>>>>>> "aptitude -q install openssh-server" before anything else or of 
>>>>>> course you won't be able to connect.
>>>>>>
>>>>>>> I tried to get my ip address but the information I got seemed to be 
>>>>>>> only valid for the local machine.  I have a router to which all of 
>>>>>>> my computers are connected so I thought my addresses should be on a 
>>>>>>> 192.168.1 subnetwork but the only addresses I saw were on a 127.0 
>>>>>>> subnetwork.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Is your router using dhcp?  In other words, do you have the dhcp 
>>>>>> server in your router turned on?  Also, what does "ifconfig" and 
>>>>>> "/etc/network/interfaces" say?  The "ifconfig" command should show 
>>>>>> you your address, gateway and netmask.  /etc/network/interfaces has 
>>>>>> this information for automatic setup on boot.  By default, you're 
>>>>>> probably trying to use dhcp.  The good thing is that you're almost 
>>>>>> guaranteed that you'll get a valid ip address assuming your router is 
>>>>>> working and provides a dhcp server.  The bad thing is that the 
>>>>>> address could change every time, making it difficult to find what 
>>>>>> address it uses. For example, our Linksys router assigns dhcp 
>>>>>> addresses starting at 192.168.0.100.  If I connect from different 
>>>>>> machines with dhcp, my address might be 192.168.0.103 or anything 
>>>>>> between 100 and 149. That's why static addresses are better, but they 
>>>>>> require manual setup. If you look at /etc/network/interfaces, it 
>>>>>> probably says something about dhcp. I suggest reading the interfaces 
>>>>>> (5) man page or I can send you a sample of mine. Then it's just a 
>>>>>> matter of connecting to the static address you assign, such as 
>>>>>> 192.168.1.5 or whatever via ssh.
>>>>>> _______________________________________________
>>>>>> Speakup mailing list
>>>>>> Speakup@braille.uwo.ca
>>>>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>>>>
>>>>>> __________ NOD32 3539 (20081021) Information __________
>>>>>>
>>>>>> This message was checked by NOD32 antivirus system.
>>>>>> http://www.eset.com
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Speakup mailing list
>>>>> Speakup@braille.uwo.ca
>>>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>>>
>>>>
>>>> _______________________________________________
>>>> Speakup mailing list
>>>> Speakup@braille.uwo.ca
>>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>>
>>>> __________ NOD32 3557 (20081026) Information __________
>>>>
>>>> This message was checked by NOD32 antivirus system.
>>>> http://www.eset.com
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: connecting via ssh

[Alex Snow]

It's pointless unless you're in a Kerberos environment, which in a 
residential setting is in itself pointless since you can just use 
password auth with ssh, or public key if you're paranoid
On Sun, Oct 26, 
2008 at 06:50:46PM -0600, Tyler Littlefield wrote:
> it does not need a bunch of depends. Seems as if it's no longer supported, 
> though.
> 
> Thanks,
> Tyler Littlefield
> email: tyler@tysdomain.com
> web: tysdomain-com
> Visit for quality software and web design.
> skype: st8amnd2005
> 
> ----- Original Message ----- 
> From: "Kerry Hoath" <kerry@gotss.net>
> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
> Sent: Sunday, October 26, 2008 6:32 PM
> Subject: Re: connecting via ssh
> 
> 
> >Why?
> >that'll pull in a whole pile of kerborose dependancies which you probably 
> >don't need.
> >
> >
> >----- Original Message ----- 
> >From: "Tyler Littlefield" <tyler@tysdomain.com>
> >To: "Speakup is a screen review system for Linux." 
> ><speakup@braille.uwo.ca>
> >Sent: Monday, October 27, 2008 9:22 AM
> >Subject: Re: connecting via ssh
> >
> >
> >>grab openssh-krb5 rather than openssh, though.
> >>
> >>Thanks,
> >>Tyler Littlefield
> >>email: tyler@tysdomain.com
> >>web: tysdomain-com
> >>Visit for quality software and web design.
> >>skype: st8amnd2005
> >>
> >>----- Original Message ----- 
> >>From: "Bruce Noblick" <brunobrook@columbus.rr.com>
> >>To: "Speakup is a screen review system for Linux." 
> >><speakup@braille.uwo.ca>
> >>Sent: Sunday, October 26, 2008 6:19 PM
> >>Subject: Re: connecting via ssh
> >>
> >>
> >>>Thanks to all,
> >>>
> >>>It is now working.
> >>>
> >>>I now have a choice.  When I get tired of orca's voice, I can connect 
> >>>from my windows box so that I can get tired of its voice too, grin.
> >>>
> >>>Thanks again for all the help.
> >>>
> >>>Enjoy!
> >>>
> >>>----- Original Message ----- 
> >>>From: "Kerry Hoath" <kerry@gotss.net>
> >>>To: "Speakup is a screen review system for Linux." 
> >>><speakup@braille.uwo.ca>
> >>>Sent: Sunday, October 26, 2008 8:05 AM
> >>>Subject: Re: connecting via ssh
> >>>
> >>>
> >>>>I'd run
> >>>>apt-get install openssh
> >>>>
> >>>>and answer yes to the question about installing packages. Usually works 
> >>>>for me.
> >>>>Regards, Kerry.
> >>>>
> >>>>----- Original Message ----- 
> >>>>From: "Bruce Noblick" <brunobrook@columbus.rr.com>
> >>>>To: "Speakup is a screen review system for Linux." 
> >>>><speakup@braille.uwo.ca>
> >>>>Sent: Sunday, October 26, 2008 8:44 PM
> >>>>Subject: Re: connecting via ssh
> >>>>
> >>>>
> >>>>>Thanks, Tony,
> >>>>>
> >>>>>I was able to get the static IP address working.  Thankfully my years 
> >>>>>of experience on mainframes with front end processors controlling 
> >>>>>their network came in handy for something, grin, even though it has no 
> >>>>>other current relevance.
> >>>>>
> >>>>>I am using ubuntu which says that it is "debian-derived" or something 
> >>>>>like that so I thought I would try the aptitude -q command you 
> >>>>>suggested and it did run and it appeared to be functional.  I got lost 
> >>>>>in the maze of categories of packages and names of packages and 
> >>>>>haven't yet found the openssh-server package.  I wasn't sure if that 
> >>>>>was the best approach with ubuntu either so I wanted to confirm that 
> >>>>>here before I allowed it to do any updates or downloads.  I didn't 
> >>>>>have a good recovery plan if things went weird since I don't know 
> >>>>>linux very well yet.
> >>>>>
> >>>>>Thanks for your patience.
> >>>>>
> >>>>>Enjoy the day!
> >>>>>Bruce
> >>>>>
> >>>>>.
> >>>>>----- Original Message ----- 
> >>>>>From: "Tony Baechler" <tony@baechler.net>
> >>>>>To: "Speakup is a screen review system for Linux." 
> >>>>><speakup@braille.uwo.ca>
> >>>>>Sent: Sunday, October 19, 2008 6:23 AM
> >>>>>Subject: Re: connecting via ssh
> >>>>>
> >>>>>
> >>>>>>Bruce Noblick wrote:
> >>>>>>>This may be a very basic question but I haven't figured out how to 
> >>>>>>>get ssh to connect with my linux box.
> >>>>>>>
> >>>>>>>
> >>>>>>First, I know this is obvious, but are you sure that the openssh 
> >>>>>>server is installed on your Linux machine?  If using Debian, do 
> >>>>>>"aptitude -q install openssh-server" before anything else or of 
> >>>>>>course you won't be able to connect.
> >>>>>>
> >>>>>>>I tried to get my ip address but the information I got seemed to be 
> >>>>>>>only valid for the local machine.  I have a router to which all of 
> >>>>>>>my computers are connected so I thought my addresses should be on a 
> >>>>>>>192.168.1 subnetwork but the only addresses I saw were on a 127.0 
> >>>>>>>subnetwork.
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>Is your router using dhcp?  In other words, do you have the dhcp 
> >>>>>>server in your router turned on?  Also, what does "ifconfig" and 
> >>>>>>"/etc/network/interfaces" say?  The "ifconfig" command should show 
> >>>>>>you your address, gateway and netmask.  /etc/network/interfaces has 
> >>>>>>this information for automatic setup on boot.  By default, you're 
> >>>>>>probably trying to use dhcp.  The good thing is that you're almost 
> >>>>>>guaranteed that you'll get a valid ip address assuming your router is 
> >>>>>>working and provides a dhcp server.  The bad thing is that the 
> >>>>>>address could change every time, making it difficult to find what 
> >>>>>>address it uses. For example, our Linksys router assigns dhcp 
> >>>>>>addresses starting at 192.168.0.100.  If I connect from different 
> >>>>>>machines with dhcp, my address might be 192.168.0.103 or anything 
> >>>>>>between 100 and 149. That's why static addresses are better, but they 
> >>>>>>require manual setup. If you look at /etc/network/interfaces, it 
> >>>>>>probably says something about dhcp. I suggest reading the interfaces 
> >>>>>>(5) man page or I can send you a sample of mine. Then it's just a 
> >>>>>>matter of connecting to the static address you assign, such as 
> >>>>>>192.168.1.5 or whatever via ssh.
> >>>>>>_______________________________________________
> >>>>>>Speakup mailing list
> >>>>>>Speakup@braille.uwo.ca
> >>>>>>http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>>>>>
> >>>>>>__________ NOD32 3539 (20081021) Information __________
> >>>>>>
> >>>>>>This message was checked by NOD32 antivirus system.
> >>>>>>http://www.eset.com
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>_______________________________________________
> >>>>>Speakup mailing list
> >>>>>Speakup@braille.uwo.ca
> >>>>>http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>>>>
> >>>>
> >>>>_______________________________________________
> >>>>Speakup mailing list
> >>>>Speakup@braille.uwo.ca
> >>>>http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>>>
> >>>>__________ NOD32 3557 (20081026) Information __________
> >>>>
> >>>>This message was checked by NOD32 antivirus system.
> >>>>http://www.eset.com
> >>>>
> >>>>
> >>>
> >>>_______________________________________________
> >>>Speakup mailing list
> >>>Speakup@braille.uwo.ca
> >>>http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>
> >>_______________________________________________
> >>Speakup mailing list
> >>Speakup@braille.uwo.ca
> >>http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
lp1 on fire
	-- One of the more obfuscated kernel messages