Project

General

Profile

Actions

Bug #12831

closed

Typo in in /etc/inc/interfaces.inc line 1107

Added by Jason Foley almost 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
LAGG Interfaces
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Force Exclusion
Affected Version:
2.7.0
Affected Architecture:

Description

This typo caused a crash on boot. (attached)

mwexec("/sbin/ifconfig " escapeshellarg($laggif) . " laggproto " . escapeshellarg($lagg['proto']) . " {$lacptimeout} {$lagghash}");

should be

mwexec("/sbin/ifconfig " . escapeshellarg($laggif) . " laggproto " . escapeshellarg($lagg['proto']) . " {$lacptimeout} {$lagghash}");


Files

crash.log (361 Bytes) crash.log Crash Jason Foley, 02/19/2022 03:24 AM

Related issues

Related to Feature #12819: GUI option to configure layers for LACP hashResolvedViktor Gurov

Actions
Actions #1

Updated by Lewis Smith almost 3 years ago

Just to confirm, this only appeared after creating a LAGG interface?

Actions #2

Updated by Jim Pingle almost 3 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #3

Updated by Jason Foley almost 3 years ago

Lewis Smith wrote in #note-1:

Just to confirm, this only appeared after creating a LAGG interface?

I see it's already fixed, but in case it's still useful information:

I already had a LAGG interface when I installed the update this morning.
I had to fix the typo in order to boot at all, so I didn't test it with my LAGG disabled.

Actions #4

Updated by Viktor Gurov almost 3 years ago

  • Status changed from Feedback to Resolved
  • Release Notes changed from Default to Force Exclusion

fixed

Actions #5

Updated by Jim Pingle almost 3 years ago

  • Related to Feature #12819: GUI option to configure layers for LACP hash added
Actions #6

Updated by Louis B almost 3 years ago

A few remarks:
- I think this issue could have been detected relatively easy quality check, so a nightly build with an issue like this one should never have been "released"
- lot of community members had to reinstall / fix there system and wrote about that in the forum
- so it would have been a good idea to reply in the forums and indicate that the issue is noted and fixed
- a new forum thread in development related to 2.7 would be a good idea

Actions

Also available in: Atom PDF