Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    1. Home
    2. pfSense® Software
    3. Development
    4. 21.02.2/2.5.1 Snapshots (Retired)
    Log in to post
    • Newest to Oldest
    • Oldest to Newest
    • Most Posts
    • Most Votes
    • Most Views
    • jimp

      pfSense Plus 21.02.2 / pfSense CE 2.5.1 RC Snapshots now available!
      • jimp

      1
      6
      Votes
      1
      Posts
      1305
      Views

      No one has replied

    • pete

      pfSense CE 2.5.1 RC update/upgrade
      • pete

      27
      0
      Votes
      27
      Posts
      3471
      Views

      pete

      13th of April, 2021

      Back to monitoring the WAN link. It is not resetting any more like before. The issues below appeared when I was streaming AOD last night. Working with XFinity to maybe correct these issues.

      Mon 4/12/2021

      18:59:30 MONITOR: WAN_DHCP has packet loss, omitting from routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|13.267ms|1.276ms|33%|down|highloss

      18:59:46 MONITOR: WAN_DHCP is available now, adding to routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|15.906ms|5.549ms|20%|online|loss

      18:59:57 MONITOR: WAN_DHCP has packet loss, omitting from routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|16.688ms|7.034ms|25%|down|highloss

      19:00:01 MONITOR: WAN_DHCP is available now, adding to routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|15.823ms|5.291ms|14%|online|loss

      19:00:04 MONITOR: WAN_DHCP has packet loss, omitting from routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|27.761ms|31.182ms|30%|down|highloss

      19:00:12 MONITOR: WAN_DHCP is available now, adding to routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|17.575ms|7.674ms|10%|online|none

      19:13:36 MONITOR: WAN_DHCP has packet loss, omitting from routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|18.989ms|11.389ms|33%|down|highloss

      19:13:38 MONITOR: WAN_DHCP is available now, adding to routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|17.675ms|10.165ms|20%|online|loss

      21:25:23 MONITOR: WAN_DHCP has packet loss, omitting from routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|15.089ms|5.734ms|21%|down|highloss

      21:27:26 MONITOR: WAN_DHCP is available now, adding to routing group Failover

      8.8.8.8|24.XX.XX.XX|WAN_DHCP|14.49ms|5.424ms|16%|online|loss

      All PFSense functions appear to work OK except for not seeing VPN status on Dashboard.

    • T

      Whats left?
      • techpro2004

      2
      1
      Votes
      2
      Posts
      210
      Views

      jimp

      Not much.

    • G

      Unbound SSL Errors
      • g.shaffer

      3
      0
      Votes
      3
      Posts
      229
      Views

      G

      @g-shaffer 2.5.1.r.20210406.1302 has resolved the issue.

    • G

      Status > DNS Resolver Shows No Data
      • g.shaffer

      9
      0
      Votes
      9
      Posts
      313
      Views

      G

      @jimp 2.5.1.r.20210406.1302 has resolved the issue. Thanks!

    • M

      OpenSSL: error:0201502D:system library:ioctl:Operation
      • mloiterman

      7
      1
      Votes
      7
      Posts
      220
      Views

      M

      @jimp

      Yup. I just updated to the latest snapshot and it's been fixed.

      Jim, you're awesome. Thanks so much.

    • R

      Continuing "Unbound crashes periodically with signal 11"
      • ryan-b

      1
      0
      Votes
      1
      Posts
      112
      Views

      No one has replied

    • G

      2.5.1-RC Routing Issue on Reboot
      • Griffo

      6
      0
      Votes
      6
      Posts
      434
      Views

      G

      Problem went away with the removal of Wireguard.

    • T

      21.02.2-RC IPSEC Status Widget
      • tve

      5
      0
      Votes
      5
      Posts
      261
      Views

      viktor_g

      @tve said in 21.02.2-RC IPSEC Status Widget:

      @jimp Two IKEv1 tunnels, first has 1 P2 in tunnel mode, the other 2 P2 also in tunnel mode. Sorry, I could not find Split connection setting.

      Fixed in the latest snapshot,
      see https://redmine.pfsense.org/issues/11435#note-6

    • B

      Slow DNS Response after reboot - 21.02.2
      • behemyth

      1
      0
      Votes
      1
      Posts
      152
      Views

      No one has replied

    • M

      WAN IPV6 gateway monitoring stops operating.
      • mmcvey7355

      2
      0
      Votes
      2
      Posts
      187
      Views

      jimp

      The last few comments on https://redmine.pfsense.org/issues/11454 should handle this, it was another simple fix.

      https://github.com/pfsense/pfsense/commit/ec3fd7e5e43ac28def2ff0bcd36c9b741a7fab32

    • M

      FRR Zebra / BGP do not seem to start on boot anymore
      • mfld

      4
      0
      Votes
      4
      Posts
      177
      Views

      viktor_g

      @mfld Unable to reproduce your issue
      Need more information about your configuration

    • M

      2.5.1 RC1 crash
      • maverick_slo

      3
      0
      Votes
      3
      Posts
      228
      Views

      jimp

      Do you have the rest of that crash dump? The info header you posted doesn't have nearly enough detail to tell what the nature of the crash is, unfortunately. There should be a lot more info in the textdump.tar file it offers to let you download.

    • G

      IPv6 Track Interface Not Working
      • g.shaffer

      3
      0
      Votes
      3
      Posts
      211
      Views

      G

      @jimp That worked. Thanks for the feedback.

    • G

      IPv6 Gateway Issue (see issue 11454)
      • g.shaffer

      14
      0
      Votes
      14
      Posts
      518
      Views

      G

      @jimp
      It has fixed the IPv6 Gateway issue, Thanks! But, I'm now seeing issues with Track Interface, I'll open up another thread.

    • P

      RC upgrade breaks pfBlockerNG
      • Pentangle

      1
      0
      Votes
      1
      Posts
      210
      Views

      No one has replied