Netgate SG-1000 microFirewall

Author Topic: IPv6 broken for pfsense.org sites  (Read 2341 times)

0 Members and 1 Guest are viewing this topic.

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +962/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
IPv6 broken for pfsense.org sites
« on: November 07, 2015, 03:43:00 pm »
« Last Edit: November 08, 2015, 02:42:26 am by doktornotor »
Do NOT PM for help!

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +962/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: IPV6 broken for pfsense.org sites
« Reply #1 on: November 08, 2015, 02:41:39 am »
I think the message has been missed. Guys, your IPv6 has been completely crippled for about a day, for entire *.pfsense.org (forums, blog, website, packages, redmine...)

Please fix it!
Do NOT PM for help!

Offline cmb

  • Hero Member
  • *****
  • Posts: 11228
  • Karma: +896/-7
    • View Profile
    • Chris Buechler
Re: IPv6 broken for pfsense.org sites
« Reply #2 on: November 09, 2015, 02:40:45 pm »
What doesn't work? They all load over v6 for me, and a lot of others judging by the v6 traffic levels.

Offline johnpoz

  • Hero Member
  • *****
  • Posts: 15168
  • Karma: +1413/-206
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #3 on: November 09, 2015, 05:03:16 pm »
yeah I just did a simple test from my remote linux box and looks good to me..

user@clean:~$ wget -6 www.pfsense.org
--2015-11-09 17:03:06--  http://www.pfsense.org/
Resolving www.pfsense.org (www.pfsense.org)... 2610:160:11:11::69
Connecting to www.pfsense.org (www.pfsense.org)|2610:160:11:11::69|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.pfsense.org/ [following]
--2015-11-09 17:03:06--  https://www.pfsense.org/
Connecting to www.pfsense.org (www.pfsense.org)|2610:160:11:11::69|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 19813 (19K) [text/html]
Saving to: ‘index.html’

100%[=================================================================================================>] 19,813      --.-K/s   in 0.04s

2015-11-09 17:03:07 (455 KB/s) - ‘index.html’ saved [19813/19813]
- An intelligent man is sometimes forced to be drunk to spend time with his fools.
- Please don't PM me for personal help
- if you want to say thanks applaud or https://www.freebsdfoundation.org/donate/
1x SG-2440 2.4.2-RELEASE-p1 (work)
1x SG-4860 2.4.2-RELEASE-p1 (home)

Offline gsiemon

  • Jr. Member
  • **
  • Posts: 80
  • Karma: +13/-0
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #4 on: November 09, 2015, 05:09:52 pm »
What doesn't work? They all load over v6 for me, and a lot of others judging by the v6 traffic levels.
From approx 12:00 UTC Saturday until sometime around 00:00 UTC Sunday (+/- a few hours as I was asleep) IPV6 access to any of the pfSense URLs either timed out or was very slow to load.  I spent most of Sunday here in Australia trying to figure out if it was something due to the 2.2.5 upgrade.  Everything is OK now but there were some significant problems during that time.  There are several threads where people made reference to the issue over the weekend:

https://forum.pfsense.org/index.php?topic=102042.0

https://forum.pfsense.org/index.php?topic=101967.msg569284#msg569284

https://forum.pfsense.org/index.php?topic=102081.0

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +962/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #5 on: November 09, 2015, 05:18:09 pm »
What doesn't work? They all load over v6 for me, and a lot of others judging by the v6 traffic levels.

Nothing worked for about 1,5 days... None of the sites loaded.
Do NOT PM for help!

Offline maverick_slo

  • Hero Member
  • *****
  • Posts: 829
  • Karma: +40/-3
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #6 on: November 10, 2015, 12:56:17 am »
+1

Offline bmeeks

  • Hero Member
  • *****
  • Posts: 3290
  • Karma: +862/-0
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #7 on: November 10, 2015, 07:30:19 am »
Another +1 for IPv6 issues over the weekend with pfsense.org.  I use a Hurricane Electric tunnel if that matters.  Sounds like the problem did not affect all IPv6 users, though.

Bill

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21566
  • Karma: +1471/-26
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #8 on: November 10, 2015, 12:18:21 pm »
I had issues hitting the forum on IPv6 over the weekend via HE.net tunnel - magically resolved itself yesterday morning. Ping worked the whole time.

AFAIK nothing was changed on our end, could have been somewhere in between
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline gsiemon

  • Jr. Member
  • **
  • Posts: 80
  • Karma: +13/-0
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #9 on: November 10, 2015, 03:48:37 pm »
I have a native IPv6 connection but did notice from traceroutes that traffic was going through HE to get to pfSense.  Maybe it was them.

Offline maverick_slo

  • Hero Member
  • *****
  • Posts: 829
  • Karma: +40/-3
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #10 on: November 11, 2015, 12:53:09 am »
On my side worked frome one ISP but not other...
It was some routing issue I guess...

Offline KOM

  • Hero Member
  • *****
  • Posts: 5602
  • Karma: +688/-23
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #11 on: November 11, 2015, 07:56:36 am »
Quote
It was some routing issue I guess...

A routing issue on the Internet?  Unheard of!

Offline maverick_slo

  • Hero Member
  • *****
  • Posts: 829
  • Karma: +40/-3
    • View Profile
Re: IPv6 broken for pfsense.org sites
« Reply #12 on: November 11, 2015, 08:06:12 am »
lol
My point was that maybe pfsense guys could do nothing about it :=)
That issue was on higher level... Unheard levels...