View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000826 | LDMud 3.5 | Networking | public | 2013-08-20 20:21 | 2022-10-06 19:17 |
| Reporter | zesstra | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | closed | Resolution | suspended | ||
| Summary | 0000826: Is a constant source IP address for connecting remote hosts really necessary? | ||||
| Description | Currently the driver always uses that source IP address for communicating with other hosts that the driver once found upon startup. I would like to discuss, if this is really necessary. Some aspects of this behaviour I would consider harmful. First it makes things in the driver more complicated (e.g. IPv4 vs IPv6). The code would be easier if we let the kernel/OS decide what source address/interface is most suitable for connecting to a remote host. Second it reacts badly if the interface goes down or its routes are not working. If we don't enforce a specific source address, that would not matter as much if the host has more than one interface: it just uses another one. Currently we have to restart the driver to solve the situation. The disadvantage is, that other hosts may see the mud connecting from different addresses, if the host system has more than one. However - is this really such a bad thing? The mud host has several valid addresses after all. As long as the mud is reachable at all these addresses (which we of course assume), any answers will reach it. Remote hosts could just use the last address they have (which they usually just do for a long time...). BTW: I asked the same questions on the ldmud-talk mailing list. | ||||
| Tags | No tags attached. | ||||
