@scottalanmiller said in Ubuntu Ethernet before WiFi:
@hobbit666 said in Ubuntu Ethernet before WiFi:
@Pete-S said in Ubuntu Ethernet before WiFi:
@Pete-S said in Ubuntu Ethernet before WiFi:
So I would look at:
changing the NIC the software binds to (configuration files?)
A quick search seems to indicate that Minecraft Server have config file called server.properties
.
Inside that there is a setting called server-ip
.
Set that to the static IP of the computer's IP on the LAN and I'm guessing it will bind to your LAN port every time.
Yeah will give that a try.
For some reason you can't "bind" to a specific port. It's been a requested feature with M$ for a while now.
Such an easy thing to do, too.
With "port" are we talking about a NIC or tcp/ip port? Sometime people say port but are actually referring to a specific network interface which can cause confusion. So to clarify, port in the text below is tcp/ip port and not network interface.
The normal thing for a server application is to bind to all or one specific IP address that the server have and to a specific port. Not a specific NIC.
As you may or may not know this comes from the low level socket api that all OSes use but originated from unix (BSD). The function that tells a socket what ip & port to use is called bind
.
Higher level functions in programming languages such as java, python or whatever are usually just wrappers for the socket api.
From what I can see there seems to be options in the configuration files for Minecraft server to set which ports it should bind to as well. I don't have any experience with Minecraft, that info is just from a quick search.
Normal procedure if you want more control over a server and which IP addresses it actually replies on, is to have it bind to all IPs then employ access control with the OS firewall.
Default behavior for the bind
function is to actually bind to all IPs - if you don't specify an IP. So I would expect Minecraft server to actually bind to all IPs if none are specified. But the OS firewall may not be open to accept traffic on all interfaces.
On linux you can check what service are bound to what ports and IPs with netstat -tulpn
It will not show if the firewall is open or closed though (I think...) You have to check that as well.