[
https://issues.apache.org/jira/browse/CLOUDSTACK-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Monos updated CLOUDSTACK-535:
-----------------------------------
Description:
Issue:
When a new router VM is generated and started the initial firewall rules allow
only port 53 on UDP. Router VMs should allow port 53 on TCP is well due to
longer resolutions can switch to TCP for example cPanel. The cPanel installer
will not run if it cannot resolve over TCP.
Workaround:
Login to the router VM and execute:
iptables -A INPUT -i eth0 -p tcp -m tcp --dport 53 -j ACCEPT
Resolution:
I'm not sure where the initial firewall rules are coming from (maybe systemVM
ISO?) but there this new rule should be added.
was:
Issue:
When a new router VM is generated and started the initial firewall rules allow
only port 53 on UDP only. Router VMs should allow port 53 on TCP is well due to
longer resolutions can switch to TCP for example cPanel. The cPanel installer
will not run if it cannot resolve over TCP.
Workaround:
Login to the router VM and execute:
iptables -A INPUT -i eth0 -p tcp -m tcp --dport 53 -j ACCEPT
Resolution:
I'm sure where the inital firewall rules are coming from (maybe systemVM ISO?)
but there this new rule should be added.
> Virtual Router DNS is restricted to UDP only
> --------------------------------------------
>
> Key: CLOUDSTACK-535
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-535
> Project: CloudStack
> Issue Type: Bug
> Components: Network Controller
> Affects Versions: 4.0.0
> Reporter: Tamas Monos
> Priority: Minor
>
> Issue:
> When a new router VM is generated and started the initial firewall rules
> allow only port 53 on UDP. Router VMs should allow port 53 on TCP is well due
> to longer resolutions can switch to TCP for example cPanel. The cPanel
> installer will not run if it cannot resolve over TCP.
> Workaround:
> Login to the router VM and execute:
> iptables -A INPUT -i eth0 -p tcp -m tcp --dport 53 -j ACCEPT
> Resolution:
> I'm not sure where the initial firewall rules are coming from (maybe systemVM
> ISO?) but there this new rule should be added.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
