Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I suppose ESXi has several ways of attaching the VM to the network. With other hypervisors like KVM or VirtualBox, default attachment is NAT, which requires port forwarding to access the VM. I have had countless situations where I could not reach a VM because I had set up the network attachment incorrectly.
So, in order to help you, it would be good to know:
how does ESXi attach the VM
from where and how are you trying to connect to the VM (if you issue commands, show the commands)
where do you define the route you mention, and what is that route precisely
which logs did you check, what do you mean by "blockage in terms of my router address", and how do you come to that conclusion
the network topology
Last edited by berndbausch; 03-09-2021 at 11:50 PM.
I suppose ESXi has several ways of attaching the VM to the network. With other hypervisors like KVM or VirtualBox, default attachment is NAT, which requires port forwarding to access the VM.
ESXi is a type 1 hypervisor, which works quite differently to the ones you mentioned.
VMs operating under ESXi are configured by default to operate the same way as any other machine on your network. That is to say that the hypervisor acts as a virtual switch by default, and you don't need to set up any port forwarding to access the VMs.
I have setup our route to forward any requests on all ports to this system, (also tried selective ports like 22/80) - but
No matter what, I cannot seem to have anyone from the outside world touch these systems.
Looking at the logs, it seems I'm getting some blockage in terms of my router address... but I thought I have it all open for port 80.
Before starting to look at this from "outside"; let's look at "inside"...
On your Linux VM; are the ports actually open? Look at output of: netstat -ntlp
Is there a firewall on your Linux VM? If so, are these ports allowed thru that firewall?
Try to access port 80 (or 22) from another machine on the same network. Does that work?
Simple question. Do you have a static ip? Generally for any server stuff you will need a static ip. In my area a static ip isn't just nice to have. It's the only way to get mostly unrestricted access to ports. They may all be blocked on the isp side as they don't want people running servers on them.
Hey Jim and everyone that replied... I'm afraid to admit - I think you guys are right.. looks like telus blocks these ports for "residential" users.. (me).
Thank you guys - this one now makes sence.. still sucks, but at least I know.
Thanks again all!
Quote:
Originally Posted by jmgibson1981
Simple question. Do you have a static ip? Generally for any server stuff you will need a static ip. In my area a static ip isn't just nice to have. It's the only way to get mostly unrestricted access to ports. They may all be blocked on the isp side as they don't want people running servers on them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.