Project

General

Profile

Actions

Bug #7412

closed

rtsold will not run on VLAN interfaces

Added by Jim Pingle over 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
DHCP (IPv6)
Target version:
Start date:
03/20/2017
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4
Affected Architecture:
SG-1000

Description

A VLAN interface for a WAN will not pull an IPv6 address via DHCPv6 with a default configuration.

In a default configuration, dhcp6c is launched via rtsold. When a VLAN-based interface is assigned, rtsold fails to run which means dhcp6c is never launched.

Running rtsold in debug mode produces the following log message:

Mar 20 12:41:41 pfsense rtsold[38666]: <make_packet> link-layer address option has null length on cpsw0_vlan10. Treat as not included.

The same message is not logged when the parent interface is used directly.

If I check "Do not wait for a RA" on the WAN settings which bypasses the need for rtsold, dhcp6c is launched directly and pulls an address.

Actions #1

Updated by mike cross over 7 years ago

Jim Pingle wrote:

A VLAN interface for a WAN will not pull an IPv6 address via DHCPv6 with a default configuration.

In a default configuration, dhcp6c is launched via rtsold. When a VLAN-based interface is assigned, rtsold fails to run which means dhcp6c is never launched.

Running rtsold in debug mode produces the following log message:
[...]

The same message is not logged when the parent interface is used directly.

If I check "Do not wait for a RA" on the WAN settings which bypasses the need for rtsold, dhcp6c is launched directly and pulls an address.

You marked #7436 as a duplicate of this - when you check Do not wait for an RA, does your configuration yield an operational default route? I just want to understand how my issue is a duplicate of this one. Thanks.

Actions #2

Updated by Jim Pingle over 7 years ago

No, there is no default gateway because rtsold won't run. DHCPv6 on its own does not handle gateways. It's the same root problem.

Actions #3

Updated by mike cross over 7 years ago

Ok, understood. Thanks for the explanation, I appreciate it. I'll lay low for a season and see how it goes.

Actions #4

Updated by mike cross about 7 years ago

Has progress been made on this bug? Thanks.

Actions #5

Updated by Luiz Souza about 7 years ago

  • Assignee set to Luiz Souza
Actions #6

Updated by Renato Botelho about 7 years ago

  • Target version changed from 2.4.0 to 2.4.1
Actions #7

Updated by Jim Pingle about 7 years ago

  • Target version changed from 2.4.1 to 2.4.2

Moving target to 2.4.2 as we need 2.4.1 sooner than anticipated.

Actions #8

Updated by Jim Pingle about 7 years ago

  • Target version changed from 2.4.2 to 2.4.3
Actions #9

Updated by Luiz Souza almost 7 years ago

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

Should be fixed in the next snapshot.

Actions #10

Updated by Jim Pingle almost 7 years ago

  • Status changed from Feedback to Resolved

Looks good now. SG-1000 with a VLAN WAN pulls an IPv6 address and default gateway now, without the "Do not wait for RA" box checked.

Actions

Also available in: Atom PDF