Bug #3513
closed
affects 2.1.1, interface 'primary' ip changes to alias-ip when saving interface.
100%
Description
Affects pfSense 2.1.1-PRERELEASE (amd64) built on Sat Mar 8 (but also that of 20140219-1945)
I could not reproduce this behavior on pfSense 2.1 RELEASE.
Problem:
logging in on the webinterface is not possible HTTP_REFERER check now complains when visiting the webgui using: 192.168.0.10 / anti lockout rule is also filtering on .20 , and in case the ip-alias was used for a different subnet it leaves you locked out of the webinterface.
Reproduction:
install pfSense on a machine with one or more interfaces
-give WAN a static ip of: 192.168.0.10
-add a ip-alias on the wan with IP: 192.168.0.20
-go back to the WAN edit page, and save and apply the settings.
Running 'ifconfig' shows that 192.168.0.20 is the 'first' ip of the interface.
Updated by Renato Botelho over 9 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 9aa6ad5c1669b044657b6c6808fae5174ff87460.
Updated by Renato Botelho over 9 years ago
Applied in changeset d130cd4674d25fb87ff673482ce215f97b979685.
Updated by Renato Botelho over 9 years ago
- Status changed from Feedback to Resolved
Updated by Pi Ba over 9 years ago
Hmm. it solved the IPv4 issue, but it seems to 'delete' the linklocal IPv6 address fe80::x:y:z now.
Updated by Renato Botelho over 9 years ago
Pi Ba wrote:
Hmm. it solved the IPv4 issue, but it seems to 'delete' the linklocal IPv6 address fe80::x:y:z now.
Fixed too, thanks!