"no internet access" on instance's NIC

asked 2017-04-05 11:11:26 +0300

Laci gravatar image

updated 2017-04-05 11:14:34 +0300

Instance starts on hyper-v, but no internet access, only APIPA address occurs in output of ipconfig. Status of 'Connections: Ethernet' is "No internet access".

At the controller everything looks like good:

+--------------------------------------+--------+--------+------------+-------------+------------------+
| ID                                   | Name   | Status | Task State | Power State | Networks         |
+--------------------------------------+--------+--------+------------+-------------+------------------+
| 37426e91-96ab-49fc-8abd-8c72366a29d3 | cirros | ACTIVE | -          | Running     | privnet=10.0.0.16 |
| 5de24a4e-c87f-4f3c-b8c8-8609a9065000 | w17    | ACTIVE | -          | Running     | privnet=10.0.0.5, 172.17.4.19 |
+--------------------------------------+--------+--------+------------+-------------+------------------+

I can associate a floating-ip address to hyper-v instance, but it is dead too.

How can I debug this?

Thanks in advance!

Laci

edit retag flag offensive close merge delete

Comments

Hey Laci, Can you confirm the private network for your instance on Hyper-V works (i.e. can you ping / arping from 10.0.0.5 the 10.0.0.16 / gw ?). After you tested the private network try to set another floating ip to another vm and ping that ip? Do you allow tcp/udp in your security groups? Alin

aserdean gravatar imageaserdean ( 2017-04-07 02:38:44 +0300 )edit

Yes, the private network working, I have instances on it (they run on KVM). instances on linux compute node have full functional networking. they can ping each other and gw, can reach internet, I can access them via SSH using floating ip address. What settings should I set in security group?

Laci gravatar imageLaci ( 2017-04-07 08:52:41 +0300 )edit