IPv6 incoming is silently dropped



  • I'm running a Hurricane Electric tunnel, and outgoing traffic is working fine for both the firewall and all clients. Incoming traffic, however (e.g., ssh, http, smtp and friends) appears to just… not exist? My firewall logs show no IPv6 traffic of any sort when there should be incoming traffic, and every online service test I find simply times out when I give one of my IPv6 addresses. Anyone have any idea where I can look for clues on where the data is being dropped?


  • Rebel Alliance Global Moderator

    Are you seeing it on pfsense?  Do a sniff on your tunnel.. You should see your monitoring for sure.. See attached.. Now send a ping to something behind pfsense..  Do you see that come through the tunnel?






  • Still not sure why the traffic never showed on the firewall logs, but apparently when I moved my IPv6 rules from my WAN ruleset to my tunnel ruleset everything started magically working and communicating. Why wouldn't the blocked messages have shown up along with everything else? :(

    [EDIT]Ok, I have a suspicion… Coming from FreeBSD and manual manipulation of the firewall rules, I know there should be a base (early) rule to by default block everything (and hopefully log as well). If I knew where to find that rule in the pfsense interface, I suspect it's set to block/log on WAN, and (apparently) to block (not log) on the tunnel interface.



  • Guessing maybe you were just trying ICMP? There was a bug in the GUI's firewall log display for ICMPv6 in versions pre-2.3, where it'd be in the log but not displayed in the GUI.



  • @cmb:

    Guessing maybe you were just trying ICMP? There was a bug in the GUI's firewall log display for ICMPv6 in versions pre-2.3, where it'd be in the log but not displayed in the GUI.

    No, I was running a web-based IPv6 SMTP test, and also trying to access IMAP via my phone (also IPv6). Both attempts always timed out, but when I moved my rules over to the tunnel ruleset they started working… never saw any block messages.