[FIXED BUG] Plesk Firewall script does not change IPv6 packet forwarding configuration

Follow

Comments

4 comments

  • Avatar
    Michel Otte

    The workaround/fix (which is in Obsidian) effectively kills IPv6 router advertisements for those who need it. Why not make things like these configurable with the firewall? Having things hard-coded in a script is (to put it gently) not the way to go.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Michel Otte

    As I understand, in your case, the server automatically gets the IPv6 address assigned. 

    Indeed, such scenario isn't taken into account. It's recommended to have static server addressing to avoid issues with e.g. services like Nginx filing to start when the address isn't assigned.

    Please, could you share your scenario in details and suggest the functionality in question at Plesk UserVoice portal: https://plesk.uservoice.com/forums/184549-feature-suggestions

    Thank you for the feedback.

    0
    Comment actions Permalink
  • Avatar
    Michel Otte

    Hello Ivan,

    That is correct, and I also understand that Plesk recommends people to set up static IP addresses over dynamic assignment.

    In cloud environments it is however very common to have the address assignments taken care of by the cloud platform / through cloud init and it becomes more & more cumbersome to make Plesk work in these environments. In these envionments, while still using dynamic address allocation, the system normally will have the same IP address assigned all the time, unless it is being transfered, migrated or cloned. And the OS can take care of properly starting services like nginx as soon as the network is considered up (i.e. network-online.target).

    I'm not directly saying Plesk must support dynamic address assignment (although I think it should), but at least not make it impossible.

    Another example is the life time of IPv6 addresses, whenever it is set by the OS to be lower than "forever", Plesk refuses to allow this address to be used by Plesk. While I do understand the reasoning behind this, it makes it much harder (if not impossible for most users) to use IPv6 addresses in Plesk when running in environments like AWS when people are using dynamic address assigments.

    Maybe my perception of how to use Plesk correctly in these environments is flawed, so please correct me if I'm wrong or point me to the documentation that would clarify correct usage of Plesk in environments like these.

    I added my comments / vote to the plesk uservoice concerning this issue as well: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/37327264-support-dynamically-assigned-ipv6-addresses-on-ple

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Michel Otte

    Thank you very much for your comment to the feature suggestion and valuable feedback.

    Popular suggestions are likely to be implemented.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request