Project

General

Profile

Actions
Copy link

Feature #9224

closed

Cannot configure STATICALLY-allocated IPv6 addresses on pfSense

Added by Răzvan Sandu about 6 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
12/26/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Hello,

On current version of pfSense, one cannot configure STATIC IPv6 addresses allocated by our ISP (RCS&RDS, Romania).

The ISP use the following scheme for offering static IPv6 to its clients:

a. a special /10 link-local address, provided by the ISP, must be configured statically on the client's device

b. for this address, the default gateway is also a link-local address (typically fe80::1 - apparently the ISP's CPE installed on the same physical wire, in client's home)

c. an IPv6 prefix of routable addresses (typically /128 or /64) is assigned to the client; at least one such address must be configured on the client's device, on the same interface

Current pfSense will not allow such a scheme, because:

- a link-local IPv6 address cannot be statically configured on an interface (pfSense signals an error)

- a link-local IPv6 address (such as fe80::1) cannot be designate as default-gateway (pfSense signals an error)

- it is presently difficult and counter-intuitive to configure multiple static IP addresses on the same interface, via the VirtualIP option

Please remove the three limitations above, in order to make pfSense usable for a large class of devices that need statically-configured IPv6 addresses, such as routers.

This suggestion was also opened as Request ID [#INC-17808] at NetGate Support.

Best regards,
Răzvan

Actions
Copy link

Also available in: Atom PDF