<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal"><p dir="auto">Hi All,</p>
<p dir="auto">As a follow-up to the thread, "Can it be done? - IPv6 only Relay" I linked the new OpenBSD Relay via an IPv4 over IPv6 tunnel to the other relay I operate.<br>
So there is: SJC01 / 328E54981C6DDD7D89B89E418724A4A7881E3192 and now SJC02 / 366BC592BC0154C0CD1D35C0E77D8F2C7F0B843E<br>
Both share the same public IP, as it's on atlas :-) I can see no issues sharing:<br>
SJC01 ORPort is on 80.127.117.180:443 / [2001:985:e77:10::4]:443 (DirPort 80)<br>
SJC02 ORPort is on 80.127.117.180:993 / [2001:985:e77:10::6]:993 (DirPort 8080)</p>
<p dir="auto">What I can't seem to get rid of is the warning:<br>
The IPv4 ORPort address 80.127.177.180 does not match the descriptor address 80.127.117.180. If you have a static public IPv4 address, use 'Address <IPv4>' and 'OutboundBindAddress <IPv4>'. If you are behind a NAT, use two ORPort lines: 'ORPort <PublicPort> NoListen' and 'ORPort <InternalPort> NoAdvertise'.</p>
<p dir="auto">I think I tried every combo of ORPort NoListen/NoAdvertise and Address/OutboundBindAddress, but I don't seem to be able to get rid of this.</p>
<p dir="auto">What I have now is:<br>
ORPort [2001:985:e77:10::6]:993<br>
ORPort <<INTERNAL IP>>:993 NoAdvertise<br>
ORPort 80.127.177.180:993 NoListen<br>
Address 80.127.117.180<br>
OutboundBindAddress <<INTERNAL IP>><br>
OutboundBindAddress [2001:985:e77:10::6]</p>
<p dir="auto">Port 993 and 8080 are one-on-one pushed through to the new node with DNAT/Port forward from the 80.127.117.180.</p>
<p dir="auto">This on:<br>
[userhost ~]$ tor --version<br>
Tor version 0.3.1.9 (git-727d3f1b5e6eeda7).<br>
[userhost ~]$ uname -a<br>
OpenBSD host 6.2 GENERIC#306 amd64</p>
<p dir="auto">The daemon reports "Self-testing indicates your ORPort is reachable from the outside. Excellent." / "Self-testing indicates your DirPort is reachable from the outside. Excellent. Publishing server descriptor." so that seems to be A-OK.</p>
<p dir="auto">Any suggestions (or should I "just" ignore this as mentioned on tor-dev @ Tue Jan 24 04:20:27 UTC 2017 in subject: "[tor-dev] log: ORPort/DirPort address does not match descriptor address")?</p>
<p dir="auto">Thx,<br>
Stijn</p>
</div>
</div>
</body>
</html>