Mojira Archive
BDS-18213

LAN discovery ignores port settings

If you set individual ports (e.g. 20132), the server will still use 19132 for lan discovery.

There are multiple work arounds out there. e.g.: not to start the server until the server.properties was modified for the 1st time. This works until you update (in my case from 1.19.70 to 1.19.71), now it is again using 19132 for lan discovery.

 

[2023-03-18 12:10:21:734 INFO] IPv4 supported, port: 20132: Used for gameplay
[2023-03-18 12:10:22:336 INFO] IPv4 supported, port: 19132 used for LAN discovery 

 

The expected behavior is to use the port from IPv4 from server.properties also for lan discovery instead of falling back to default.

Environment

Linux / docker

Linked Issues

Comments2

Hi

Does this issue occur only on Linux or it can be reproduced on Windows bedrock server?

This ticket will automatically reopen when you reply.

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

History7

McFCologne

Changed description:

If you set individual ports (e.g. 20132), the server will still use 19132 for lan discovery.

0

There are multiple work arounds out there. e.g.: not to start the server until the server.properties was modified for the 1st time. This works until you update (in my case from 1.19.70 to 1.19.71), now it is again using 19132 for lan discovery.

0

 

0

The expected behavior is to use the port form IPv4 from server.properties also for lan discovery instead of falling back to default.

McFCologne

Changed description:

If you set individual ports (e.g. 20132), the server will still use 19132 for lan discovery.

0

There are multiple work arounds out there. e.g.: not to start the server until the server.properties was modified for the 1st time. This works until you update (in my case from 1.19.70 to 1.19.71), now it is again using 19132 for lan discovery.

0

 

0
0
0[2023-03-18 12:10:21:734 INFO] IPv4 supported, port: 20132: Used for gameplay
0
0
0
0[2023-03-18 12:10:22:336 INFO] IPv4 supported, port: 19132 used for LAN discovery 
0
0

 

0

The expected behavior is to use the port form IPv4 from server.properties also for lan discovery instead of falling back to default.

McFCologne

Changed description:

If you set individual ports (e.g. 20132), the server will still use 19132 for lan discovery.

0

There are multiple work arounds out there. e.g.: not to start the server until the server.properties was modified for the 1st time. This works until you update (in my case from 1.19.70 to 1.19.71), now it is again using 19132 for lan discovery.

0

 

0
0
0[2023-03-18 12:10:21:734 INFO] IPv4 supported, port: 20132: Used for gameplay
0
0
0
0[2023-03-18 12:10:22:336 INFO] IPv4 supported, port: 19132 used for LAN discovery 
0
0

 

0

The expected behavior is to use the port form IPv4 from server.properties also for lan discovery instead of falling back to default.

If you set individual ports (e.g. 20132), the server will still use 19132 for lan discovery.

0

There are multiple work arounds out there. e.g.: not to start the server until the server.properties was modified for the 1st time. This works until you update (in my case from 1.19.70 to 1.19.71), now it is again using 19132 for lan discovery.

0

 

0
0
0[2023-03-18 12:10:21:734 INFO] IPv4 supported, port: 20132: Used for gameplay
0
0
0
0[2023-03-18 12:10:22:336 INFO] IPv4 supported, port: 19132 used for LAN discovery 
0
0

 

0

The expected behavior is to use the port from IPv4 from server.properties also for lan discovery instead of falling back to default.

Maciej Piornik
[MCQA] Kinga Izdebska
[MCQA] Kinga Izdebska

Resolution: UnresolvedIncomplete

[Mod] Jarl-Penguin
Incomplete
McFCologne
0
0
Unconfirmed
1.19.70