How to use multiple network cards for green network

ritchie · 17 July 2020 20:37

Hi,

I am using a IPC with 5 Network card and would like to
use 4 NIC’s as Green network.

I have configured the “Network Card Assignment like This”

But only devices on the first green network card are available, devices on the following network card are not seen.

This is what ipconfig shows me:

[root@host ~]# ifconfig
blue0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr: Bcast: Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1936 errors:0 dropped:0 overruns:0 frame:0
TX packets:3701 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:296121 (289.1 Kb) TX bytes:1983494 (1.8 Mb)

eth1 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:X1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7780 errors:0 dropped:0 overruns:0 frame:0
TX packets:10031 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:987604 (964.4 Kb) TX bytes:9752877 (9.3 Mb)
Memory:df600000-df61ffff

eth2 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:X2
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Memory:df500000-df51ffff

eth3 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:X3
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Memory:df400000-df41ffff

eth4 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:X4
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Memory:df300000-df31ffff

green0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:X5
inet addr: Bcast: Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7748 errors:0 dropped:0 overruns:0 frame:0
TX packets:7713 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:877020 (856.4 Kb) TX bytes:9599889 (9.1 Mb)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:12167 errors:0 dropped:0 overruns:0 frame:0
TX packets:12167 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:854229 (834.2 Kb) TX bytes:854229 (834.2 Kb)

red0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:X6
inet addr: Bcast: Mask:255.255.255.0
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:13405 errors:0 dropped:3950 overruns:0 frame:0
TX packets:7128 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10055282 (9.5 Mb) TX bytes:900382 (879.2 Kb)
Memory:df700000-df71ffff

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr: P-t-P: Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[root@host ~]#

Where is my failure or how can I fix this ?

Best regards
R.

anon42188109 · 17 July 2020 21:31

this may help, there is a script from Arne … https://forum.ipfire.org/viewtopic.php?t=11860

in short, create /etc/init.d/bridge
brctl addif green0 eth2 eth3
ifconfig eth2 up
ifconfig eth3 up

anon33261557 · 17 July 2020 22:41

I think this WUI must be there for something good And after a quick search i found

So it should works somehow At the moment i have only a inspiration. It seems you have still set green, red, orange, blue. So my idea behind is, maybe there is some mismatch behind the settings. I would now try console setup and delete orange / setup green, red, blue

ritchie · 18 July 2020 11:19

Hi,

during the first startup I choose red+green+blue+orange, but I noticed, that
i would like to have my internal server still in the green network and changed
the setting back to red+green+blue.

This is the only screen, where I see “orange” .

I had configured in the past the bridge on my old system with the script shown in the answers, but I thought the function is now handled by the ipfire as a standard function.

This link is a dead one. Page is not existing.
https://wiki.ipfire.org/optimization/using_extra_ports_as_a_network_switch

How can I get closer to the problem ?

How is the system handling this ? will it create such a script like “bridge”, which I can check if this one ist existing and how it looks like ?

What is needed to get support ?

Best regards
R.

anon33261557 · 18 July 2020 11:29

My thought about the link i gave you is, that @ms said (in the whole thread not the dead link) its possible to do it with the WUI. Thats why i gave you the inspiration to do what i said.

ritchie · 18 July 2020 11:42

I guess this means, the screen is not working as expected and I should use the
workaround with the bridge script so long.
Best regards
R.

anon33261557 · 18 July 2020 12:47

Maybe, let me know when you find out.

ritchie · 18 July 2020 13:00

I am just working on the bridge script solution, because I do not know ipfire such good, that I will
found the reason why it is not working as expected and I need the access to my internal servers.
Best regards
R.

ritchie · 18 July 2020 13:17

Hi,

the solution with the bridge is not running, because the system says, that the nic is already member of a bridge.

see here the reaction of the system, trying to install the bridge script.

[root@host ~]# 
[root@host ~]# 
[root@host ~]# nano /etc/init.d/bridge
[root@host ~]# 
[root@host ~]# chmod 754 /etc/init.d/bridge
[root@host ~]# ln -s /etc/init.d/bridge /etc/rc.d/rc3.d/S19bridge
[root@host ~]# ln -s /etc/init.d/bridge /etc/rc.d/rc0.d/K82bridge
[root@host ~]# ln -s /etc/init.d/bridge /etc/rc.d/rc6.d/K82bridge
[root@host ~]# 
[root@host ~]# 
[root@host ~]# /etc/init.d/bridge  start
Create bridge for green net...
Bring down green0...
Rename green0 to green1...
Create new bridge green0...
Wait for 2 seconds...
Add real green nic (renamed to green1) to green0...
device green1 is a bridge device itself; can't enslave a bridge device to a bridge device.
Add eth2 eth3 eth4 to green0...
**device eth2 is already a member of a bridge; can't enslave it to bridge green0.**
Bring ALL nic's up...
Bring green1 up...
Bring eth2 up...
Bring eth3 up...
Bring eth4 up...
[root@host ~]# /etc/init.d/bridge  stop
Remove bridge for green net......
Bring down green1...
Bring down eth2...
Bring down eth3...
Bring down eth4...
Bring down green0...
Delete bridge green0...
Rename green1 to green0...
Bring green0 up...
Set ip on green0...
[root@host ~]#

Best regards
R.

anon33261557 · 18 July 2020 21:51

Meanwhile i tested it myself. Confirm now what @ms said. Its possible with the WUI.

Setup new machine with 4 Nics
Setup green/red
After boot Green Default --> Bridge
The 2 free Nics set in green also to Native
reboot

All 3 Nics works as green. So it looks now similar as yours without blue/orange.
I repeat now your setting is mismatch.

If you use from beginning only the WUI, it works.

ritchie · 19 July 2020 08:46

Hi,
because of the message, that there is already a bridge active a went thru the complete network cabling and found a damaged plug. After replacement, the bridge is working.
Sorry. Hardware problem which came up after installation of the new system.