The pfSense Store

Author Topic: 24 hours of 2.2.5, ~1.3 TB of mostly auto-updates  (Read 3397 times)

0 Members and 1 Guest are viewing this topic.

Offline cmb

  • Hero Member
  • *****
  • Posts: 11230
  • Karma: +893/-7
    • View Profile
    • Chris Buechler
24 hours of 2.2.5, ~1.3 TB of mostly auto-updates
« on: November 06, 2015, 07:13:49 pm »
Y'all chew up some bandwidth. :)

Pretty typical of the first 24 hours after release.

Thanks to our friends at NYI for the bandwidth.

Offline luckman212

  • Hero Member
  • *****
  • Posts: 726
  • Karma: +59/-0
    • View Profile
    • @luckman212 - github
Re: 24 hours of 2.2.5, ~1.3 TB of mostly auto-updates
« Reply #1 on: November 07, 2015, 04:36:00 pm »
Nice! That's something you don't see everyday (thankfully)

Any idea when 2.2.5 images will be posted to https://portal.pfsense.org/firmware/memstick/ ?

Offline Harvy66

  • Hero Member
  • *****
  • Posts: 2217
  • Karma: +204/-12
    • View Profile
Re: 24 hours of 2.2.5, ~1.3 TB of mostly auto-updates
« Reply #2 on: November 08, 2015, 09:25:44 am »
That's a lot of blocked outgoing IPv6, yes?

Offline divsys

  • Hero Member
  • *****
  • Posts: 919
  • Karma: +91/-1
    • View Profile
Re: 24 hours of 2.2.5, ~1.3 TB of mostly auto-updates
« Reply #3 on: November 08, 2015, 01:14:12 pm »
Quote
That's a lot of blocked outgoing IPv6, yes?

Did I miss something?

I don't see any blocked IPv6 traffic in that graph, just a whole whack of outgoing traffic.

I have seen a few notes about an issue with IPv6 traffic being mangled at the moment, but that graph doesn't say much about that IMHO

Don't know if there's as much v6 traffic as you might expect, looks like ~10:1 v4 over v6 but that's really a guess based on 1 graph.

 (Kudos on 2.2.5 to all at pfSense, it's very clean and solid so far)
-jfp

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +956/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: 24 hours of 2.2.5, ~1.3 TB of mostly auto-updates
« Reply #4 on: November 08, 2015, 02:38:50 pm »
Did I miss something?
I don't see any blocked IPv6 traffic in that graph, just a whole whack of outgoing traffic.

Very likely. Since the traffic apparently doesn't even get routed properly to the destination... Frankly, I'd expect some working monitoring in place. Been broken for two days, would feel kinda ashamed.  :(
Do NOT PM for help!

Offline grandrivers

  • Sr. Member
  • ****
  • Posts: 566
  • Karma: +13/-2
    • View Profile
Re: 24 hours of 2.2.5, ~1.3 TB of mostly auto-updates
« Reply #5 on: November 09, 2015, 10:00:47 am »
come on there using Apinger to monitor it, its all good :)
pfsense 2.4 super micro A1SRM-2558F
C2558 8gig ECC  60gig SSD
tripple Wan dual pppoe

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +956/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: 24 hours of 2.2.5, ~1.3 TB of mostly auto-updates
« Reply #6 on: November 09, 2015, 10:06:49 am »
Yah, that'd fully explain it. :D ROFL.
Do NOT PM for help!

Offline dennypage

  • Hero Member
  • *****
  • Posts: 697
  • Karma: +133/-0
    • View Profile
Re: 24 hours of 2.2.5, ~1.3 TB of mostly auto-updates
« Reply #7 on: November 09, 2015, 11:07:22 am »
LOL!

come on there using Apinger to monitor it, its all good :)

Offline Harvy66

  • Hero Member
  • *****
  • Posts: 2217
  • Karma: +204/-12
    • View Profile
Re: 24 hours of 2.2.5, ~1.3 TB of mostly auto-updates
« Reply #8 on: November 09, 2015, 11:27:29 am »
Quote
That's a lot of blocked outgoing IPv6, yes?

Did I miss something?

I don't see any blocked IPv6 traffic in that graph, just a whole whack of outgoing traffic.

I have seen a few notes about an issue with IPv6 traffic being mangled at the moment, but that graph doesn't say much about that IMHO

Don't know if there's as much v6 traffic as you might expect, looks like ~10:1 v4 over v6 but that's really a guess based on 1 graph.

 (Kudos on 2.2.5 to all at pfSense, it's very clean and solid so far)

I seem to have mixed the two IPv6 colors. I blame poor LCD monitor color reproduction.