Project

General

Profile

Bug #1444

Reconfiguring interfaces doesn't deconfigure previous ones

Added by Malte Stretz over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
Start date:
04/17/2011
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

I just installed 2.0-RC1 via pfSense-memstick-2.0-RC1-i386-20110417-0359.img.gz with the quick install wizard (SMP kernel).

This machine has three network interfaces: msk0, rl0, rl1.

My first try looked like this:
WAN (wan) -> rl0 -> NONE (DHCP)
LAN (lan) -> msk0 -> 192.168.1.1
OPT1 (opt1) -> rl1 -> NONE

This didn't work, I got no DHCP lease and pinging from a manually assigned IP didn't work either (IPv6 neither). I assumed trouble with the driver for msk0 and thus switched to the following config:
WAN (wan) -> rl0 -> NONE (DHCP)
LAN (lan) -> rl1 -> 192.168.1.1

That didn't work either. But after some invatsigation I could see, that msk0 still had the IP address 192.168.1.1 assigned and the route was still set for interface msk0.

Associated revisions

Revision 7a18dfa4 (diff)
Added by Luiz Gustavo S. Costa about 8 years ago

Fixes #1444. Implements the same fix that issue ermal made in #1522 to the console menu

History

#1 Updated by Malte Stretz over 8 years ago

BTW, this sounds like bug 174, fixed a year ago.

#2 Updated by Ermal Lu├ži over 8 years ago

No its not like #174. This is in console and i am not sure that it has been forseen for such use.
I will give a look at how hard it is to correct this.

#3 Updated by Luiz Gustavo S. Costa about 8 years ago

  • Status changed from New to Feedback

#4 Updated by Luiz Gustavo S. Costa about 8 years ago

  • % Done changed from 0 to 100

#5 Updated by Chris Buechler about 8 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF