Ubuntu Ethernet before WiFi
-
@Pete-S said in Ubuntu Ethernet before WiFi:
Inside that there is a setting called
server-ip.Looks like that server-ip option is only for java edition
Should of said i'm running Bedrock. -
@hobbit666 said in Ubuntu Ethernet before WiFi:
@scottalanmiller said in Ubuntu Ethernet before WiFi:
@hobbit666 said in Ubuntu Ethernet before WiFi:
Or even disable the WiFi during boot and only bring it up after fully boot, or delayed say 5mins after
I've not played with this configuration. But my thought would be maybe do...
- Disable Wifi on boot completely
- make sure Ethernet is good on boot
- Make an "@boot" cronjob with a short delay (1 minute should be fine) and have that enable the wifi
If the cron job enables the WiFi would it still be enabled if I rebooted the machine?
The point of the cron job is that it starts wifi at boot time.
-
@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.Port is a different issue. Would be nice to have but would also cause a lot of end user confusion as it would break certain mechanisms.
-
@hobbit666 said in Ubuntu Ethernet before WiFi:
Yes i mean it can't bind to a specific NIC,
That's a much harder thing to do in the configs because it's crazy hard and constantly variable. If you had that feature, and any hardware changed, it would just stop working and people would be confused.
You CAN also fix this by running it in a VM and controlling things at the VM level.
-
OK silly question slightly off topic.
If i'm setting up SSH keys between my Windows machine and the ubuntu server does my windows username need to be the same as the ubuntu server?
i.e. windows user is hobbit, but ubuntu only has a user minecraft? Do i need to create a user called hobbit on ubuntu?
-
@hobbit666 said in Ubuntu Ethernet before WiFi:
OK silly question slightly off topic.
If i'm setting up SSH keys between my Windows machine and the ubuntu server does my windows username need to be the same as the ubuntu server?
i.e. windows user is hobbit, but ubuntu only has a user minecraft? Do i need to create a user called hobbit on ubuntu?
No, you just need to pass the correct user to the ubuntu server when connecting with ssh/scp. IE
ssh minecraft@ubuntuip -
@travisdh1 said in Ubuntu Ethernet before WiFi:
No, you just need to pass the correct user to the ubuntu server when connecting with ssh/scp. IE
ssh minecraft@ubuntuipThought so, must be doing something wrong
still asking for the minecraft password not "SSH Key" password
Edit - Think it's just Terminal in Win11 - Putty seems to work -
@hobbit666 said in Ubuntu Ethernet before WiFi:
If i'm setting up SSH keys between my Windows machine and the ubuntu server does my windows username need to be the same as the ubuntu server?
Nope, no need to match. Are you using the Windows built in SSH system from PowerShell (that's what I do.)
-
@hobbit666 said in Ubuntu Ethernet before WiFi:
@travisdh1 said in Ubuntu Ethernet before WiFi:
No, you just need to pass the correct user to the ubuntu server when connecting with ssh/scp. IE
ssh minecraft@ubuntuipThought so, must be doing something wrong
still asking for the minecraft password not "SSH Key" password
Edit - Think it's just Terminal in Win11 - Putty seems to workTerminal should just be using OpenSSH.
-
@scottalanmiller said in Ubuntu Ethernet before WiFi:
Terminal should just be using OpenSSH.
This might be the issue. Will have a play after my holidays
-
@hobbit666 said in Ubuntu Ethernet before WiFi:
@scottalanmiller said in Ubuntu Ethernet before WiFi:
Terminal should just be using OpenSSH.
This might be the issue. Will have a play after my holidays
In theory, Window's OpenSSH implementation is completely identical to the one on Linux and BSD. I can't way I've tested much in Windows 11, but on 10, it's definitely identical.
-
@scottalanmiller said in Ubuntu Ethernet before WiFi:
@hobbit666 said in Ubuntu Ethernet before WiFi:
@scottalanmiller said in Ubuntu Ethernet before WiFi:
Terminal should just be using OpenSSH.
This might be the issue. Will have a play after my holidays
In theory, Window's OpenSSH implementation is completely identical to the one on Linux and BSD. I can't way I've tested much in Windows 11, but on 10, it's definitely identical.
I've not had any issues with it.
-
@scottalanmiller said in Ubuntu Ethernet before WiFi:
@hobbit666 said in Ubuntu Ethernet before WiFi:
@scottalanmiller said in Ubuntu Ethernet before WiFi:
Terminal should just be using OpenSSH.
This might be the issue. Will have a play after my holidays
In theory, Window's OpenSSH implementation is completely identical to the one on Linux and BSD. I can't way I've tested much in Windows 11, but on 10, it's definitely identical.
"Completely identical" is a bit of a stretch since it's a fork, so it has additions and changes and might not support everything the main project does. It's likely lagging behind the main project too.
But "works the same" or "practically the same" or "has the same code base"...
Microsoft only has one fork, so windows version shouldn't make any noticeable difference.
https://github.com/PowerShell/openssh-portablePS. In OP's case he has probably hasn't the right key in openssh. OpenSSH and Putty don't share their ssh keys. They are in different folders.
