Creating a segregated network using a second interface

    Hello,


    I'm in the middle of setting up my server and am hoping to be able to run a second network for my IP cameras that have no connection to my normal network (and by extension, the internet).


    What is the best way to achieve this? Do I need an extra router (non-wifi) on the camera side or can I run the network with my server acting as the router?


    Thanks
    James

    Dell T320 Server E5-2430 24GB RAM, running OMV 4.1.22-1 with Docker
    Software Engineer

    Thanks, I did add the interface to OMV, but it doesn't bring the interface up. I figured it was because there is no "Gateway" for this network?


    Edit: This is what the error logs are saying:


    Code
    May 10 13:33:28 server avahi-daemon[44249]: Joining mDNS multicast group on interface eno2.IPv4 with address 10.47.2.1.
May 10 13:33:28 server avahi-daemon[44249]: New relevant interface eno2.IPv4 for mDNS.
May 10 13:33:28 server avahi-daemon[44249]: Registering new address record for 10.47.2.1 on eno2.IPv4.
May 10 13:33:28 server ifup[11117]: RTNETLINK answers: Invalid argument
May 10 13:33:28 server ifup[11117]: ifup: failed to bring up eno2

    And drilling down (using ifup with verbose logging) I found the issue is with the following command:
    sudo /bin/ip route add default via 10.47.2.1 dev eno2 onlink

    Dell T320 Server E5-2430 24GB RAM, running OMV 4.1.22-1 with Docker
    Software Engineer

    Einmal editiert, zuletzt von jwheeler ()

    Not 100% what I'm expecting here, but am I right in thinking that everything is routed back to 10.47.1.1?

    Code
    Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         10.47.1.1       0.0.0.0         UG        0 0          0 eno1
10.8.0.0        0.0.0.0         255.255.255.0   U         0 0          0 tun0
10.47.1.0       0.0.0.0         255.255.255.0   U         0 0          0 eno1
10.47.2.0       0.0.0.0         255.255.255.0   U         0 0          0 eno2
172.17.0.0      0.0.0.0         255.255.0.0     U         0 0          0 docker0
172.18.0.0      0.0.0.0         255.255.0.0     U         0 0          0 br-60bdef43a2d3

    Dell T320 Server E5-2430 24GB RAM, running OMV 4.1.22-1 with Docker
    Software Engineer

    Zitat von jwheeler

    am I right in thinking that everything is routed back to 10.47.1.1?

    This is at least the default gateway configured. Whether your OMV box will route depends on net.ipv4.ip_forward -- if this is set to 1 you most probably want to set it to 0 instead (see here for example for details and a persistent setting).

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden