Navigation

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

    IPv6 is down

    IPv6
    2
    4
    2499
    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.
    • G
      Gradius last edited by

      I did everything as in:
      http://doc.pfsense.org/index.php/Using_IPv6_on_2.1_with_a_Tunnel_Broker

      However when I try to ping or traceroute I get:
      [2.1-BETA0][**]/(3): ping6 2001:4860:4860::8888
      PING6(56=40+8+8 bytes) 2001:470::::1 โ€“> 2001:4860:4860::8888
      ping6: sendmsg: Network is down
      ping6: wrote 2001:4860:4860::8888 16 chars, ret=-1
      ping6: sendmsg: Network is down
      ping6: wrote 2001:4860:4860::8888 16 chars, ret=-1
      ping6: sendmsg: Network is down
      ping6: wrote 2001:4860:4860::8888 16 chars, ret=-1
      ping6: sendmsg: Network is down
      ping6: wrote 2001:4860:4860::8888 16 chars, ret=-1

      Why?

      1 Reply Last reply Reply Quote 0
      • jimp
        jimp Rebel Alliance Developer Netgate last edited by

        Not nearly enough info there.

        Please show the output of:

        ifconfig -a
        netstat -rn

        And also make sure that the he.net tunnelbroker server you're using can ping your WAN IP, if it can't ping your WAN IP, they won't send you traffic.

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • G
          Gradius last edited by

          Found out the problem.

          pfBlocker is blocking 66.220.2.74 for some odd reason. ย ???

          Snort is blocking 66.220.2.74, I did a whitelist including that IP on Snort, but even so is still blocking.

          pfBlocker might be the culpit, I'll need to test it with that turn off.

          Any simple way to do a whitelist for pfBlocker?

          1 Reply Last reply Reply Quote 0
          • G
            Gradius last edited by

            I did a whitelist for pfBlocker, will test when it changes IP (is working fine atm).

            Also, Snort isn't showing any IPv6 attack, only IPv4.ย  So it needs to gets updated.

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