https://community.hpe.com/t5/switches-hubs-and-modems/hp-1810g-two-networks/m-p/7049084#M34023 Generally separation (broadcast domain separation) requires the usage of defined VLANs (one for Data and one for Voice) and, again generally, Switch ports used to connect VoIP phoned are tagged members of Voice VLAN and untagged members of Data VLAN.<BR /><BR />When you seize your Switch in order to have, let me say, half of its ports untagged members of a particular VLAN ID and the other half untagged members of another VLAN ID then you need an external router (or equivalent internal Layer 3 IP routing features, if provided/supported by the Switch itself) to manage IP traffic routing between VLAN IDs...clearly if that is required by your network topology (there are cases where you need to keep traffic strictly separated up to a Firewall, as example). So it all boils down to what you have (in terms of features and network topology) and what are your requirements. Fri, 07 Jun 2019 01:45:14 GMT parnassus 2019-06-07T01:45:14Z https://community.hpe.com/t5/switches-hubs-and-modems/hp-1810g-two-networks/m-p/7048877#M34021 <P>Hi,</P><P>I have 2 networks (one for voip one for internet)</P><P>How can I separate switch so first half of ports will use DHCP router for voip and other half of ports will use second part od ports?</P><P>&nbsp;</P><P>&nbsp;</P> Wed, 05 Jun 2019 09:04:56 GMT https://community.hpe.com/t5/switches-hubs-and-modems/hp-1810g-two-networks/m-p/7048877#M34021 Charlie86 2019-06-05T09:04:56Z https://community.hpe.com/t5/switches-hubs-and-modems/hp-1810g-two-networks/m-p/7049084#M34023 Generally separation (broadcast domain separation) requires the usage of defined VLANs (one for Data and one for Voice) and, again generally, Switch ports used to connect VoIP phoned are tagged members of Voice VLAN and untagged members of Data VLAN.<BR /><BR />When you seize your Switch in order to have, let me say, half of its ports untagged members of a particular VLAN ID and the other half untagged members of another VLAN ID then you need an external router (or equivalent internal Layer 3 IP routing features, if provided/supported by the Switch itself) to manage IP traffic routing between VLAN IDs...clearly if that is required by your network topology (there are cases where you need to keep traffic strictly separated up to a Firewall, as example). So it all boils down to what you have (in terms of features and network topology) and what are your requirements. Fri, 07 Jun 2019 01:45:14 GMT https://community.hpe.com/t5/switches-hubs-and-modems/hp-1810g-two-networks/m-p/7049084#M34023 parnassus 2019-06-07T01:45:14Z