SOLVED Connection to Minecraft Bedrock Server (outside LAN) running in Ubuntu VM in FreeNAS

[NASOD6572]

Hi,

I currently setup a Minecraft Bedrock Server on my FreeNAS machine for my kids. The server is running on an Ubuntu 18.04 "Bionic Beaver" and seems to run without issue. It can be accessed from inside our LAN but when I attempt to access it from outside the LAN, I cannot get a connection. I have opened the required port (19132) which I verified in the Server.Properties folder. I am using a DDNS service (no-IP.com) for the external IP address.

I feel comfortable I have all the port forwarding and DDNS setting correct; I had setup a Minecraft Java Edition server & had IP cameras I could remote into with port forwarding and could connect from outside our LAN without issue.

I am not sure if I need to bridge my VM network card to the host machines NIC?

I am very inexperienced with most of this.
Any help would be greatly appreciated!

FreeNAS Box
HP Z420 Workstation
Intel(R) Xeon(R) CPU E5-1650 v2 # 3.50GHZ
FreeNAS 11.3-U2.1
Intel Gigabit Ethernet Network Server Adapter I350-T4 V2 Quad Ports 1000Mbps OEM
Netgear - Orbi Ac3000 Tri-Band Mesh Wi-Fi System
Netgear N600 Cable Modem (C3700)

 

[Samuel Tai]

No need to bridge the VM's NIC to the host's NIC; this is already happening in the background. Did you port forward to the VM's IP or to the host's IP?

 

[NASOD6572]

No need to bridge the VM's NIC to the host's NIC; this is already happening in the background. Did you port forward to the VM's IP or to the host's IP?

Thanks for the reply!

I believe my VM has the same IP as host with a port tied to it. To clarify, my FreeNAS has an IP of 192.168.1.156 and I VNC into the Ubuntu VM with VNC Viewer at 192.168.1.156:5649. To answer your question, I am port forwarding to the 192.168.1.156 and using the suggested Minecraft Bedrock port. I had also tried using this with port triggering. Is there a way to specify the port of the VM? I will include some screen shots of my router's port forwarding/triggering setup pages.

 

[Samuel Tai]

No, run ifconfig -a inside the VM. You should have a different IP. The VNC IP isn't the same as your VM's IP.

 

[NASOD6572]

No, run ifconfig -a inside the VM. You should have a different IP. The VNC IP isn't the same as your VM's IP.

Okay. I tired that and attached is the result. I see two IP addresses 192.168.1.65 (this is the IP of my PiHole DNS) and the other is 192.168.1.255. I assume it is the one ending in .255?

 

[NASOD6572]

I did try the .255 with no luck.

The second part of the return "flags" doesn't sound good. Do I have something setup incorrectly within the VM?

 

[Samuel Tai]

No, your VM IP is 192.168.1.65.

 

[NASOD6572]

Worked like a charm!

Thanks for the help!

I cannot find where I mark this topic as solved. Found it. Thanks again!