Bug #3949
closedDynamic DNS public IP check always uses default gateway
0%
Description
When using the "Use Public IP" option of RFC 2136 dynamic DNS updates, you'll always end up with the public IP of the interface where the default route resides, not that of the interface selected.
CB Updated by Chris Buechler almost 12 years ago
- Subject changed from RFC 2136 public IP check always uses default gateway to Dynamic DNS public IP check always uses default gateway
- Priority changed from Normal to High
Updated subject to reflect full extent of issue - it's all dynamic DNS services, not just RFC 2136.
RB Updated by Renato Botelho almost 12 years ago
- Assignee set to Renato Botelho
CB Updated by Chris Buechler almost 12 years ago
- Status changed from New to Confirmed
CB Updated by Chris Buechler almost 12 years ago
- Assignee changed from Renato Botelho to Chris Buechler
this does set CURLOPT_INTERFACE, which should force source IP selection, and then route-to handle accordingly. I have a good test case, back to me for testing.
EL Updated by Ermal Luçi almost 12 years ago
The issue here should be coming from the route-to.
Since routing table need to have static routes to allow entries going the right interface.
If the static routes are not there route-to policies on pfSense will override the source selection.
CB Updated by Chris Buechler almost 12 years ago
- Status changed from Confirmed to Resolved
this was fixed by coincidence when something else got fixed, my systems where this was an issue are now fine.