Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: IPv6 static vs autoconf/privacy addresses and Incapsula  (Read 756 times)

rdk

  • Newbie
  • *
  • Posts: 2
    • View Profile
IPv6 static vs autoconf/privacy addresses and Incapsula
« on: January 20, 2017, 07:38:26 AM »

Hi!

I've been struggling to understand this for a few days now.

I have an HE IPv6 tunnel and its really nice.  (Thanks by the way).

I have a /48 and use a mixture of autoconf and static IPv6 addresses.

I noticed the other day that I could not get to t-mobile.com website from my desktop.  I dug further and it appears that incapsula is blocking my queries.  I have a static IPv6 address 2001:470:e499:1::7b

On a windows 10 PC, I have a EUI-64 or privacy/autoconf IPv6 address.  It could talk just fine to the t-mobile website via my HE tunnel.

As soon as I configured the windows 10 box to use a static assigned IPv6 address  2001:470:e499:2::75 and not the autoconf one, the t-mobile website stopped responding.  When I re-enabled autoconf address on this box, started working again.

From other devices in my network (ipads, linux laptops, android phones), I can get to the t-mobile website.  These devices all have auto-configured IPv6 addresses.

t-mobile's website is behind an incapsula proxy of some sort.

Why would incapsula block some IPv6 addresses in my net and not others?  Seems like a strange security parameter or setting.

Note that I can ping6 any of these ipv6 website addresses and they respond so I don't believe its a IP-layer issue.

Same goes for trying to connect to www.incapsula.com -- blocks static ipv6 addresses, allows dynamic ipv6 addresses.  They won't respond to support emails since I'm not a customer.  And, would not be fun to try to get through the phalanx of support people at t-mobile to get them to explain whats going on either.

Hoping some folks in HE land have heard of this.

I can post data to back up my hypothesis if need be.

Thanks,

Bobby
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2568
    • View Profile
Re: IPv6 static vs autoconf/privacy addresses and Incapsula
« Reply #1 on: January 22, 2017, 12:56:18 PM »

SLAAC gives you a gateway...when you assigned yourself a static address, did you assign yourself the correct gateway?
Logged

rdk

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: IPv6 static vs autoconf/privacy addresses and Incapsula
« Reply #2 on: January 22, 2017, 07:09:40 PM »

Hi!

Yes, I can ping6 the website in question so i believe the ipv6 route to/from works.  I can telnet port 80 to the website address and get back a proxy error when I don't tell the proxy which host I'm trying to reach.

I did some experimenting on a windows pc with selectively changing bytes in the static ipv6 host portion. 

The host's original static IPv6 address was 2001:470:e499:2::75  That system was not able to connect to the webserver.

When I changed the ipv6 address to 2001:470:e499:2:200:200:0:0:75, it was able to connect to the website.

2001:470:e499:2:2000:2000:0:75 fails

2011:470:e499:2:0:1:0:75 works

Lots of other variants worked, didnt work, etc.  I couldnt really discern a pattern based on the IPv6 addressing constraints that I'm aware of.

Also, the router I'm using is a linux box I've built/configured and am routing through my HE ipv6 tunnel.

Thanks,

Bobby
Logged