Project

General

Profile

Actions
Copy link

Bug #8429

closed

radvd/IPv6 broken in 2.4.3 when using a LAN bridge

Added by Spencer Hakim over 6 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Luiz Souza
Category:
IPv6 Router Advertisements (radvd/rtsold)
Target version:
2.4.4
Start date:
04/03/2018
Due date:
% Done:

0%

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

Description

Due to the fix for #6974 included in 2.4.3 (commits 1, 2, 3), radvd no longer works when using a bridge as the LAN interface due to bridges not actually having any media. Without radvd, IPv6 routes aren't sent to clients and IPv6 connectivity is non-existent (outside of link-local).

Sample logs:

Apr 3 19:20:09    radvd    53166    ioctl(SIOCGIFMEDIA) failed on bridge0: Invalid argument
Apr 3 19:19:58    radvd    53166    ioctl(SIOCGIFMEDIA) failed on bridge0: Invalid argument
Apr 3 19:19:48    radvd    53166    ioctl(SIOCGIFMEDIA) failed on bridge0: Invalid argument
Apr 3 19:19:38    radvd    53166    ioctl(SIOCGIFMEDIA) failed on bridge0: Invalid argument
Apr 3 19:19:28    radvd    53166    ioctl(SIOCGIFMEDIA) failed on bridge0: Invalid argument
[...]

My setup, for reference (works without issue in 2.4.2):

WAN -> em0
LAN -> bridge0 (opt1 opt2; Enabled IPv6 auto linklocal for SLAAC)
opt1 -> em1
opt2 -> ovpns1 (tap)

net.link.bridge.pfil_member=0
net.link.bridge.pfil_bridge=1

Since this is a fairly major regression, is there any chance of the original fix being reverted and a patch release issued, with an updated fix for #6974 appearing in 2.4.4?

Actions
Copy link

Also available in: Atom PDF