• Dear all,
    I have some issue setting up my Reelboxes with a Netceiver.
    In the living-room I have a Netceiver and Reelbox AVG 2. They are both connected through a smart switch.
    In my other room I have AVG 3, running BM2LTS connected to another smart switch.
    Please see the network diagram:


    [Blockierte Grafik: http://i.imgur.com/A9AkWHc.jpg]


    I have successfully connected the devices which are on the same switch using this settings:


    [Blockierte Grafik: http://i.imgur.com/DqukFDn.jpg]


    [Blockierte Grafik: http://i.imgur.com/dODCa7X.jpg]


    I have tried to connect the AVG 3 to the netceiver using the following settings but the AVG is blind for it.


    [Blockierte Grafik: http://i.imgur.com/UuYHbkV.jpg]


    [Blockierte Grafik: http://i.imgur.com/VV1YoLI.jpg]


    Please kindly help me with solving this issue. Where am I doing it wrong?
    Thank you in advance.

    Server: YaVDR Ansible VM (VDR 2.4.8) as a VNSI Server and Streamdev Server. DD CINE S2 + 2 x DD Duoflex S2 (6 tuners)

    VDR1 Client- ASUS AT3IONTI, 4gb RAM, 32GB SSD, MCE Remote, Custom case, YAVDR 0.6.2

    VDR2 Client- ASUS AT5IONTI, 4gb RAM, 128GB SSD, MCE Remote, D-Vine 5 HTPC Case, YAVDR Ansible, Ubuntu 20.04.2

    VDR3 Client- Modified Reelbox AVG II with working display: Gigabyte C1037UN-EU + EHD + 4GB ram + 32GB SSD. Streamdev client only.BM2LTS

    UNRAID - 110 TB storage, Supermicro X10SRL -F + Xeon E5-2680 v3 + 256 GB DDR4 ECC Ram.

  • Based on your network picture I assume, that you have configured the VLANs on both switches (.201 & .201), where the NetCeiver and where the AVG3 is connected. You have to configure the VLANs also on the ports of the Microtek-Router there the switches are connected. If the Router doesn't support VLANs, you should connect the both switches (.201 & .202) through another VLAN capable switch.

    Server:  (K)VM on Proxmox 4.x-Host, VDR 2.2.0 (selbstgebaut vom yaVDR unstable Repo) auf Debian 8 (Jessie), 1x Digital Devices Cine S2 (V6) + DuoFlex S2
    Clients: Raspberry Pi 2/3 mit Raspbian, VDR 2.2.0 (selbstgebaut vom yaVDR unstable Repo) als Streamdev-Clients

  • Dear atl,
    Thank you fro your input.
    Yes, indeed, both .201 and .202 are configured.
    The problem is that the switches are communicating to one another via series of other non-smart switches. The infrastructure is not the conventional one router->one switch->clients.
    If I will have to assign vlan on the router (yes, it is capable of assigning vlans) the task will get extremely complicated.


    Thank you once again for your help.

    Server: YaVDR Ansible VM (VDR 2.4.8) as a VNSI Server and Streamdev Server. DD CINE S2 + 2 x DD Duoflex S2 (6 tuners)

    VDR1 Client- ASUS AT3IONTI, 4gb RAM, 32GB SSD, MCE Remote, Custom case, YAVDR 0.6.2

    VDR2 Client- ASUS AT5IONTI, 4gb RAM, 128GB SSD, MCE Remote, D-Vine 5 HTPC Case, YAVDR Ansible, Ubuntu 20.04.2

    VDR3 Client- Modified Reelbox AVG II with working display: Gigabyte C1037UN-EU + EHD + 4GB ram + 32GB SSD. Streamdev client only.BM2LTS

    UNRAID - 110 TB storage, Supermicro X10SRL -F + Xeon E5-2680 v3 + 256 GB DDR4 ECC Ram.

  • If I will have to assign vlan on the router (yes, it is capable of assigning vlans) the task will get extremely complicated.


    Yes, you have to. On the Router the both ports, where the smart switches (.201 & .202) are connected and on the connected switch ports the VLAN 2 has to be configured.


    I know from my own home network, that setting up VLANs on such switches is not an easy part. :huh:

    Server:  (K)VM on Proxmox 4.x-Host, VDR 2.2.0 (selbstgebaut vom yaVDR unstable Repo) auf Debian 8 (Jessie), 1x Digital Devices Cine S2 (V6) + DuoFlex S2
    Clients: Raspberry Pi 2/3 mit Raspbian, VDR 2.2.0 (selbstgebaut vom yaVDR unstable Repo) als Streamdev-Clients

  • The problem is that the switches are communicating to one another via series of other non-smart switches

    you MUST have smart switches, otherwise it will not work. i have had the same problem years ago. then i have installed new smart switches an now i have a working network...you can test ist. please use a very long network-cable from 201 to 202 .....

    --------------------------------------------------------------------------------------------------------------------------------------------------

    BM2LTS im VDR-Portal   http://www.bm2lts.de   http://www.sc-schulze.de

    --------------------------------------------------------------------------------------------------------------------------------------------------

    Empfang: Octopus Net S2 max (8 Tuner) + Octopus Net S2 max (8 Tuner) + Netceiver (2x DVB-s2dual)

    Kopfstation: Virtuelle Maschine mit BM2LTS v3.4.XX

    Clients: NUC10i5FNH2 -> BM2LTS v3.4.XX; FireTV4k mit Kodi u. VNSI-Plugin

    NAS: Aufnahmen u. Plex-Media

    --------------------------------------------------------------------------------------------------------------------------------------------------


  • Thank you both for your answers.
    As the mikrotik router is not that easy for management it was setup in the past by a friend of mine who is a certificated Cisco admin, and I don't feel very confident to make any changes in it. It is really very different than any other router I have seen before.
    Instead of playing with the router it will be easier for me just to connect both rooms with one cable, thus only one management switch will be used. My existing cable, where the AVG 3 is connected, will be extended and will directly goes to one of the ports of .201.
    The cable will be very long, something like 60 meters. Hope the length will not be a bottleneck for the speed between the devices but it shouldn't have be.
    It is very snowy here and probably I will have to wait for a couple of weeks (for better weather) to accomplish the task.
    I will keep you informed once the cable is changed.
    Kind regards and thanks again.

    Server: YaVDR Ansible VM (VDR 2.4.8) as a VNSI Server and Streamdev Server. DD CINE S2 + 2 x DD Duoflex S2 (6 tuners)

    VDR1 Client- ASUS AT3IONTI, 4gb RAM, 32GB SSD, MCE Remote, Custom case, YAVDR 0.6.2

    VDR2 Client- ASUS AT5IONTI, 4gb RAM, 128GB SSD, MCE Remote, D-Vine 5 HTPC Case, YAVDR Ansible, Ubuntu 20.04.2

    VDR3 Client- Modified Reelbox AVG II with working display: Gigabyte C1037UN-EU + EHD + 4GB ram + 32GB SSD. Streamdev client only.BM2LTS

    UNRAID - 110 TB storage, Supermicro X10SRL -F + Xeon E5-2680 v3 + 256 GB DDR4 ECC Ram.

Jetzt mitmachen!

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