0.3.0

[junkurihara]

Improvements

• Totally restructured and reimplemented all components
• [Breaking] Support multiple bootstrap resolvers, which requires to modify the config file.
• Periodic health check of all path candidates.
• Periodic nexthop IP address resolution via the proxy itself, bootstrap resolver is only used at the first time and fall-back.
• Periodic fetching of access token with refresh token.
• Hot reloading of configuration files, including block and override files.
• Configurable "user-agent" as whatever you like.

[przemyslaw0]

The bootstrap resolver feature could support DNS-over-TCP and to set the port arbitrarily. This would be useful in firewalled environments, when the UDP or ports other than 80/443 are blocked.

[junkurihara]

@przemyslaw0

The bootstrap resolver feature could support DNS-over-TCP and to set the port arbitrarily. This would be useful in firewalled environments, when the UDP or ports other than 80/443 are blocked.

That makes sense indeed. Thanks for your great suggestion.

I just remembered that even in my working environment, UDP 53 to external network is actually blocked. I will consider to put an option like bootstrap_dns_over_tcp = <boolean> and bootstrap_dns_port = <int>!

[przemyslaw0]

@junkurihara

What if the user wants to specify two different resolvers that use different ports and/or protocols (TCP and UDP)?

Maybe something like "tcp://208.67.222.222:443" or "udp://1.1.1.1:53" would be more suitable.