Jump to content

Search the Community

Showing results for tags 'vlans'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Features Discussion
    • Getting started
    • Release Notes
    • General
    • Industry Chats
    • Feedback & Feature Requests
    • Agent
    • User Portal and Web App
    • Domotz Mobile App
    • Domotz Hardware
    • Public API for Developers
  • Third Party Hardware
    • Power Distribution Units (PDU) & Smart Power Plugs
    • Managed Network Switches
    • Device Configuration Management - Backup & Restore
    • Gateway/Controller Integrations
    • Wi-Fi Access Point and Controllers Integrations
    • Audio Video and Multimedia Integrations
    • Other Devices
    • Manufacturer Support
    • Domotz Agents on 3rd party platforms

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 2 results

  1. I will be doing an install over the next couple of days the network for me is a bit out of the ordinary and i need some idea as to how i should configure everything. The setup: 2 x Virgin media business superhubs connected to wan ports of Draytek Vigor 300b load balancer 24 port smart switch serves main network from lan1 port on the draytek - range 192.168.2.x (staff network) Small Desktop switch connected to lan 2 port on draytek - range 192.168.3.x (guest network) Both Virgin media superhubs are accessed via 192.168.100.1 (same ip) which until now hasn't been a problem because they are on the wan side of the router and accessed locally by direct connection. With the domotz box i assume i need to somehow create another vlan to connect the superhubs to? I'm thinking about fitting anther small switch to connect the lan side of the superhubs to and obviously giving them different ip addresses for the web gui. Am i on the right track any suggestions on how best to configure it all so that the domotz box will see all networks.
  2. Configuring Multi-VLAN support for Remote Network Monitoring with Domotz Pro Domotz Pro is a remote network monitoring software which supports multi-VLAN configurations for remote network and device monitoring. The software which is designed for integration companies and IT professionals enables a host of network monitoring features including: Remote Access, Remote Power Management, Network Mapping, SNMP, Alerts, Network Diagnostics and more. Read more about Domotz’s Remote Network Monitoring Features. Domotz supports monitoring of multi-VLAN network configuration through a variety of network installation options which include: Self Installation on a Raspberry Pi (i.e. your own Raspberry Pi device), Domotz Box, Windows, Linux, Synology etc. This post will explain how to configure mutli-VLAN support via your own self-installed Raspberry Pi device. Configuring Multi-VLAN support on a Self-Installed Raspberry Pi device for Remote Monitoring Starting from Package version 1.03-201(April 2016) of the Domotz Agent for Raspberry Pi, the full package can be installed on your own Raspberry Pi device and supports the discovery and monitoring of devices hosted on two or more VLANs accessible from the Raspberry Pi. (Instructions and latest package are available at Portal > Add an Agent tab. This short guide is meant for users who have multiple VLAN and are already aware of related configuration and procedures. For further details, and step by step guides, on how to configure VLANs on Switches and Raspberry Pi, the user should refer to detailed guides and or dedicated foruns like the https://www.raspberrypi.org/forums/ . In order to allow the Domotz to discover and monitor devices on two or more VLANs, the user should configure both the Switch and the Raspberry Pi to multiple VLANs: Switch Configuration The interface port of the switch which will be used to connect the Raspberry Pi, should be configured: - in Access mode / Untagged for the main interface used by the Raspberry to communicate with the gateway (e.g. eth0). - in Trunk 802.1q mode / Tagged for the additional VLANs to be monitored (e.g. the eth0.10 used for vlan 10) Please, refer to your specific switch/model guide on how to configure Trunk 802.1q and Access mode (Untagged/Tagged) for the port. Raspberry Pi Configuration (Raspberry Pi OS 10/ Debian Buster 10) In order to configure the Raspberry Pi to access both the main and VLAN interfaces, execute the following steps: 1. Install vlan package and configure modules: sudo apt-get install vlan sudo su echo 8021q >> /etc/modules exit 2. Create and edit the file /etc/network/interfaces.d/vlans E.g. if you want to add the VLAN ID 10 and VLAN ID 20 add the following content to the file auto eth0.10 iface eth0.10 inet manual vlan-raw-device eth0 auto eth0.20 iface eth0.20 inet manual vlan-raw-device eth0 * By convention, a VLAN virtual NIC should follow the naming convention: <physicalNIC>.<PVID> If you have multiple VLANs, you can just add them all to that same vlan file, following the same format. 3. Configure static IP addresses to the new virtual interfaces by editing the file /etc/dhcpcd.conf : # Example of static IP configuration: interface eth0 static ip_address=10.0.20.125/24 static routers=10.0.20.1 static domain_name_servers=1.1.1.1 #static domain_search= interface eth0.10 static ip_address=10.0.10.125/24 static routers=10.0.10.1 static domain_name_servers=1.1.1.1 interface eth0.20 static ip_address=10.0.20.125/24 static routers=10.0.20.1 static domain_name_servers=1.1.1.1 4 - Reboot the Agent, the interface eth0.10 and eth0.20 should be up automatically now.
×
×
  • Create New...