Project

General

Profile

Actions
Copy link

Bug #6974

closed

radvd enabled on a disconnected interface kills RA completely on all interfaces

Added by Kill Bill almost 8 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Luiz Souza
Category:
IPv6 Router Advertisements (radvd/rtsold)
Target version:
2.4.3
Start date:
11/30/2016
Due date:
% Done:

100%

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

Description

After much head scratching about why devices are not getting v6 IPs any more, nothing short of disabling it on the disconnected interface would get things working again... Kinda retarded behaviour.

Nov 30 09:46:05    radvd    22782    sendmsg: No buffer space available
Nov 30 09:45:54    radvd    22782    sendmsg: No buffer space available
Nov 30 09:45:41    radvd    22782    sendmsg: No buffer space available
Nov 30 09:45:21    radvd    22782    sendmsg: No buffer space available
Nov 30 09:45:06    radvd    22782    sendmsg: No buffer space available
Nov 30 09:44:53    radvd    22782    sendmsg: No buffer space available
Nov 30 09:44:39    radvd    22782    sendmsg: No buffer space available
Nov 30 09:44:30    radvd    22782    sendmsg: No buffer space available
Nov 30 09:44:23    radvd    22782    sendmsg: No buffer space available
Nov 30 09:44:16    radvd    22782    sendmsg: No buffer space available
Nov 30 09:43:57    radvd    22782    sendmsg: No buffer space available
Nov 30 09:43:38    radvd    22782    sendmsg: No buffer space available
Nov 30 09:43:28    radvd    22782    sendmsg: No buffer space available
Nov 30 09:43:11    radvd    22782    sendmsg: No buffer space available
Nov 30 09:43:02    radvd    22782    sendmsg: No buffer space available
Nov 30 09:42:48    radvd    22782    sendmsg: No buffer space available
Nov 30 09:42:36    radvd    22782    sendmsg: No buffer space available
Nov 30 09:42:29    radvd    22782    sendmsg: No buffer space available
Nov 30 09:42:16    radvd    22782    sendmsg: No buffer space available
Nov 30 09:42:00    radvd    22782    sendmsg: No buffer space available
Nov 30 09:41:47    radvd    22782    sendmsg: No buffer space available
Nov 30 09:41:39    radvd    22782    sendmsg: No buffer space available
Nov 30 09:41:33    radvd    22782    sendmsg: No buffer space available
Nov 30 09:41:27    radvd    22782    sendmsg: No buffer space available
Nov 30 09:41:16    radvd    22782    sendmsg: No buffer space available
Nov 30 09:41:02    radvd    22782    sendmsg: No buffer space available
Nov 30 09:40:49    radvd    22782    sendmsg: No buffer space available
Nov 30 09:40:39    radvd    22782    sendmsg: No buffer space available
Nov 30 09:40:31    radvd    22782    sendmsg: No buffer space available
Nov 30 09:40:19    radvd    22782    sendmsg: No buffer space available
Nov 30 09:40:11    radvd    22782    sendmsg: No buffer space available
Actions
Copy link
 #1

Updated by Jim Thompson almost 8 years ago

  • Assignee set to Kill Bill

There is code in radvd to stop sending on interfaces that are no longer transmitting.

I don't know how difficult it might be to wire up.

Actions
Copy link
 #2

Updated by Kill Bill almost 8 years ago

Not really sure why's this assigned to me. Either it's a bug in radvd or in pfSense. Either way, I won't fix it. Also, I could not find any such code there in the first place. The only thing I could find is an option to ignore missing interface, which is

- unusable here since the interface is NOT missing
- buggy in addition and breaks things (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650047)

The fact that FreeBSD is many years behind upstream with the shipped version certainly doesn't help either. Looking at Freshports, someone finally added a port for 2.x, so maybe that'd be a good start. pfSense is even worse, the code here is from 2012/06/19 release.

Actions
Copy link
 #3

Updated by Renato Botelho almost 8 years ago

  • Assignee deleted (Kill Bill)
Actions
Copy link
 #4

Updated by Renato Botelho about 7 years ago

  • Target version changed from 2.4.0 to 2.4.1
Actions
Copy link
 #5

Updated by Jim Pingle about 7 years ago

  • Target version changed from 2.4.1 to 2.4.2
Actions
Copy link
 #6

Updated by Jim Pingle about 7 years ago

  • Target version changed from 2.4.2 to 2.4.3
Actions
Copy link
 #7

Updated by Luiz Souza almost 7 years ago

  • Assignee set to Luiz Souza
Actions
Copy link
 #8

Updated by Luiz Souza almost 7 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Fixed in radvd-2.17_4.

Disconnected interfaces will be properly ignored.

Actions
Copy link
 #9

Updated by Luiz Souza over 6 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #10

Updated by Spencer Hakim over 6 years ago

Hi, the fix to this bug breaks radvd for bridge interfaces, which subsequently breaks IPv6 routing within/out of the LAN.

On 2.4.3, my LAN clients correctly receive global IPv6 addresses, but never receive routes; only link-local routing works. IPv6 connectivity from the router itself is unaffected. Any chance this gets quickly rolled back? I'm hardly the only person to use a bridge to join multiple LAN interfaces together as one.

Actions
Copy link
 #11

Updated by Nicolas Vollmar over 6 years ago

Spencer Hakim wrote:

Hi, the fix to this bug breaks radvd for bridge interfaces, which subsequently breaks IPv6 routing within/out of the LAN.

On 2.4.3, my LAN clients correctly receive global IPv6 addresses, but never receive routes; only link-local routing works. IPv6 connectivity from the router itself is unaffected. Any chance this gets quickly rolled back? I'm hardly the only person to use a bridge to join multiple LAN interfaces together as one.

Agree, this is very annoying!

Actions
Copy link
 #12

Updated by Luiz Souza over 6 years ago

and... should be fixed by radvd-2.17_5. Check #8429 for the current bug.

Actions
Copy link

Also available in: Atom PDF