OMC Lan direct PC

  • Without a switch? You need a crossover cable and static IP addresses on both. I would buy a switch though. It won't cost that much more than the crossover cable.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


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

  • Hello.

    Having OMV installed on a workstation and using it normally through my Router on a 1Gbs LAN , is there possible to place a PCIe 10Gb NIC both on server / my PC and to connect them directly to be able to write/read at 10Gbs between server and my PC ? - reason for this would be to avoid buying an expensive 10Gb switch .


    (meanwhile the connection to internet should stay as it is on the 1Gbs cards/local network of Server & PC ).

  • A normal cable is straight through. This means a pin on one end goes to same on the other end of the cable. The wires go to different pins on the other end of a crossover cable.



    http://www.archonmagnus.com/mo…sOverCable/xOverCable.php

    My understanding is that this is outdated. Modern NICs can are smart enough to not need a crossover cable. I've done it between 2 PCs with a regular patch cable.

  • Hello.

    Having OMV installed on a workstation and using it normally through my Router on a 1Gbs LAN , is there possible to place a PCIe 10Gb NIC both on server / my PC and to connect them directly to be able to write/read at 10Gbs between server and my PC ? - reason for this would be to avoid buying an expensive 10Gb switch .


    (meanwhile the connection to internet should stay as it is on the 1Gbs cards/local network of Server & PC ).

    *push*

    Same issue here. Any solutions? The how-to's I found just explain how to bond NICs or how to have two unbonded NICs in the same network via switch etc.


    UPDATE

    Ok, seems to be simple, if you know where Windows is blocking the second network.

    1. assign a unique IP to your second OMV NIC via ip addr add xxx.xxx.xxx.2/NETMASK dev DEVICE. If the NIC is down, activate it via ip link set DEVICE up.
    2. assign a unique IP to your second Windows NIC, which is +1 to the OMV address, so xxx.xxx.xxx.3. Netmask must be the same as the NETMASK for OMV. It now is crucial to set the gateway of your second Windows NIC to the unique IP of you OMV NIC; otherwise Windows is blocking the second network.
    3. Connect your SAMBA/CIFS share using the IP-address of the second OMV NIC instead of the OMV machine name.

    Done.


Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!