From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6608] New: ebtables missing ethertypes - fix included
Date: Thu, 24 Oct 2013 13:19:50 +0000 (UTC) [thread overview]
Message-ID: <bug-6608-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6608
Summary: ebtables missing ethertypes - fix included
Product: buildroot
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: cassiano at idbinfo.com.br
CC: buildroot at uclibc.org
Estimated Hours: 0.0
ebtables installer macro does not copy ethertypes file.
As result, you cant use readable characters instead of hexadecimal numbers for
the protocols. For example, 0x0800 will be represented by IPV4.
Add to the install macro the following command to fix:
cp $(@D)/ethertypes $(TARGET_DIR)/etc/ethertypes
Thanks
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-10-24 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 13:19 bugzilla at busybox.net [this message]
2013-10-25 7:33 ` [Buildroot] [Bug 6608] ebtables missing ethertypes - fix included bugzilla at busybox.net
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-6608-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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