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@xxxxxxxxxxxx> To: "Speakup is a screen review system for Linux." <speakup at 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 at 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 > >
