[kwlug-disc] SSH to a VM

[Nick Guenther]

Tell us if it turns out you need to turn on IP routing! If your box is handling two interfaces already and the VM interface is just appearing as a third, you might not need that afterall. Good luck.

On February 6, 2015 3:08:05 PM EST, CrankyOldBugger <crankyoldbugger at gmail.com> wrote:
>Well I was puzzled by why virbr0 picked 192.x.x.x when there were two
>NICs
>on that box box on 10.x.x.x.  I assumed that there was some deep reason
>behind that which was beyond my understanding.. I could try changing
>virbr0
>tonight and see what happens.
>
>On Fri Feb 06 2015 at 3:05:17 PM Nick Guenther <nguenthe at uwaterloo.ca>
>wrote:
>
>> Also to diagnose the last problem--which is not IP related-- run ssh
>-vv.
>> It sounds like you're offering a pubkey and it's rejecting it, and
>this
>> will show you which. I believe openssh by default falls back to
>asking for
>> passwords in this case, but maybe your client config or the VM config
>is
>> denying that.
>>
>> On February 6, 2015 2:51:19 PM EST, CrankyOldBugger <
>> crankyoldbugger at gmail.com> wrote:
>>
>>> I finally returned to the idea of building some VMs on my home
>network on
>>> an Ubuntu server.  I found uvt-kvm to be a stupid-easy way to
>actually make
>>> the VMs (in this case, a straightforward Ubuntu 14.04 Desktop
>install).
>>>
>>> The VM is running fine when I view it in Virtual Machine Manager
>from a
>>> separate desktop client (connect to the host, then open the VM from
>the
>>> list).  I've set up port forwarding on my router, installed SSH on
>the VM,
>>> made sure it's running, installed a ddclient and set up the machine
>name on
>>> dyn.com, generally everything I've done on other physical Ubuntu
>>> machines.
>>>
>>> However, when I try to connect remotely via SSH, I get "Error in
>TightVNC
>>> Viewer: A connection attempt failed because the connected party did
>not
>>> properly respond after a period of time, or established connection
>failed
>>> because connected host has failed to respond."
>>>
>>> I get this error when I'm outside my network.  From within the
>network, I
>>> get "no route to host" if I use "ssh jeff at 192.168.122.15".
>>>
>>> Note that my network runs on the 10.x.x.x subnet. The 192.168.122.x
>came
>>> from virbr0 on the physical host box.
>>>
>>> If I try to ssh from the physical host to the VM, I get "Permission
>>> denied (publickey)" before it even asks me to login.
>>>
>>> So I seem to be missing a hop somewhere from my router to the
>virtual
>>> machine.  Does anyone have any ideas on how to make the connection?
>>>
>>> ------------------------------
>>>
>>> kwlug-disc mailing list
>>> kwlug-disc at kwlug.org
>>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>>>
>>>
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20150206/472b225f/attachment.htm>