Project

General

Profile

Actions

Bug #7298

closed

IPv6 on a second interface doesn't work until the router is pinged

Added by Andy Wang about 7 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
02/22/2017
Due date:
% Done:

0%

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

Description

I'm using 6rd for IPv6 and have two LAN interfaces both of them configured to Track WAN interface and each has a unique IPv6 prefix Id.

The first LAN interface, everything always works fine.

On the second LAN interface, after rebooting pfsense, systems on that interface are able to acquire a IPv6 address via DHCPv6 and SLAAC just fine. However, there router advertisement doesn't work. None of the systems are able to route IPv6 outbound.

from linux 'ip neighbor' doesn't show the router advertisement.

However, if I ping the router's IP address from the host, everything just starts to working and 'ip neighbor' starts to show the router advertisement. This will work fine until the next time pfsense is rebooted when I have to ping the router again.

There is a firewall rule for the interface allowing all IPv6 traffic.

Actions #1

Updated by Jim Pingle over 4 years ago

  • Category set to Interfaces
Actions #2

Updated by Andy Wang over 4 years ago

This issue stopped at some point. I don't recall if I did something, or an update took care of it or what, but I'd completely forgotten I had filed this bug. I think this can be resolved. Sorry I don't have the specific details on how it may have gone away.

Actions #3

Updated by Jim Pingle over 4 years ago

  • Status changed from New to Closed

OK, thanks for the update!

Actions

Also available in: Atom PDF