[one-users] Yet another problem with connecting to ttylinux via ssh

Wed Jun 1 08:45:26 PDT 2011

Can you send us the configuration of bridges and routes from your physical host?

brctl show
netstat -nr

On Tue, May 31, 2011 at 3:18 PM, Adnan Pasic <pqado at yahoo.de> wrote:
> OK, the problem with the vncviewer was yet another beginners' mistake. I am
> now able to log into the ttylinux-VM and perform a "ifconfig". Here's what I
> get:
> eth0      Link encap:Ethernet  Hardware Adresse 02:00:C0:A8:00:05
>           inet Adresse:192.168.0.5  Bcast:192.168.0.255  Maske:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:321 errors:0 dropped:0 overruns:0 carrier:0
>           Kollisionen:0 SendewarteschlangenlÃ¤nge:1000
>           RX bytes:0 (0.0 B)  TX bytes:19260 (18.8 KB)
>           Interrupt:11 Basisadresse: 0xc100
>
> lo        Link encap:Lokale Schleife
>           inet Adresse:127.0.0.1  Maske:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metrik:1
>           RX packets:320 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:320 errors:0 dropped:0 overruns:0 carrier:0
>           Kollisionen:0 SendewarteschlangenlÃ¤nge:0
>           RX bytes:35840 (35.0 KB)  TX bytes:35840 (35.0 KB)
> And still I can't ping whether the host PC (192.168.0.3), nor the
> ONE-frontend (192.168.0.1). Obviously it's some kind of virtual-network
> configuration issue. However, strangely the migration and suspend/resume
> etc. are working, but only the ping won't do!
>
> ________________________________
> Von: Adnan Pasic <pqado at yahoo.de>
> An: "users at lists.opennebula.org" <users at lists.opennebula.org>
> Gesendet: 12:13 Dienstag, 31.Mai 2011
> Betreff: [one-users] Yet another problem with connecting to ttylinux via ssh
>
> Hello,
> I've been trying to enter my ttylinux-VM from the tutorial, but somehow the
> connection just cant be established. Every time I get a "no route to host"
> error, when I try the various IP's. First of all, here are my ifconfig data,
> after the VM has been created:
> eth0      Link encap:Ethernet  Hardware Adresse 00:19:99:03:b0:3e
>           inet Adresse:192.168.0.3  Bcast:192.168.0.255  Maske:255.255.255.0
>           inet6-Adresse: fe80::219:99ff:fe03:b03e/64
> GÃ¼ltigkeitsbereich:Verbindng
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
>           RX packets:21659 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:10582 errors:0 dropped:0 overruns:0 carrier:0
>           Kollisionen:0 SendewarteschlangenlÃ¤nge:1000
>           RX bytes:31304320 (31.3 MB)  TX bytes:776923 (776.9 KB)
>           Interrupt:17
>
> lo        Link encap:Lokale Schleife
>           inet Adresse:127.0.0.1  Maske:255.0.0.0
>           inet6-Adresse: ::1/128 GÃ¼ltigkeitsbereich:Maschine
>           UP LOOPBACK RUNNING  MTU:16436  Metrik:1
>           RX packets:70 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
>           Kollisionen:0 SendewarteschlangenlÃ¤nge:0
>           RX bytes:5584 (5.5 KB)  TX bytes:5584 (5.5 KB)
>
> virbr0    Link encap:Ethernet  Hardware Adresse fe:00:c0:a8:00:06
>           inet Adresse:192.168.122.1  Bcast:192.168.122.255
> Maske:255.255.255.0
>           inet6-Adresse: fe80::a8e2:ff:fe60:a424/64
> GÃ¼ltigkeitsbereich:Verbindugn
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
>           RX packets:5 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
>           Kollisionen:0 SendewarteschlangenlÃ¤nge:0
>           RX bytes:230 (230.0 B)  TX bytes:5750 (5.7 KB)
>
> vnet0     Link encap:Ethernet  Hardware Adresse fe:00:c0:a8:00:06
>           inet6-Adresse: fe80::fc00:c0ff:fea8:6/64
> GÃ¼ltigkeitsbereich:Verbindun          UP BROADCAST RUNNING MULTICAST
> MTU:1500  Metrik:1
>           RX packets:5 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
>           Kollisionen:0 SendewarteschlangenlÃ¤nge:500
>           RX bytes:300 (300.0 B)  TX bytes:1040 (1.0 KB)
>
>
> The VM has been created with the IP 192.168.0.5, but when I try to ssh onto
> it, I get the above mentioned error. Strangely, when I perform a "sudo
> vncviewer localhost:6789" I get the screen of the VM, but can't also do
> anything in it. I try to type in the password, but no keystrokes get taken
> over and the vncviewer screen looks more like just a screenshot through
> which I can scroll up and down.
> This is my network-configuration:
> NAME = "Small Network"
> TYPE = FIXED
> BRIDGE = virbr0
> LEASES = [IP=192.168.0.5]
>
> Anyone got an idea???
> Thanks!
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>

-- 
Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org