Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Private IPV6 address is not configurable #1738

Open
michaeldg opened this issue Mar 9, 2020 · 0 comments · May be fixed by #2262
Open

Private IPV6 address is not configurable #1738

michaeldg opened this issue Mar 9, 2020 · 0 comments · May be fixed by #2262

Comments

@michaeldg
Copy link

Hi,

From what I understand, the feature of public and private IPs is used for miab installations that are behind NAT.

I have a Linode box and Linode provided me with an extra IPv6 /64 range. This results in my Linode having 3 IPv6 addreses configured. Somehow it seams that I cannot remove the default IP addresses added by Linode.

I have found that it is possible to change the used public IP addresses in the configuration file /etc/mailinabox.conf. The same configuraton file also contains a record 'PRIVATE_IPV6_ADDRESS', but changing this has no effect. The installation mentions the (detected) IP, not the IP from the configuration and changes the configuration file in the process to the (detected, incorrect) IP.

Please change this so we can configure the private IPV6 address, as this is used for outgoing postfix SMTP connections. If this connection is with the wrong IPV6 address the suggested and automatically configured SPF records are incorrect.

Steps to reproduce:

  1. Create a cloud VM with two public IPV6 IPs (You can create one with Linode, and request a /64 IPV6 range for mail sending)
  2. Install MIAB normally, observe the private IP address that is detected by the installer
  3. Change the configuration file to the other IPV6 address
  4. Rerun installer
  5. Observe the same IPV6 address as in step 2

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant