it is a problem -- using 43110 port on Linux

### it is a problem -- using 43110 port on Linux for listening of ZeroNet localhost-server.

## why?

because port range (on Linux by default) from 32768 upto 60999 used for **ephemeral port range** . for outgoing connections mostly and other getting dynamic port purposes.

see -- https://en.wikipedia.org/wiki/Ephemeral_port and https://www.ncftp.com/ncftpd/doc/misc/ephemeral_ports.html .

see sysctl on Arch Linux (all default settings):

```
$ sysctl net.ipv4.ip_local_port_range
net.ipv4.ip_local_port_range = 32768 60999
```

## what the problem with using a port from dynamic (ephemeral) range?

the problem is -- every time there is a chance (it is a low chance) that ZeroNet failes to start with some probability (it is a low probability).

there is a chance that ANY PORT from range 32768~60999 is **already busy** (and you CAN NOT PREDICATE IT!) when you are starting a ZeroNet on 43110 port.

you could replace 43110 for example to 23110. it would solve conflict with ephemeral range!

## what if I use FreeBSD, not Linux?

in this case you have no problems. you can close the issue-ticket with ``WONTFIX``. and you could suggest to Linux-users to apply Barmin's patch on their computers.

FreeBSD follows IANA recommendations.

## 43110 is legacy! we can not just change this one to another port. all instructions are written to using 43110 port. all URLs are with this port. how it could be changed now?!

you **should** do port changing. you should admit wrong port selecting was.

the early admit it, the less consequestions would be in long perpective.

today almost nobody knows about ZeroNet -- few people would suffer from port changing.

but tomorrow more people could be suffer from port changing.

## what the problem if the program starts successfully not every time? it is the low probability to fail! and failure doesn't happen on FreeBSD!

making or not making bugged software -- is a philosophical question. life is short. I would understand if you didn't want to fix it.

thanks in advance

No file or test is named. Start by locating the listener configuration and all instructions or URLs that use port 43110, then trace how the server starts on Linux. Done means the port choice and its documented references are handled consistently and startup avoids the reported ephemeral-port conflict.

索引モデルが issue の本文から書いたものです。