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

Rule matching with "WAN address" for IPv6 is broken?

Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
2 Posts 2 Posters 3.0k Views
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.
  • B
    bkraptor
    last edited by Sep 6, 2013, 1:40 PM

    I have an inbound rule for IPv6 with destination selected as "WAN address" and protocol IPv6 from the drop-down lists. The traffic destined to the WAN IPv6 address is not matched by the rule and gets discarded by the default deny rule. When I replace the destination with "any", the traffic is not discarded any more.

    2.1-RC2 (amd64)
    built on Thu Sep 5 21:38:32 EDT 2013

    IPv4 is PPPoE, IPv6 is via DHCPv6, with "Use IPv4 connectivity as parent interface" checked.

    Another, possibly related, issue is that the IPv6 address is not listed under the WAN interface in Status -> Interfaces, nor in the text console menu, although it can be seen via ifconfig on the pppoe1 interface.

    1 Reply Last reply Reply Quote 0
    • J
      jimp Rebel Alliance Developer Netgate
      last edited by Sep 6, 2013, 5:02 PM

      Your last note may be correct there, if it can't determine the IP for that it may not know it for use in firewall rules.

      I ran a test here with a static config and it does properly form the expected rule.

      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
      1 out of 2
      • First post
        1/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received