Project

General

Profile

Actions

Bug #843

closed

Interface controls coupling unexpectedly

Added by Marcus Brown over 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
Start date:
08/24/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

I have an ALIX board running a single ADSL/PPPoE link for the WAN on vr2.

I also have DHCP set up on vr2 (via OPT4) to get an address from the ADSL modem.

When I click on "Release" on status interfaces, it brings down my PPPoE link too.

This piece of code in the interfaces.inc -> interface_bring_down() is the culprit I think. I looked at the code for pfSense_interface_flags and don't really understand what it does.

if(does_interface_exist("$realif")) {
mwexec("/sbin/ifconfig " . escapeshellarg($realif) . " delete", true);
pfSense_interface_flags($realif, -IFF_UP);
mwexec("/usr/sbin/arp -d -i {$realif} -a");
}

I'm not sure, but I think that the pfSense_interface_flags might be causing my system to freeze at boot time when the system is "Configuring OPT4 interface. . . "
It's the same situation, which is that the physical interface is already up because it was configured during the WAN/PPPoE start process and something else is going on.

Actions #1

Updated by Marcus Brown over 11 years ago

Can we get this classified for 2.0?

Actions #2

Updated by Chris Buechler over 11 years ago

  • Category set to Interfaces
  • Target version set to 2.0
  • Affected Version set to 2.0
Actions #3

Updated by Ermal Luçi over 11 years ago

  • Status changed from New to Feedback
Actions #4

Updated by Marcus Brown about 11 years ago

This issue is resolved and can be closed.

Actions #5

Updated by Chris Buechler about 11 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF