Changes between Initial Version and Version 1 of Ticket #1161, comment 4


Ignore:
Timestamp:
12/11/19 16:05:34 (3 years ago)
Author:
mike_SF
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1161, comment 4

    initial v1  
    11Here's a new issue I just encountered.
    22
    3 We register devices that roam around via DDNS with a wget https:// call to an outside provider.  We obviously want the device's public IP address to be the one registered, so we have the following directive for IPv4:
     3We register devices that roam around via DDNS with a wget https:// call to an outside provider.  We obviously want the device's public IP address to be the one registered, not the address of the VPN's egress, so we have the following directive for IPv4:
    44
    55
     
    88}}}
    99
    10 When registering with DDNS server, due to the lack of the equivalent IPv6 directive, we're seeing the private fd00 address being registered (yes, we have to NAT IPv6 for various reasons, primarily privacy and SLAAC).
     10When registering with DDNS server, due to the lack of the equivalent IPv6 directive, we're seeing the VPN server's address being registered (yes, we have to NAT IPv6 for various reasons, primarily privacy and SLAAC).