Topic: Howto configure (db) second internal NIC (eth1)

[djurhuus]

Does anybody know howto configure a second internal NIC (eth1) so it will be on the same network as eth0.
SME Server is running as "server only".
The problem is not to give eth1 an IP address on the same network but put this information in the database (/sbin/db configuration) so the configuration still will be there after a reboot.

Thanks in advance
Djurhuus

[gordonr]

Does anybody know howto configure a second internal NIC (eth1) so it will be on the same network as eth0.
SME Server is running as "server only".
The problem is not to give eth1 an IP address on the same network but put this information in the database (/sbin/db configuration) so the configuration still will be there after a reboot.

There is currently no option for additional internal NICs.

[djurhuus]

There is currently no option for additional internal NICs.

But how do I then configure a second NIC an still have this configuration after a reboot. There mut be a way.

[gordonr]

There is currently no option for additional internal NICs.

But how do I then configure a second NIC an still have this configuration after a reboot. There mut be a way.

If you configure the NIC according to the RedHat/CentOS docs, it should be persistent. However, since it isn't a supported option, we can't guarantee it won't get accidentally removed at some later stage by later development work. There are no current plans to add third-NIC support, but you should keep this in mind.

You will also need to configure the NIC as an additional "Local Network", but you will need to manually set the "Router" entry to the IP address of the NIC using the "config" command (since the web interface won't allow you to do this).

[CharlieBrady]

There is currently no option for additional internal NICs.

But how do I then configure a second NIC an still have this configuration after a reboot. There mut be a way.

If you configure the NIC according to the RedHat/CentOS docs, it should be persistent.

No, I don't think that is the case. I think we always generate ifcfg-eth1 from templates, even in serveronly mode. The generated file will include "ONBOOT=no", so will be ignored during network startup.

djurhuus hasn't said why he/she wants a second NIC on the same network as the first NIC. That's an unusual setup, and one likely to be troublesome (although bonding is one possible option).

[gordonr]

No, I don't think that is the case. I think we always generate ifcfg-eth1 from templates, even in serveronly mode. The generated file will include "ONBOOT=no", so will be ignored during network startup.

Good catch. However, eth2 or later should be o.k.