Bug #3657
closed
Web Interface - Missing Static IPv6 /127 Subnet Prefix
Added by Cyril Tourist over 10 years ago.
Updated over 9 years ago.
Affected Version:
2.1-IPv6
Description
Bug: When using the web interface (GUI) to configure a network interface with a static IPv6 the subnet prefix /127 is not available.
Workaround: Use the console (CLI) to configure the network interface.
Tested Affected Versions: 2.1.2 & 2.1.3
Files
/usr/local/www/interfaces.php has code to specifically exclude 127:
for ($i = 128; $i > 0; $i--) {
if($i <> 127) {
echo "<option value=\"{$i}\" ";
if ($i == $pconfig['subnetv6']) echo "selected=\"selected\"";
echo ">" . $i . "</option>";
}
}
I wonder why that is?
- Affected Version changed from 2.1.2 to 2.1-IPv6
Because FreeBSD 8.x doesn't support it, the same as it doesn't support /31s. 10.x might support it, as it does support /31s, will need to be checked before changing the missing /127.
We have successfully been using a IPv6 /127 subnet to connect our pfSense router with our ISP's router (COLT).
The use of a /127 was defined by COLT to connect our router with them.
The very very simplified setup looks something like this:
<ISP 'COLT' Router> [2001:920:X:X::24/127] <------> [2001:XXX:X:X::25/127] <pfSense Router> [2001:920:XXXX::1/48] <------> 2001:920:XXXX::/48 <Assigned /48 Subnet>
This setup has been working as expected (other then the GUI bug) with pfSense version 2.1 (FreeBSD 8.3-RELEASE-p11).
. . It would therefore seem that FreeBSD 8.3 supports /127 subnets?
- Status changed from New to Resolved
- Target version set to 2.2
this has been fixed in 2.2
Also available in: Atom
PDF