Actions
Regression #11594
closedIPv6 routes with a prefix length of 128 result in an invalid route table entry
Start date:
03/02/2021
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.5.0
Affected Architecture:
Description
After adding fc00:1234::1234/128 via fc00:129::bbbb route, I see an invalid route in the routing table:
illegal prefixlen 7400:2a20::/0 fc00:129::bbbb UGS vtnet1
Updated by Viktor Gurov almost 4 years ago
Using `-net` argument with /128 netmask produces invalid routes, i.e.:
# /sbin/route add -net -inet6 fc00:aaaa::1/128 fc00:129::bbbb add net fc00:aaaa::1/128: gateway fc00:129::bbbb # netstat -rn | grep fc00:129::bbbb illegal prefixlen 7400:2a20::/0 fc00:129::bbbb UGS vtnet1
seems `route(8)` bug
fix/workaround:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/167
Updated by Jim Pingle almost 4 years ago
- Status changed from New to Pull Request Review
- Target version set to CE-Next
Updated by Jim Pingle almost 4 years ago
- Target version changed from CE-Next to 2.5.1
Updated by Renato Botelho almost 4 years ago
- Status changed from Pull Request Review to Waiting on Merge
- Assignee set to Viktor Gurov
PR has been merged. Thanks!
Updated by Renato Botelho almost 4 years ago
- Status changed from Waiting on Merge to Feedback
Updated by Jim Pingle over 3 years ago
- Subject changed from Unable to add static IPv6 routes to IPv6 routes with a prefix length of 128 result in an invalid route table entry
Updating subject for release notes.
Actions