public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Daniel Weismüller" <daniel.weismueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Core 152: the script "network-hotplug-bridges" now reads the variable ${ZONE}_STP from /var/ipfire/ethernet/settings so that STP can be turned on and off for each bridge
Date: Fri, 20 Nov 2020 07:58:32 +0100	[thread overview]
Message-ID: <ba5fae11-c02a-ca77-5113-abc4ae5e10db@ipfire.org> (raw)
In-Reply-To: <6126BB16-DC05-45C1-8141-8C0EEF74EEA9@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]

Hello,

In my opinion it is sufficient to be able to set these parameters via 
command line.

It should only be made sure that the settings are persitend and not 
overwritten by a reboot or the webif.

-
Daniel

Am 19.11.2020 um 15:56 schrieb Michael Tremer:
> Hello Daniel,
>
> This patch looks good to me.
>
> I had assumed that we automatically enabled STP on all bridges, but apparently we do not.
>
> How do we process with this?
>
> I suppose it is not the most user-friendly way to ask the user to edit the configuration file. This either must be documented somewhere or the zoneconfig.cgi script needs to be extended to allow enabling STP.
>
> Does anyone want to be able to change any STP parameters like priority or cost of the ports?
>
> Best,
> -Michael
>
>> On 19 Nov 2020, at 13:18, Daniel Weismüller <daniel.weismueller(a)ipfire.org> wrote:
>>
>> Signed-off-by: Daniel Weismüller <daniel.weismueller(a)ipfire.org>
>> ---
>> config/udev/network-hotplug-bridges | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/config/udev/network-hotplug-bridges b/config/udev/network-hotplug-bridges
>> index 33d6d65ba..7431377bb 100644
>> --- a/config/udev/network-hotplug-bridges
>> +++ b/config/udev/network-hotplug-bridges
>> @@ -81,6 +81,7 @@ MODE="$(get_value "${ZONE}_MODE")"
>>
>> # The name of the virtual bridge
>> BRIDGE="$(get_value "${ZONE}_DEV")"
>> +STP="$(get_value "${ZONE}_STP")"
>>
>> case "${MODE}" in
>> 	bridge)
>> @@ -89,7 +90,8 @@ case "${MODE}" in
>>
>> 		# We need to create the bridge if it doesn't exist, yet
>> 		if [ ! -d "/sys/class/net/${BRIDGE}" ]; then
>> -			ip link add "${BRIDGE}" address "${ADDRESS}" type bridge
>> +			ip link add "${BRIDGE}" address "${ADDRESS}" type bridge \
>> +				$([ "${STP}" = "on" ] && echo "stp_state 1")
>> 			#ip link set "${BRIDGE}" up
>> 		fi
>>
>> -- 
>> 2.28.0
>>

  reply	other threads:[~2020-11-20  6:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 13:18 Daniel Weismüller
2020-11-19 14:56 ` Michael Tremer
2020-11-20  6:58   ` Daniel Weismüller [this message]
2020-11-20  7:40     ` Daniel Weismüller
2020-11-20 10:55     ` Michael Tremer
2020-11-20 11:36       ` Daniel Weismüller
2020-11-20 13:44         ` Michael Tremer
2020-11-20 15:18       ` Kienker, Fred
2020-11-20 18:31         ` Daniel Weismüller
2020-11-21 16:39           ` Leo Hofmann
     [not found] <52028c49-1f25-9979-1aea-12d0c9ef21d4@ipfire.org>
2020-11-23 15:16 ` Michael Tremer
     [not found] <4bd57771-dfe2-032f-5230-09f96e5ad81d@leo-andres.de>
2020-11-25 20:57 ` Michael Tremer
2020-11-26 14:47   ` Daniel Weismüller
2020-11-27  8:34     ` Jonatan Schlag
2020-11-27 10:59       ` Michael Tremer
2020-11-27 17:48         ` Adolf Belka
     [not found] <e670b603-48bc-6f7c-a933-d6156443b186@leo-andres.de>
2020-11-28 13:24 ` Adolf Belka
2020-12-01 16:27   ` Michael Tremer
2020-12-03 18:00     ` Jonatan Schlag
2020-12-03 22:13 ` Kienker, Fred
     [not found] <e07c7859-0715-8920-a93a-e0e801c6a647@ipfire.org>
2020-12-10 13:34 ` Michael Tremer
2020-12-10 17:59   ` Leo Hofmann
2020-12-11  8:51     ` Michael Tremer
2020-12-11 15:33       ` hofmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ba5fae11-c02a-ca77-5113-abc4ae5e10db@ipfire.org \
    --to=daniel.weismueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox