[one-users] newbie how-to configure network to connect to the vm

[Thomas Stein]

Please post the output of 

ip a
ip r
ip neigh show

iptables -nvL

from the hardwarenode the vm is running on and from within the vm.

cheers
t.


On 20. November 2014 16:44:29 MEZ, Nikolaj Majorov <nikolaj at majorov.biz> wrote:
>HI,
>unfortunately I can’t connect … :-(
>
>Here is my new configuration:
>
> $cat mynetwork_virbr0.one
>NAME = "2private"
>
>BRIDGE = virbr0
>
>AR = [
>    TYPE = IP4,
>    IP = 192.168.0.100,
>    SIZE = 3
>]
>
>
>
>$ tracepath -n 192.168.0.101
>1:  46.4.99.35                                            0.052ms pmtu
>1500
> 1:  46.4.99.33                                            0.901ms
> 1:  46.4.99.33                                            0.956ms
> 2:  213.239.224.193                                       0.305ms
> 3:  213.239.245.125                                       0.453ms
> 4:  213.239.245.221                                       3.034ms
> 5:  no reply
> 6:  no reply
> 7:  no reply
> 8:  no reply
>
>
>> On 20.11.2014, at 15:00, Thomas Stein <himbeere at meine-oma.de> wrote:
>> 
>> On Thursday 20 November 2014 11:57:17 Nikolaj Majorov wrote:
>>> Hello,
>>> 
>>> 
>>> I install open nebula 4.8 on centos 7 as described in quickstarts
>and
>>> confiture my private network as it was showed in example:
>>> 
>>> NAME = "private"
>>> 
>>> BRIDGE = br0
>>> 
>>> AR = [
>>>    TYPE = IP4,
>>>    IP = 192.168.0.100,
>>>    SIZE = 3
>>> ]
>> 
>> I suppose you using virbr0 as bridge device. Can you try this?
>> 
>> t.
>> 
>>> Starting vm I have got IP 192.168.0.100, but  I can’t connect to the
>VM over
>>> ssh and even ping it. What should I do with network to access the VM
>( add
>>> route/gateway  ) ? I’m really newbie in the networking  , so please
>give
>>> some hints ..
>>> 
>>> 
>>> So my network configuration is :
>>> 
>>> ifconfig -a
>>> 
>>> br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>>        inet 46.4.99.35  netmask 255.255.255.255  broadcast
>46.4.99.35
>>>        inet6 fe80::6e62:6dff:fed9:905  prefixlen 64  scopeid
>0x20<link>
>>>        ether 6c:62:6d:d9:09:05  txqueuelen 0  (Ethernet)
>>>        RX packets 522518  bytes 1880517877 (1.7 GiB)
>>>        RX errors 0  dropped 0  overruns 0  frame 0
>>>        TX packets 444071  bytes 51737672 (49.3 MiB)
>>>        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>> 
>>> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>>        inet6 fe80::6e62:6dff:fed9:905  prefixlen 64  scopeid
>0x20<link>
>>>        ether 6c:62:6d:d9:09:05  txqueuelen 1000  (Ethernet)
>>>        RX packets 1498963  bytes 1952763267 (1.8 GiB)
>>>        RX errors 0  dropped 0  overruns 0  frame 0
>>>        TX packets 444309  bytes 51763060 (49.3 MiB)
>>>        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>> 
>>> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>>>        inet 127.0.0.1  netmask 255.0.0.0
>>>        inet6 ::1  prefixlen 128  scopeid 0x10<host>
>>>        loop  txqueuelen 0  (Local Loopback)
>>>        RX packets 149945  bytes 166430929 (158.7 MiB)
>>>        RX errors 0  dropped 0  overruns 0  frame 0
>>>        TX packets 149945  bytes 166430929 (158.7 MiB)
>>>        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>> 
>>> virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>>        inet 192.168.122.1  netmask 255.255.255.0  broadcast
>192.168.122.255
>>> ether fe:00:c0:a8:7a:03  txqueuelen 0  (Ethernet)
>>>        RX packets 18  bytes 3711 (3.6 KiB)
>>>        RX errors 0  dropped 0  overruns 0  frame 0
>>>        TX packets 69  bytes 3818 (3.7 KiB)
>>>        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>> 
>>> vnet2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>>        inet6 fe80::fc00:c0ff:fea8:7a03  prefixlen 64  scopeid
>0x20<link>
>>>        ether fe:00:c0:a8:7a:03  txqueuelen 500  (Ethernet)
>>>        RX packets 25  bytes 4805 (4.6 KiB)
>>>        RX errors 0  dropped 0  overruns 0  frame 0
>>>        TX packets 1303  bytes 68138 (66.5 KiB)
>>>        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>> 
>>> 
>>> and routing looks like this:
>>> 
>>> $ route -n
>>> Kernel IP routing table
>>> Destination     Gateway         Genmask         Flags Metric Ref   
>Use
>>> Iface 0.0.0.0         46.4.99.33      0.0.0.0         UG    0      0
>      
>>> 0 br0 46.4.99.33      0.0.0.0         255.255.255.255 UH    0      0
>      
>>> 0 br0 169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0
>      
>>> 0 br0 192.168.122.0   0.0.0.0         255.255.255.0   U     0      0
>      
>>> 0 virbr0
>>> 
>>> Many thanks for any hint !
>>> 
>>> 
>>> Kind regards ,
>>> 
>>> Nikolaj Majorov
>>> nikolaj at majorov.biz
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org <mailto:Users at lists.opennebula.org>
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
><http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
>> 
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org <mailto:Users at lists.opennebula.org>
>> http://lists.opennebula.org/listinfo.cgi/users-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