Project

General

Profile

Actions

Bug #9324

closed

IPv6 on top of a PPPOE ipv4 interface assigns parent interface to default route, not pppoe interface

Added by James Tandy over 2 years ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Category:
Interfaces
Target version:
Start date:
02/14/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

Hi,
Have been seeing this since at least 2.4, and persists in 2.4.4-p2

WAN: vdsl, via modem on em1
ipv4 config: pppoe
ipv6 config: SLAAC

ISP provides link local only on wan, with an fe80::x gateway address.
When this interface comes up, pfsense sets the default route to the pppoe interfaces parent nic, rather than the pppoe1 interface.

This is easy to fix from console for a single ipv6 wan, simply change the default route and specify %pppoe1 rather than %em1
However I now have 2 ISPs who both support ipv6 - I am unable to get the second ISP working at all.

After a clean boot, this is what is required to get ipv6 traffic flowing:

[2.4.4-RELEASE][]/root: route n show default
route to: 0.0.0.0
destination: 0.0.0.0
mask: 0.0.0.0
gateway: 212.42.162.225
fib: 0
interface: pppoe1
flags: <UP,GATEWAY,DONE,STATIC>
recvpipe sendpipe ssthresh rtt,msec mtu weight expire
0 0 0 0 1492 1 0
[2.4.4-RELEASE][]/root: route -n6 show default
route to: ::
destination: ::
mask: ::
gateway: fe80::f2f7:55ff:fe55:d300%re1
fib: 0
interface: re1
flags: <UP,GATEWAY,DONE,STATIC>
recvpipe sendpipe ssthresh rtt,msec mtu weight expire
0 0 0 0 1500 1 0
[2.4.4-RELEASE][]/root: ping6 google.com
PING6 2a02:13a0:a006:1::1 -
> 2a00:1450:4009:80c::200e
^C
--- google.com ping6 statistics ---
6 packets transmitted, 0 packets received, 100.0% packet loss
[2.4.4-RELEASE][]/root: route n6 change default fe80::f2f7:55ff:fe55:d300%pppoe1
change net default: gateway fe80::f2f7:55ff:fe55:d300%pppoe1
[2.4.4-RELEASE][]/root: route -n6 show default
route to: ::
destination: ::
mask: ::
gateway: fe80::f2f7:55ff:fe55:d300%pppoe1
fib: 0
interface: pppoe1
flags: <UP,GATEWAY,DONE,STATIC>
recvpipe sendpipe ssthresh rtt,msec mtu weight expire
0 0 0 0 1492 1 0
[2.4.4-RELEASE][]/root: ping6 google.com
PING6 2a02:13a0:a006:1::1 -
> 2a00:1450:4009:80c::200e
16 bytes from 2a00:1450:4009:80c::200e, icmp_seq=0 hlim=57 time=16.731 ms
16 bytes from 2a00:1450:4009:80c::200e, icmp_seq=1 hlim=57 time=16.450 ms
16 bytes from 2a00:1450:4009:80c::200e, icmp_seq=2 hlim=57 time=16.734 ms
16 bytes from 2a00:1450:4009:80c::200e, icmp_seq=3 hlim=57 time=17.052 ms
16 bytes from 2a00:1450:4009:80c::200e, icmp_seq=4 hlim=57 time=16.207 ms
^C
--- google.com ping6 statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 16.207/16.635/17.052/0.286 ms

Actions #2

Updated by Jim Pingle about 2 years ago

  • Category set to Gateways
  • Affected Version changed from 2.4.4_2 to All
Actions #4

Updated by Jim Pingle over 1 year ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0
Actions #5

Updated by Renato Botelho over 1 year ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

Pull request has been merged. Thanks!

Actions #6

Updated by Viktor Gurov over 1 year ago

  • Status changed from Feedback to Resolved
  • Affected Architecture All added
  • Affected Architecture deleted (amd64)

works as expected on 2.5.0.a.20200207.1337

Actions #7

Updated by Viktor Gurov over 1 year ago

  • Status changed from Resolved to Feedback

small update:
https://github.com/pfsense/pfsense/pull/4186

It adds $slaacusev4iface parameter,
Otherwise using one parameter $ipv6usev4iface by both Static IPv6 and SLAAC confuse WebGUI

Actions #8

Updated by Jim Pingle over 1 year ago

  • Status changed from Feedback to Pull Request Review
Actions #9

Updated by Renato Botelho over 1 year ago

  • Status changed from Pull Request Review to Feedback

PR has been merged. Thanks!

Actions #10

Updated by James Tandy over 1 year ago

Can confirm this is present and working on build 2.5.0.a.20200213.1525

Thanks :)

Actions #11

Updated by Renato Botelho over 1 year ago

  • Status changed from Feedback to Resolved
Actions #12

Updated by Kristopher Kolpin 12 months ago

Is there a similar fix for DHCP6?

i.e. $dhcp6usev4iface parameter?

Maybe this is related to ticket #8136 ?

Actions #13

Updated by Jim Pingle 12 months ago

  • Category changed from Gateways to Interfaces
Actions #14

Updated by Viktor Gurov 11 months ago

  • Status changed from Resolved to New
Actions #15

Updated by Renato Botelho 11 months ago

  • Status changed from New to Feedback

PR has been merged. Thanks!

Actions #16

Updated by Viktor Gurov 9 months ago

  • Status changed from Feedback to Resolved

2.5.0.a.20210201.2350 fixed

Actions

Also available in: Atom PDF