two eth interfaces

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • two eth interfaces

      Hello All,

      I need to setup two eth interfaces, and configure two separate but interconnected LANs.
      One will be the usual office LAN, the other will be dedicated to Video Cam traffic, since OMV will be the storage.
      The first one will be a DHCP client, the second a DHCP server.
      I am looking for a way to do this from the webgui, but I haven't found anything.
      Should I go with command line, or do I risk to disrupt the install database?

      Thanks in advance for any helpful comments,

      -Gian
    • in the meanwhile, I found you can ADD a network interface indeed from the webgui, however, I got a message error while saving the new config...

      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start 'networking' 2>&1' with exit code '1': Job for networking.service failed because the control process exited with error code.See "systemctl status networking.service" and "journalctl -xe" for details.
      Error #0:OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start 'networking' 2>&1' with exit code '1': Job for networking.service failed because the control process exited with error code.See "systemctl status networking.service" and "journalctl -xe" for details. in /usr/share/php/openmediavault/system/process.inc:175Stack trace:#0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)#1 /usr/share/php/openmediavault/system/systemctl.inc(146): OMV\System\SystemCtl->exec('start', NULL, false)#2 /usr/share/openmediavault/engined/module/networking.inc(44): OMV\System\SystemCtl->start()#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleNetworking->startService()#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(536): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusws...', '/tmp/bgoutputXu...')#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))#9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)#10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)#13 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)#14 {main}
    • I was not able to setup the second eth with the webGUI, but now I have two NICs up and working, having configured them manually, adding the each stanza in /etc/network/interfaces.d/.

      However, the second eth does not show up in the webGUI, so I cannot setup a DHCP server on the NIC..

      I am worried that if I proceed with a manual setup, I'll end with a somewhat "crippled" install of OMV.
    • tkaiser wrote:

      are you able to clarify?
      OMV knows nothing of the interfaces.d directory. If there is config in the directory, it will still work but can't be edited in the web interface. If you configure the same adapter in the web interface, then the config will exist twice - /etc/network/interfaces and /etc/network/interfaces.d/whatever.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!