[
https://issues.apache.org/jira/browse/CLOUDSTACK-10016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104646#comment-16104646
]
ASF subversion and git services commented on CLOUDSTACK-10016:
--------------------------------------------------------------
Commit 471b68698a9e64877c1f4611fa216ee8434da30f in cloudstack's branch
refs/heads/4.9 from [~slair1]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=471b686 ]
CLOUDSTACK-10016: VPC VR doesn't respond to DNS requests from remote access vpn
clients (#2201)
When enabling remote access VPN, a new interface is created upon client
connecting via VPN. The DNS service (dnsmasq) is set only to listen on
interfaces that are active when it starts. Thus VPN users are provided the VR's
IP address for DNS resolution, but it is not actually listening for DNS
requests.
> VPC VR doesn't respond to DNS requests from remote access vpn clients
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-10016
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10016
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router, VPC
> Affects Versions: 4.9.0
> Environment: All
> Reporter: Sean Lair
> Labels: patch
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When enabling remote access VPN, a new interface is created upon client
> connecting via VPN. The DNS service (dnsmasq) is set only to listen on
> interfaces that are active when it starts. Thus VPN users are provided the
> VR's IP address for DNS resolution, but it is not actually listening for DNS
> requests.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
