Re: Unable to access Internet from an instance and accessing instance using floating-point IPs from external network
On Mon, Nov 21, 2022 at 7:39 PM vincent lee <vincentlee676@gmail.com> wrote:
After reviewing the post you shared, I believe that we have the correct subnet. Besides, we did not modify anything related to the cloud-init for openstack.
I didn't either. But I found it's a good test of the network! If you are using an image that doesn't rely on it you might not notice (but I would not recommend that).
After launching the instances, we are able to ping between the instances of the same subnet. However, we are not able to receive any internet connection within those instances. From the instance, we are able to ping the router IP addresses 10.42.0.56 and 10.0.0.1.
To make sure I understand: - 10.42.0.56 is the IP of the router external to OpenStack that provides internet access - This router is tested and working for devices outside of OpenStack - OpenStack compute instances can ping this router - OpenStack compute instances cannot reach the internet If that is correct, it does not sound like an OpenStack issue necessarily, but perhaps a missing default route on your compute instances. I would check that DHCP is enabled on the internal subnet and that it's providing everything necessary for an internet connection to the instances. Tobias
it should be missing a default route most of the time. or check IP tables on router namespace the DNAT and SNAT are working properly On Tue, Nov 22, 2022 at 9:40 AM Tobias McNulty <tobias@caktusgroup.com> wrote:
On Mon, Nov 21, 2022 at 7:39 PM vincent lee <vincentlee676@gmail.com> wrote:
After reviewing the post you shared, I believe that we have the correct subnet. Besides, we did not modify anything related to the cloud-init for openstack.
I didn't either. But I found it's a good test of the network! If you are using an image that doesn't rely on it you might not notice (but I would not recommend that).
After launching the instances, we are able to ping between the instances of the same subnet. However, we are not able to receive any internet connection within those instances. From the instance, we are able to ping the router IP addresses 10.42.0.56 and 10.0.0.1.
To make sure I understand: - 10.42.0.56 is the IP of the router external to OpenStack that provides internet access - This router is tested and working for devices outside of OpenStack - OpenStack compute instances can ping this router - OpenStack compute instances cannot reach the internet
If that is correct, it does not sound like an OpenStack issue necessarily, but perhaps a missing default route on your compute instances. I would check that DHCP is enabled on the internal subnet and that it's providing everything necessary for an internet connection to the instances.
Tobias
Just one more thing to check, did you edit the security-group rules to allow access to the outside world? Zitat von Adivya Singh <adivya1.singh@gmail.com>:
it should be missing a default route most of the time. or check IP tables on router namespace the DNAT and SNAT are working properly
On Tue, Nov 22, 2022 at 9:40 AM Tobias McNulty <tobias@caktusgroup.com> wrote:
On Mon, Nov 21, 2022 at 7:39 PM vincent lee <vincentlee676@gmail.com> wrote:
After reviewing the post you shared, I believe that we have the correct subnet. Besides, we did not modify anything related to the cloud-init for openstack.
I didn't either. But I found it's a good test of the network! If you are using an image that doesn't rely on it you might not notice (but I would not recommend that).
After launching the instances, we are able to ping between the instances of the same subnet. However, we are not able to receive any internet connection within those instances. From the instance, we are able to ping the router IP addresses 10.42.0.56 and 10.0.0.1.
To make sure I understand: - 10.42.0.56 is the IP of the router external to OpenStack that provides internet access - This router is tested and working for devices outside of OpenStack - OpenStack compute instances can ping this router - OpenStack compute instances cannot reach the internet
If that is correct, it does not sound like an OpenStack issue necessarily, but perhaps a missing default route on your compute instances. I would check that DHCP is enabled on the internal subnet and that it's providing everything necessary for an internet connection to the instances.
Tobias
Hi guys, sorry for the late reply. I noticed that the gateway I gave was not pingable and I will try it tomorrow and let you all know if it works out. Before I posted this discussion, I did a fresh installation of openstack. I have only modified the external network in init-runonce script. Will that cause a problem? I have attached an image of the modification I made before running the script as shown below. Other than that I have not made any changes to the configuration. Besides, I have not make any changes to the security-group rules regardless of the internet access. [image: image.png] Best regards, Vincent On Tue, Nov 22, 2022 at 3:58 AM Eugen Block <eblock@nde.ag> wrote:
Just one more thing to check, did you edit the security-group rules to allow access to the outside world?
Zitat von Adivya Singh <adivya1.singh@gmail.com>:
it should be missing a default route most of the time. or check IP tables on router namespace the DNAT and SNAT are working properly
On Tue, Nov 22, 2022 at 9:40 AM Tobias McNulty <tobias@caktusgroup.com> wrote:
On Mon, Nov 21, 2022 at 7:39 PM vincent lee <vincentlee676@gmail.com> wrote:
After reviewing the post you shared, I believe that we have the correct subnet. Besides, we did not modify anything related to the cloud-init for openstack.
I didn't either. But I found it's a good test of the network! If you are using an image that doesn't rely on it you might not notice (but I would not recommend that).
After launching the instances, we are able to ping between the instances of the same subnet. However, we are not able to receive any internet connection within those instances. From the instance, we are able to ping the router IP addresses 10.42.0.56 and 10.0.0.1.
To make sure I understand: - 10.42.0.56 is the IP of the router external to OpenStack that provides internet access - This router is tested and working for devices outside of OpenStack - OpenStack compute instances can ping this router - OpenStack compute instances cannot reach the internet
If that is correct, it does not sound like an OpenStack issue necessarily, but perhaps a missing default route on your compute instances. I would check that DHCP is enabled on the internal subnet and that it's providing everything necessary for an internet connection to the instances.
Tobias
-- thanks you. vincentleezihong 2garnet form2
participants (4)
-
Adivya Singh
-
Eugen Block
-
Tobias McNulty
-
vincent lee