View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000827 | LDMud 3.5 | Networking | public | 2013-08-20 23:25 | 2018-03-11 22:16 |
| Reporter | zesstra | Assigned To | zesstra | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | i686 | OS | GNU/Linux | OS Version | 4.0 |
| Target Version | 3.5.1 | ||||
| Summary | 0000827: __HOST_IP_NUMBER__ returns wrong information on IPv6 systems | ||||
| Description | __HOST_IP_NUMBER__ relies on host_ip_number, which is struct in_addr. in_addr is a 32 wide integer. On systems using IPv6 addresses, 96 bits get lost. Example: on Nightfall the reported __HOST_IP_NUMBER__ was: 5e17:fa18:0000:0000:0000:0000:0000:0000. (on some systems, in_addr is unsigned long, but even that is too short.) BTW: The usage of in_addr is not recommened. ;-) | ||||
| Tags | No tags attached. | ||||
|
|
I can't reproduce that behavior. For IPv6 systems in_addr is #defined to in6_addr (in comm.h), so this should pose no problem. |
|
|
Strange. I remember that I observed the truncation on my home system as well. However, Nightfall just confirmed that it currently works as expected. So lets close it. ;-) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-08-20 23:25 | zesstra | New Issue | |
| 2017-10-04 19:42 | zesstra | Status | new => confirmed |
| 2017-10-04 19:42 | zesstra | Target Version | 3.5.0 => 3.5.1 |
| 2018-02-03 23:23 | Gnomi | Note Added: 0002449 | |
| 2018-03-11 22:16 | zesstra | Assigned To | => zesstra |
| 2018-03-11 22:16 | zesstra | Status | confirmed => closed |
| 2018-03-11 22:16 | zesstra | Resolution | open => no change required |
| 2018-03-11 22:16 | zesstra | Note Added: 0002459 |
