Here is an approach that might be worth a NFR for it touches 1 line in e-smith-base...
Use at your own risk!
edit /usr/share/perl5/vendor_perl/esmith/console/configure.pm
find the line: if (scalar @adapters == 1)
and change it to:
if (scalar @adapters == 1 || $db->get_value('ForceDummyNic') eq 'enabled')
Now you can toggle the yes/no listing of the Dummy NIC by setting the db key:
config set ForceDummyNic enabled and config delete ForceDummyNic
After setting the db key, you can run console and the dummy NIC will be listed and available to pick as the internal (LAN) adapter only.
HTH
grazie! provo stasera... ti tengo aggiornato.
I don't understand. Why would you want to use a dummy NIC if you have a real one ? Just choose one of the unused NIC, without pluging anything on it, and you'll have the same effect
...
Use at your own risk!
edit /usr/share/perl5/vendor_perl/esmith/console/configure.pm
...
... Can you detail the reason not to use one of the real NIC, even if unplugged, as this would have the same effect than using the dummy NIC ...
... (support for the dummy NIC was added only for those case where you have a single NIC, and you can't run in server only mode because this single NIC is the public one)
RequestedDeletion 2013-01-07 06:07:01 CET
These patches will add the ability to run SME Server in servergateway mode with only 1 hardware ethernet adapter. It is based on RH/Centos dummy adapter.
the reason is the free will :-|
Server (server & gateway) has 2 NIC's. 1 NIC is going to be used as WAN adapter and the other NIC for other purposes such as extra connection to the server (Rsync, monitoring, backup etc etc). The dummy should be used as the LAN adapter.I don't see this as a valid use case. Why wouldn't the "other purpose" (backup, monitoring etc...) wouldn't use the LAN NIC, as in such a situations, obviously, nothing else would be using this link.
I don't see this as a valid use case. Why wouldn't the "other purpose" (backup, monitoring etc...) wouldn't use the LAN NIC, as in such a situations, obviously, nothing else would be using this link.
... If the 2 NIC you don't want to use are using a different driver than the one you want to use (you should be able to identify this in the NIC selection screen of the console, or using lscpi -vv), then you should be able to blacklist this single module (in /etc/modprobe.d/) ...
alias eth1 off
alias eth2 off
Thanks, unfortunately, not the case.
However, I imagine that any had ever installed nvidia graphics driver on a CentOS system has learned the trick
caro Stefano, you missed a good time to be silent ... :-(
I suggest you ask here on the forum if there is any connection between SME and RHEL/CentOS!
You might be surprised at the response you'll get.
@ Stefano
caro Stefano, you missed a good time to be silent ... :-(
I suggest you ask here on the forum if there is any connection between SME and RHEL/CentOS!
You might be surprised at the response you'll get.
... Stefano knows probably better than you that SME is based on CentOS
... (support for the dummy NIC was added only for those case where you have a single NIC, and you can't run in server only mode because this single NIC is the public one)
I don't see this as a valid use case. Why wouldn't the "other purpose" (backup, monitoring etc...) wouldn't use the LAN NIC, as in such a situations, obviously, nothing else would be using this link.
... was made being as well informed
Indeed, I'm well informed. Thanks for noticing