I have an Ubuntu Instance (10.20.20.122) in Microstack. I can reach outside world from it but it is not reachable from outside network.For example, from the host (physical) LAN it is not reachable ( it is reachable only from host). There is a br-ex (10.20.20.1) bridge already available with the installation of Microstack.
My host is Ubuntu 1804 Desktop
Host IP is 193.166.x.y
I want to ping the instance from other hosts as well (such as 193.166.x.y1,y2,y3.. etc.).
Your help/suggestion is greatly appreciated. Thanks a million.
I'm not sure if you're still looking for a solution. I've just published an approach to solve this problem in my blog. The link is:
https://connection.rnascimento.com/2021/03/08/openstack-single-node-microstack/
I've included some explanation why we can't change the default CIDR for br-ex and suggested a workaround.
Related
I have the following topology:
Basically 2 subnets, 10.0.27.0 and 192.168.0.0.
I have a floating ip that I assign to one of the machines using the interface in the 10.0.27.0 subnetwork, and it works fine. I added the rules for allowing the ssh traffic. However, when I try to do the same for the interface in the subnet 192.168.0.0, it doesn't work. After a nmap I can see that the port is closed, so I don't know what is happening. Any help is appreciated.
So many possible reason,
Did subnet 192.168.0.0 has opened port? did you test it first?
Did you try to change the subnet into 192.168.0.1? test by changing the subnet into that first. Using default subnet end with 0.0 or 1.1 value sometimes in different environment cause a problem.
You may share what environment you setup this topology and how you do this?
Is it through virtualised network environment or using physical network (switches or router).
I've run into a problem adding IP's to an SME server VM.
Determining if ip address xxx.xxx.xxx.xx is already in use for device eth3...
Error, some other host(mac address) aleady uses address xxx.xxx.xxx.xx.
Now, of course, I started looking at other servers hosted in Proxmox and outside of it as well, finding no other device using the IP addresses in question.
You could ping one of the addresses, but not the other.
More precisely I could ping the local address, but not the public one.
I realised that the device using the IP's is actually Proxmox itself. When I disabled the interfaces in the host (ifdown vmbr6) I could assign the address to the server in question after that.
The IP's are configured like this in the Proxmox network tab.
vmbr6 Linux Bridge enp5s0f0 xxx.xxx.xxx.xx 255.255.255.0
Now I might add that the SME server is being migrated using this guide:
https://www.caretech.io/2017/10/17/migrating-virtualbox-vdi-to-proxmox-ve-5/
Though I don't think it's related to the networking issue.
So steps that I've taken to try and fix the issue are:
Rebooted the SME server
Restarted the networking service on the SME server
Rebooted Proxmox
Removed network interfaces from the SME server
Changed the interface model from VirtIO to IntelE1000
Tried changing the MAC addresses
I've been battling this issue for 2 days and any and all help would be appreciated. Kind of in a hurry to migrate our services from VirtualBox to Proxmox.
Thank you.
We have an hyper-v machine in our DMZ with an Ubuntu machine on it. SonarQube is installed on the VM. When we try to access it from inside the network by IP there is nothing wrong and it works fine. We have setup a firewall route to forward all traffic from the internet to the VM. The forwarder as we setup is correct as we used it multiple times with other servers and works fine. The VM has 1 NIC with the internal IP on it. Is there something we are missing? If you need any more information please let me know. Thanks in advanced.
I have found the issue.
In the hosts file there was no local host setup.
From internal we connected by ip so there was no issue. The files were setup to connect to localhost so it did not know where to go. thanks for the support.
First I must say that I have no idea what kind of problem it is (Ubuntu/Windows/vmware/secureW2), so I hope anyone can select the necessary information from this mess.
I am running an Ubuntu 15.04 guest on a Windows 10 host using the vmware Virtual Machine. The Ubuntu internet icon in the right hand corner claims that it has a (wired) connection, yet I can't browse or ping google. Windows 10 is successfully connected by wi-fi, vmware uses a bridged connection (automatic) and my router enables DHCP. I can successfully ping my router from within the VM (at least, I assume 192.168.1.1 still refers to my actual router, and not some virtual router). In windows I can see two network adapters running (VMnet1 and VMnet8), both of which say they're enabled but have no internet access. I tried installing the bridge protocol in them, I tried using NAT instead of a bridge, but all to no avail. I was still connected just a few days ago when I was at school, which makes me think SecureW2 (a program responsible for connecting me to the school wi-fi) could also be involved somehow.
Everyone thanks in advance!
Turns out it was DNS related, caused by Ubuntu and SecureW2. The /etc/resolv.conf file was set up specifically for the LAN at school, for which I blame SecureW2. I "solved" it by adding my router IP to (the top of) the name server list, though I know this is only a practical solution.
I have a cloonix simulated network with debian virtual machines.
I'd like to install and update stuff on the vms.
How do I connect them to internet via my host computer ?
thanks.
why not ask the author?
You should not rely on help on cloonix, communication on the product has been small and not many know about it.
To reach the internet from a virtual machine, the host must be connected to the internet and the file /etc/resolv.conf of the host must be valid.
If the above is ok, then connect an interface of the vm to the cloonix_slirp_admin_vlan and do dhclient on this interface from within the guest.
Then your vm should be connected to the internet (check your /etc/apt/sources.list to have apt-get).
You should connect eth1 (for example) of vm to "cloonix_slirp_admin_vlan" which is always in hidden. Then input "dhclient eth1" in the console of vm, then the vm can connect to the Internet. There is an example, I hope it will help you:
http://www.brianlinkletter.com/upgrade-a-guest-vm-in-the-cloonix-network-simulator/