Anyone using IPv6 yet?

optize

• October 26, 2013 13:29

I found a bug, well... according to cPanel, it's not a bug. Trying to figure out if it affects anyone but me. Everytime you enable IPv6 on a customer account, it will change your outbound IPv6 IP to that customer's IPv6 IP. To test (you need to have IPv6 already on the box) - curl Did the IP's change? They do on all of my boxes, trying to figure out if it's the way we configure the primary IPv6 IP, or if this is a bug that cPanel refuses to acknowledge. Thanks!

• 

  Infopro

  • October 27, 2013 05:41

  [QUOTE]or if this is a bug that cPanel refuses to acknowledge.
  Do you have a ticket ID you can post here?

  0
• 

  Radeonpower

  • October 28, 2013 20:52

  Happens here also, I noticed this in Exim.

  0
• 

  cPanelMichael

  • October 29, 2013 15:32

  Please open a support ticket so we can take a closer look: Submit A Ticket You can post the ticket number here so we can update this thread with the outcome. It's important to keep in mind that we only support IPv6 for website content at this time. IPv6 support for sending and receiving email will come in a future release. Thank you.

  0
• 

  ChrisFirth

  • November 06, 2013 09:02

  [quote="optize, post: 1491141"> Everytime you enable IPv6 on a customer account, it will change your outbound IPv6 IP to that customer's IPv6 IP.
  I have not had a chance to play with IPv6 support yet, I will update my test server now and give it a go to verify what I'm saying below. I suspect this happens if when an account has an IPv6 address assigned cPanel then binds the address to the server. When sending traffic out via IPv6 there is a selection algorithm that gets run to choose which address to send the traffic out via. If more than one address meets all the conditions then the one that was added last is picked. Generally the fix for this is set "preferred_lft 0" when the address is bound so it is marked as deprecated and it will not be used for outgoing traffic unless it is replying to something sent to it. If you run 'ip a l' (assuming Linux), check to see if the IPv6 addresses have 'deprecated' next to them like this: 3: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 .... inet6 2400:8900::something/64 scope global deprecated valid_lft forever preferred_lft forever inet6 2400:8900::something2/64 scope global deprecated valid_lft forever preferred_lft forever If they don't, then its probably the selection algorithm doing it's job and picking the latest added address. If they do say deprecated something else is happening. ----- Just tested it on my test cPanel server and I can confirm the same problem, assigning an IPv6 address to a user causes the server to use that IP as the outgoing address for IPv6, address is not deprecated.

  0
• 

  bazzi

  • November 21, 2013 07:37

  Same problem here. I also see that if you do # service restart network
  It loses al the IPv6 adresses in the ifconfig.

  0
• 

  cPanelMichael

  • November 21, 2013 13:24

  [quote="bazzi, post: 1512542">Same problem here. I also see that if you do # service restart network
  It loses al the IPv6 adresses in the ifconfig.
  Does restarting "ipaliases" resolve this issue? Thank you.

  0
• 

  bazzi

  • November 22, 2013 12:52

  [quote="cPanelMichael, post: 1512791">Does restarting "ipaliases" resolve this issue? Thank you.
  No but in the ticket it suggested to restart cpipv6 and that resolved it.

  0

Please sign in to leave a comment.