• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Firewall problem for Incomming connections

P

P. Marian

Guest
I have recentlly updated my Plesk Panel installation from version 10.3.1 to 10.4.4. After playing with my Server I have realized that my server is accepting connection to all TCP ports on which I have not explicitly denied access. This situation seems to occur only when "IPv6 Neighbor Discovery" service is ALLOWed to pass the firewall.

Can you please check and eventually provide an update?

---------------------------------------------------------------
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk 10.4.4, openSUSE 11.4, i386

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
1) Open plesk, goto Firewall
2) remove all access rules to port <80> (or another port). When I said remove, it means DELETE. Take another port if possible.
3) enable "IPv6 Neighbor Discovery"
4) deny "System policy for incoming traffic"

ACTUAL RESULT
access to port <80> (or another) is allowed !!!

EXPECTED RESULT
access to port <80> should be denied.

ANY ADDITIONAL INFORMATION
it seems that there is no plesk-firewall program anymore, instead plesk interface is settings only the iptables. After checking the commands used to configure the firewall rules, I have realized that after "firewall-active.sh" is created (script which simulates the plesk-firewall), when enabling (ACCEPT) the "IPv6 Neighbor Discovery" settings, we will have something like this:

...

/usr/sbin/iptables -A INPUT -p udp -j ACCEPT/DROP
/usr/sbin/iptables -A INPUT -p tcp -j ACCEPT/DROP
/usr/sbin/ip6tables -A INPUT -p icmpv6 --icmpv6-type 134/0 -j ACCEPT/DROP
/usr/sbin/ip6tables -A INPUT -p icmpv6 --icmpv6-type 135/0 -j ACCEPT/DROP
/usr/sbin/ip6tables -A INPUT -p icmpv6 --icmpv6-type 136/0 -j ACCEPT/DROP
/usr/sbin/ip6tables -A INPUT -p icmpv6 --icmpv6-type 137/0 -j ACCEPT/DROP

...

Well, I have reasons to believe, that first two commands are wrong.
--------------------------------------------------------------
 
Me too.

Not a security hole?

Why are not they worried about is why a big topic.


Enable(default) IPv6 Neighbor Discovery
#iptables -L > enable.txt

Disable IPv6 Neighbor Discovery
#iptables -L > disable.txt

# diff disable.txt enable.txt

< ACCEPT udp -- anywhere anywhere
< ACCEPT tcp -- anywhere anywhere
---
> DROP udp -- anywhere anywhere
> DROP tcp -- anywhere anywhere

What's a wonderful rule.
 
Last edited:
I found that denying all for 'IPv6 Neighbor Discovery' also blocks FTP access so beware with disabling it.
 
Back
Top