All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 13466] creation of bridge interface via interfaces does not work
Date: Mon, 16 Jan 2023 20:18:16 +0000	[thread overview]
Message-ID: <bug-13466-163-2S3HvgaYp2@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13466-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=13466

--- Comment #4 from Arınç ÜNAL <arinc.unal@arinc9.com> ---
I made it work. The brctl check on ifupdown.sh needed to be changed to
/usr/sbin/brctl.

I only needed to install bridge-utils. No need for the ifupdown package. Bridge
VLAN filtering won't work if iproute2 is not installed. BusyBox's ip command
does not support that.

My current rootfs overlay looks like this:

rootfsOverlay
├── etc
│   └── network
│       ├── if-down.d
│       │   └── bridge -> /lib/bridge-utils/ifupdown.sh
│       ├── if-post-down.d
│       │   └── bridge -> /lib/bridge-utils/ifupdown.sh
│       ├── if-pre-up.d
│       │   └── bridge -> /lib/bridge-utils/ifupdown.sh
│       └── interfaces
└── lib
    └── bridge-utils
        ├── bridge-utils.sh
        └── ifupdown.sh

I'm planning to work on the scripts a little to replace brctl with ip so it
would be usable without requiring any other packages to be installed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-01-16 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 14:15 [Buildroot] [Bug 13466] New: creation of bridge interface via interfaces does not work bugzilla at busybox.net
2021-02-17 16:26 ` [Buildroot] [Bug 13466] " bugzilla at busybox.net
2021-02-28 19:47 ` bugzilla at busybox.net
2021-04-16 16:32 ` bugzilla at busybox.net
2023-01-16 20:18 ` bugzilla [this message]
2024-06-15 14:56 ` bugzilla

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=bug-13466-163-2S3HvgaYp2@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.