Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    SOLVED New SG-3100 config issue

    Official Netgate® Hardware
    3
    4
    242
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      lenhuppe last edited by lenhuppe

      Installed my first Netgate today. IPv6 is not working and IPv4 is running very slow. I am connected to the net but at a fraction of the speed I had before the Netgate. My ISP is Xfinity/Comcast and my IPv6 works fine w/out the Netgate. I have tried resetting to factory defaults and running the setup wizard again but that has had no impact. I also tried adding a firewall rule that allows all IPv4 + IPv6 traffic to pass on the LAN but that has had no impact.

      Do I need to reinstall pfSense and try again?

      UPDATE:

      I needed to turn off IPv6 on both the LAN and WAN interfaces.

      Gertjan 1 Reply Last reply Reply Quote 0
      • Gertjan
        Gertjan @lenhuppe last edited by

        @lenhuppe said in SOLVED New SG-3100 config issue:

        I also tried adding a firewall rule that allows all IPv4 + IPv6 traffic to pass on the LAN but that has had no impact.

        Such a rule is present on LAN by default.
        Why adding a second ?

        No "help me" PM's please. Use the forum.

        L 1 Reply Last reply Reply Quote 0
        • L
          lenhuppe @Gertjan last edited by

          @Gertjan said in SOLVED New SG-3100 config issue:

          @lenhuppe said in SOLVED New SG-3100 config issue:

          I also tried adding a firewall rule that allows all IPv4 + IPv6 traffic to pass on the LAN but that has had no impact.

          Such a rule is present on LAN by default.
          Why adding a second ?

          I am a pfSense newb and found that tidbit while googling. It came from a tutorial on setting up pfSense to work with Comcast. The issue is that Comcast only supports a prefix of 64 by default. Therefore I have to disable ipv6 until I get that resolved.

          Thank you for pointing that out

          1 Reply Last reply Reply Quote 0
          • rdunkle
            rdunkle last edited by

            There is perhaps some other issue here.
            I have a customer with the SG-1100 and Xfinity/Comcast. I am using a Netgear C7100V in bridge mode. On pfsense I turned on WAN dhcpv6 debug mode, to find out what the system delegation prefix was. The log showed a /60 prefix. I do not think there is any other way in the pfsense ui to see the value of the system delegation prefix.
            On the LAN side of pfsense, I set ipv6 to "track interface", ID 0, selected WAN interface to track, left the prefix size at /64.

            ipv6 is working OK for all clients

            1 Reply Last reply Reply Quote 0
            • First post
              Last post