public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: g6094199@freenet.de
To: development@lists.ipfire.org
Subject: RE: Re: Re: Possible configuration bug with >6 nics
Date: Mon, 02 May 2016 12:38:49 +0200	[thread overview]
Message-ID: <d5f2422daf55fa2934157e5e91051985@email.freenet.de> (raw)

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

Hi Michael!


Just tested the current nightly. Now all 8 NICs are shown, so

bug -> fixed


At least for 8 NIC devices :-)


THX!

sash


> -----Ursprüngliche Nachricht-----
> Von: Michael Tremer 
> Gesendet: Fr. 29.04.2016 14:24
> An: g6094199(a)freenet.de,  development(a)lists.ipfire.org
> Betreff: Re: Re: Possible configuration bug with >6 nics
>
>http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=3d7e6b4b6146c85dfd0b5804242e0847f3645525
>
> Could you please test the next nightly build that contains this change?
>
> On Fri, 2016-04-29 at 09:50 +0200, g6094199(a)freenet.de wrote:
>>         Hi Michael,
>>
>>
>>
>> as i said all nics are shown, even in ip link:
>>
>> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
>>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> 2: eth0:  mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group
>> default qlen 1000
>>     link/ether 00:90:7f:41:2d:25 brd ff:ff:ff:ff:ff:ff
>> 3: eth1:  mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group
>> default qlen 1000
>>     link/ether 00:90:7f:41:2d:24 brd ff:ff:ff:ff:ff:ff
>> 4: eth2:  mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group
>> default qlen 1000
>>     link/ether 00:90:7f:41:2d:23 brd ff:ff:ff:ff:ff:ff
>> 5: green0: 
>>  mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
>>     link/ether 00:90:7f:41:2d:22 brd ff:ff:ff:ff:ff:ff
>> 6: eth4: 
>>  mtu 1500 qdisc fq_codel master red0 state UP mode DEFAULT group default qlen
>> 1000
>>     link/ether 00:90:7f:41:2d:21 brd ff:ff:ff:ff:ff:ff
>> 7: eth5:  mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group
>> default qlen 1000
>>     link/ether 00:90:7f:41:2d:20 brd ff:ff:ff:ff:ff:ff
>> 8: eth6:  mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group
>> default qlen 1000
>>     link/ether 00:90:7f:41:2d:1f brd ff:ff:ff:ff:ff:ff
>> 9: eth3:  mtu 1500 qdisc fq_codel master red0 state DOWN mode DEFAULT group
>> default qlen 1000
>>     link/ether 00:90:7f:41:2d:1e brd ff:ff:ff:ff:ff:ff
>> 10: red0: 
>>  mtu 1500 qdisc fq_codel state UP mode DEFAULT group default 
>>     link/ether 00:90:7f:41:2d:1e brd ff:ff:ff:ff:ff:ff
>>
>>
>> There ist no scroll bar in the setup. Also if you try to scroll down nothing
>> happens.
>> setup.log is empty
>>
>> Since i'm running Core 100 (fresh embedded install), the limitation doesnt
>> seem to be fixed.
>>
>> I'm attaching an setup screenshot to your private mail.
>>
>>
>>
>> regards 
>> sash
>>
>>
>>
>>
>> >
>> > -----Ursprüngliche Nachricht-----
>> > Von: Michael Tremer 
>> > Gesendet: Do. 28.04.2016 19:25
>> > An: g6094199(a)freenet.de,  development(a)lists.ipfire.org
>> > Betreff: Re: Possible configuration bug with >6 nics
>> >
>> > 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>
>> > -----Ursprüngliche Nachricht Ende----
>>
>>  
>>
>> ---
>> Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! htt
>> ps://email.freenet.de/mail/Uebersicht?epid=e9900000451
>>
>>>
>
> -----Ursprüngliche Nachricht Ende-----


 

---
Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451



             reply	other threads:[~2016-05-02 10:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 10:38 g6094199 [this message]
2016-05-02 10:54 ` Michael Tremer

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=d5f2422daf55fa2934157e5e91051985@email.freenet.de \
    --to=g6094199@freenet.de \
    --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