I am hoping to connect to a Tomcat server on a local host from virtual machines running on VMWare Station that connects to the host with a NAT virtual network.
I started a Tomcat server with port 8080 on my host PC.
The host normally has the following interfaces:
Loopback interface, IP: 127.0.0.1
An interface for the ethernet, IP: 10.10.31.194 Gateway: 10.10.31.254
The IP and DNS values are automatically assigned.
A virtual interface for the virtual network VNet8, IP: 192.168.129.1 Gateway: 192.168.129.2
The IP and DNS values are automatically assigned. (This interface appears after the VMNet 8 is setup, to reduce confusion)
I can connect to a webpage (say /helloProject/helloPage.html) on the Tomcat server with the following URLs:
http://127.0.0.1:8080/helloProject/helloPage.html
http://10.10.31.194:8080/helloProject/helloPage.html
Then I setup my VMWare Station and opened a Network Address Translation network with the following configurations:
VMNet8
DHCP: Enabled
Subnet Address: 192.168.129.0
Subnet Mask: 255.255.255.0
Gateway IP: 192.168.129.2
But I cannot connect to the helloPage.html webpage through:
http://192.168.129.1:8080/helloProject/helloPage.html
Either from the host itself with IP 192.168.129.1, or from a Linux CentOS virtual machine with IP 192.168.129.128 on the same network.
However, pinging the host from the host or the Linux VM I get response:
ping 192.168.129.1
Reply from 192.168.129.1: bytes=32 time<1ms TTL=128
...
Can anyone suggest something to try so as to make the connection work?
In addition: VM (192.168.129.128) can reach Gateway (192.168.129.2) as well as host (192.168.129.1). But host (192.168.129.1) cannot reach Gateway (192.168.129.2), ping no response. Strange.
Check if you have adress=0.0.0.0 in server.xml Connector's tag for port 8080. It will tell Tomcat to listen on all interfaces available on the host.
Restart Tomcat after the change.
Related
QUESTION:
Is there a way to trigger Tailscale to restart in a scenario like the following so that packets again flow to a remote Tailscale subnet over a backup ISP connection?
Scenario: Tailscale does not reconnect after my upstream router fails over to its backup ISP connection.
Prior to failover, local client machines can ping public IP addresses -- 8.8.8.8 for example -- as well as private IP addresses on the other side of a Tailscale subnet router -- 10.0.0.2 for example.
After failover, local clients regain public Internet access, but the private network on the other side of the Tailscale subnet router remains unreachable. The remote Tailscale subnet never becomes reachable again, even after waiting over 15 minutes.
The upstream router fails back after plugging the local WAN1 ethernet cable back in. Clients can still access the public Internet and can again reach the remote Tailscale subnet.
Test configuration:
Tailscale is running on a local Linux machine with IP forwarding enabled.
IP address is 192.168.0.2.
Default route is via 192.168.0.1.
Tailscale flags:
--advertise-routes=192.168.0.0/24
--snat-subnet-routes=false
--accept-routes
Local upstream router has two WAN ports configured for failover only.
WAN1 connects to a cable modem in bridge mode.
WAN2 connects to an LTE router in bridge mode.
LAN IP address is 192.168.0.1.
Static route to 10.0.0.0/8 via 192.168.0.2.
Tailscale is running on a remote EC2 instance in an AWS VPC with IP forwarding enabled.
IP address is 10.0.0.2.
Default route is via 10.0.0.1.
Tailscale flags:
--advertise-routes=10.0.0.0/8
--snat-subnet-routes=false
--accept-routes
tailscaled generally reacts to linkchange events, like links going up or down, and figures out which interface has the default route. If both interfaces remain up and both interfaces have a default route, it may not know which one to use.
I want to access a web-server running on my local Vagrant VM on say network A from a different host machine's browser connected to network B. I have used following in my vagrant file and forwarding ports accordingly :
config.vm.network "private_network", ip: "192.168.59.49"
It's working fine if I try to access the server from my local machine's browser but not from a machine connected to a different network.
You can open and forward your 80 port from local machine to vm or other port like 8080.
You can put the VM in the same network with your machine via DHCP or give it a static IP
Create a VPN with all the machines from where you wannt to access you VM
In GNS3, I have configured the DHCP pool on the router R1, and I have a vmware VM (Ubuntu 16.04), another router R2 and VPCs are connected to R1. The R2 and VPC can get their IP address without a problem, however, the vmwareVM can't receive the IP address.
Note that:
the station is configured as host-only
the connect a host virtual adapter to this network is checked
the VMware Workstation DHCP Server is turned OFF
No configuration on my local PC Network Connections (DHCP)
Once I type the command dhclient eth0 to get the IP address from dhcp, it freezes and returns nothing and no IP address is assigned.
I want to know what is the problem that causes that issue and how to solve it.
Thank you.
My mistake was in the configuration of my VMware network adapter (VMnet2) in my network adapter in my host.
so in order to get the IP address from the DHCP router: I did the following steps:
Create a virtual network (VMnet2) in the virtual network editor
of VMware.
I checked the "Host-only" option
I checked the
"connect a host virtual adapter to this network" option
Uncheck the "use local DHCP service to distribute IP address to VMs".
Do not change the default configuration of the VMnet from your
network connexion options.
I hope that will help someone has the same issue as me
I in a remote Server (I call it host machine) setup the OpenStack Ocata.
And in the OpenStack Ocata I created a VM, the VM use the Security Group (named allow ping & ssh), which is created by myself:
Now, I can use my Mac ping the VM. but can not ssh connect to the VM.
And in the VM(it's IP is 192.168.1.4 and floating IP is 103.35.202.3), I can ping 192.168.1.1 and 103.35.202.1(the host machine's public IP), but can not ping google.com or other public IP.
Why in my Mac I can ping the VM but can not ssh to it?
Why in the VM I can ping the host machine, but can not ping other public IP?
where is the issue?
Currently the only Egress traffic allowed out is for ICMP. Egress is missing for TCP/UDP. Add in Egress rules for both UDP (should help resolve the DNS issue) and TCP (should resolve the SSH issue.)
After adding in the Egress rules for TCP - test ssh again.
After adding in the Egress rules for UDP - test DNS resolution, if you are still running into issues then you may want to verify the DNS servers used when configuring the network.
I have linux server installed with RHEL. My network is configured with natted IPs.
I am confused how can I set the RDNS.A public IP is bonded with server but ifconfig shows only privet natted IP 10.1.... like that