From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Possible configuration bug with >6 nics
Date: Thu, 28 Apr 2016 18:25:59 +0100 [thread overview]
Message-ID: <1461864359.10266.232.camel@ipfire.org> (raw)
In-Reply-To: <664ada1215548a8a7bf0cc5d5b983a71@email.freenet.de>
[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]
Hello,
there was a limit prior to Core Update 100 but this should have gone away and
actually 20 NICs should be shown by now.
Did you try to scroll down? Are there any errors shown?
What is the output of "ip link"?
Best,
-Michael
On Thu, 2016-04-28 at 16:52 +0200, g6094199(a)freenet.de wrote:
> He guys!
>
> i recently installed IPFire core 100 to an Watchguard Firebox X 750e/1000e.
> All installed to an CF-card, booted up fine.
> Came to the general setup and asked to map the nics to an interface. While the
> x750 has 8 nics (4x Marvell 88E8001, 4x 88E8053) only 6 nics are shown in the
> setup menue via serial port. which seems to be a limitation by the GUI or a
> bug.
>
> I can see als of the interfaces on cli after i finished the initial setup
>
> lspci:
> 01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E
> Gigabit Ethernet Controller (rev 19)
> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E
> Gigabit Ethernet Controller (rev 19)
> 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E
> Gigabit Ethernet Controller (rev 19)
> 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E
> Gigabit Ethernet Controller (rev 19)
> 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit
> Ethernet Controller (rev 13)
> 05:01.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit
> Ethernet Controller (rev 13)
> 05:02.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit
> Ethernet Controller (rev 13)
> 05:03.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit
> Ethernet Controller (rev 13)
>
> I also can use them. So it seems to be a limitation/bug of the setup menue?!
>
> Any thoughs?
>
>
> regards
> sash
>
>
> ---
> Mail & Cloud Made in Germany mit 3 GB Speicher! Jetzt kostenlos anmelden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
parent reply other threads:[~2016-04-28 17:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <664ada1215548a8a7bf0cc5d5b983a71@email.freenet.de>]
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=1461864359.10266.232.camel@ipfire.org \
--to=michael.tremer@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