Re: [Sks-devel] seeking peers for keyserver.vanbaak.eu

[Todd Fleisher]

I see. The resolver I used only showed me your IPV4 addresses. Perhaps a more 
seasoned list member can advise if this will work properly as I’ve not yet come 
across such a setup. I believe the gossip protocol uses the hostname value 
provided on the stats page and am unsure how (or if) it would work to have the 
gossip using a different hostname/IP.

-T

> On Feb 17, 2019, at 10:23 AM, Michiel van Baak <address@hidden> wrote:
> 
> On Sun, Feb 17, 2019 at 09:26:55AM -0800, Todd Fleisher wrote:
>>> On Feb 16, 2019, at 6:19 AM, Michiel van Baak <address@hidden> wrote:
>>> 
>>> I am running SKS version 1.1.6, on keyserver.vanbaak.eu.
>>> The GOSSIP part is running on sks.pgp.vanbaak.eu because of internal
>>> routing and IP policies.
>> 
>> Can you clarify what you are trying to convey here? Both of those hostnames 
>> resolve to the same IP address currently & report:
>> 
>> Hostname: keyserver.vanbaak.eu
> 
> Yes, I can
> 
> My connection is fiber-to-the-home with 1 static ipv4 address and a
> static /48 ipv6 prefix.
> 
> The keyserver.vanbaak.eu and sks.pgp.vanbaak.eu resolve to the same ipv4
> address (the one and only I have) but they resolve to different ipv6
> addresses.
> This, because the vm running nginx has a different address than the one
> running sks.
> Since one can proxy all ports in nginx, except for the GOSSIP protocol,
> I pointed keyserver.vanbaak.eu to my webserver, and sks.pgp.vanbaak.eu
> to the sks server.
> 
> I hope this makes some sense.
> 
> --
> Michiel van Baak
> address@hidden
> GPG key: http://pgp.mit.edu/pks/lookup?op=get&search=0x6FFC75A2679ED069
> 
> NB: I have a new GPG key. Old one revoked and revoked key updated on 
> keyservers.

signature.asc
Description: Message signed with OpenPGP