|
| Reporter | thejackimonster | Assigned To | thejackimonster | Due Date | |
|---|
| Priority | normal | Severity | minor | Reproducibility | always |
|---|
| Status | confirmed | Resolution | open | |
|---|
| Product Version | Git master | |
|---|
| Target Version | 1.0.0 | |
|---|
|
| Summary | 0009263: Transport is ignoring disabled IPv6 |
|---|
| Description | If you manually disable IPv6 via configuration, the transport service still forwards IPv6 addresses to the communicators which then can't handle them, causing the queue creation to fail. However transport never really recognizes that it's a ridiculous request that can not work because it only looks at the prefix of addresses which currently specifies underlying protocols like "udp" or "tcp" - not whether IPv4 or IPv6 is supported. |
|---|
| Additional Information | I think we need some kind of error signal for that to reduce unnecessary requests. A different solution would be using a different prefix for IPv6 addresses. So the communicator wouldn't register to all "udp" or "tcp" addresses but only supported IPv4 or IPv6 specifically. Technically both optimizations would also work together. But I think the second option is the cleaner solution to drop IPv6 address requests if not supported more easily. I just don't know how much overhead it brings to change prefixes from "udp-" to "udp4-" and "udp6-". |
|---|
| Tags | No tags attached. |
|---|
|