Project

General

Profile

Actions
Copy link

Bug #12632

closed

Changing an interface IP address and gateway at the console does not save the new gateway if one already exists for the interface

Added by M Felden over 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Jim Pingle
Category:
Console Menu
Target version:
2.7.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.01
Release Notes:
Default
Affected Version:
2.5.2
Affected Architecture:
amd64

Description

First encoutnered two months ago. Assumed I had done a typo or something and moved on. Now notice this can be reproduced every time on all installs I have tried:

ISP / Colo assign an IPv4 /30 203.0.113.156/30

Hardware has two NICs. bxe0 and bxe1. bxe0 is WAN bxe1 has no link.

- Install pfSense 2.5.2
- Assign bxe0 as WAN via console menu option 1
- Do not assign bxe1 as anything.
- Assign WAN IP manually via console menu option 2
- Specify: WAN IP 203.0.113.158, Netmask 30, Gateway 203.0.113.157

Expected behavior: Default route should be set with gateway as 203.0.113.157
Actual behavior: Gateway revers to 203.0.113.158, networking becomes impossible

Workaround:

- route del default
- route add default 203.0.113.157
- Enter web configurator
- Notice here during the WAN configuration step in web configurator it does indeed show gateway incorrectly as 203.0.113.158
- Fix gateway in web configurator
- Apply

Only ever seen this when WAN is a /30 - /22 /23/24 etc do not do this.

Files

clipboard-202112311307-sidpz.png (85.5 KB) clipboard-202112311307-sidpz.png Danilo Zrenjanin, 12/31/2021 06:07 AM
Actions
Copy link

Also available in: Atom PDF