alternative_access
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
alternative_access [2025/01/04 16:12] – bent | alternative_access [2025/01/04 18:48] (current) – bent | ||
---|---|---|---|
Line 26: | Line 26: | ||
===== Routing ===== | ===== Routing ===== | ||
- | Once decided to have two routers on the LAN you have to use a routing protocol in order to keep the router | + | Once decided to have two routers on the LAN you have to use a routing protocol in order to keep the routers |
- | [[Alternate address|Alternate routed address space]] | + | We have decided to solely use IPv6 for this function. Each of us have delegated a /64 sub-domain of our IPv6 allocation to the other. We have also set up routing tables so that connection requests to this sub-domain are routed through the tunnel back to the other. |
+ | |||
+ | The details of the sub-allocation and the routing is described in [[Alternate address|Alternate routed address space]] | ||
===== DNS considerations ===== | ===== DNS considerations ===== | ||
+ | |||
+ | Connecting back to our servers through the tunnel does not require actions beyond what is described above. If, however, it should be necessary to use the sub-delegated addresses as source address for sending mail, further action is required. | ||
+ | |||
+ | In order to have our sent email properly accepted by foreign mail server it is necessary to provide reverse name lookup for the mail servers. For practical reasons we decided to delegate the administration of the delegated sub-domain to the one that uses it. Details of the name space delegation is described in [[cross-allocation|IPv6 Cross allocation]] | ||
alternative_access.1736007132.txt.gz · Last modified: 2025/01/04 16:12 by bent