Bug #5258: Using pppoe WAN with ipv6 SLAAC, reply-to rules use the wrong interface address - pfSense - pfSense bugtracker

Actions

Copy link

Bug #5258

closed

Using pppoe WAN with ipv6 SLAAC, reply-to rules use the wrong interface address

Added by James Tandy about 9 years ago. Updated over 4 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Rules / NAT

Target version:

2.5.0

Start date:

10/05/2015

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

Affected Architecture:

Description

When enabling reply-to rules on WAN,
Where the WAN is PPPOE, configured by SLAAC,
When you add a rule, the reply-to address used is that of the physical interface, and not pppoeX.
This only applies to ipv6 rules.

With reply-to disabled:
pass in quick on pppoe1 inet proto icmp from any to 87.252.44.195 keep state label "USER_RULE: allow inbound ping"
pass in quick on pppoe1 inet6 proto ipv6-icmp all keep state label "USER_RULE: allow inbound icmpv6"

With reply-to enabled:
pass in quick on pppoe1 reply-to (pppoe1 212.42.162.226) inet proto icmp from any to 87.252.44.195 keep state label "USER_RULE: allow inbound ping"
pass in quick on pppoe1 reply-to (sge0 fe80::f2f7:55ff:fe0c:5700) inet6 proto ipv6-icmp all keep state label "USER_RULE: allow inbound icmpv6"

sge0 is the physical WAN interface.
The gateway IP is correct.