Posted: 1/1/2014 4:20:23 PM EDT
|
Okay I've got one hard wired LAN with one DSL router and a variety of switches, computer's, TVs connected, etc.
I want to connect two AT&T voip gateways and two AT&T voip desksets into the LAN. However, #1 voip gateway and #1 deskset cannot be allowed to see #2 voip gateway and #2 deskset. PC in question has two LAN ports. One LAN port on the PC needs to be on the main LAN and see #1 voip setup. Second LAN port should only be able to see the #2voip setup. How do I do this? Change the router subnet mask to 255.255.255.128 to have two subnets and assign the main LAN port and #1 voip with a less than.127 IP and the second LAN port and #2 voip setup on .129+ IP? Will this keep them separate so they cannot communicate? Sorry I'm an IT rookie. |
|
You are on the right track, You will need two networks here.
Network 1: 192.168.1.0/25 VoIP Gateway 1: 192.168.1.2 255.255.255.128 PC NIC 1: 192.168.1.3 255.255.255.128 Network 2: 192.168.1.128/25 VoIP Gateway 2: 192.168.1.130 255.255.255.128 PC NIC 2: 192.168.1.131 255.255.255.128 Your router will need to have an interface listening on each network if you need these devices to get out to the internet. |
|
Your solution only fixes the issue on layer 3, however the devices (nics, voip, etc ) can still communicate at layer 2. The most annoying piece is your computer will constantly be complaining it has to change its name because it found a dup.
The should build vlans in your switch or get different switches. |
|
Quoted:
Your solution only fixes the issue on layer 3, however the devices (nics, voip, etc ) can still communicate at layer 2. The most annoying piece is your computer will constantly be complaining it has to change its name because it found a dup. The should build vlans in your switch or get different switches. Yea, ideally you would want to vlan these devices off into seperate vlans to isolate traffic, but not necessarily for l2 communication. A device will not ARP for another device in a different network, instead it will ARP for its default gateway and shove the traffic over to that to be routed to the different network. If one of the devices were configured for a /24 then you'll run into a layer 2 issue as the device would believe the other device is in the same network. But, with the devices in separate /25 networks they won't be doing l2 communication. |
|
Quoted:
Yea, ideally you would want to vlan these devices off into seperate vlans to isolate traffic, but not necessarily for l2 communication. A device will not ARP for another device in a different network, instead it will ARP for its default gateway and shove the traffic over to that to be routed to the different network. If one of the devices were configured for a /24 then you'll run into a layer 2 issue as the device would believe the other device is in the same network. But, with the devices in separate /25 networks they won't be doing l2 communication. Quoted:
Quoted:
Your solution only fixes the issue on layer 3, however the devices (nics, voip, etc ) can still communicate at layer 2. The most annoying piece is your computer will constantly be complaining it has to change its name because it found a dup. The should build vlans in your switch or get different switches. Yea, ideally you would want to vlan these devices off into seperate vlans to isolate traffic, but not necessarily for l2 communication. A device will not ARP for another device in a different network, instead it will ARP for its default gateway and shove the traffic over to that to be routed to the different network. If one of the devices were configured for a /24 then you'll run into a layer 2 issue as the device would believe the other device is in the same network. But, with the devices in separate /25 networks they won't be doing l2 communication. You are correct about ARP. My statement is more around non-ip protocols and multicast. |
|
Quoted:
Is that a router or voip gateway setting? My router has a "static route rules" section...is that applicable to this situation? Quoted:
Quoted:
IP forwarding enabled on your system? Is that a router or voip gateway setting? My router has a "static route rules" section...is that applicable to this situation? It is possible that your router is routing between the two inside subnets. However, it is unusual for devices to auto-discover beyond their own subnet. It appears that layer 2 communications may be involved, which would be solved either by using a managed switch with VLANs, or simply using two separate switches. It may be worth investigating whether you can tell your router NOT to route between the two internal subnets. If not, another switch is not expensive. |
|
Quoted:
Is that a router or voip gateway setting? My router has a "static route rules" section...is that applicable to this situation? Quoted:
Quoted:
IP forwarding enabled on your system? Is that a router or voip gateway setting? My router has a "static route rules" section...is that applicable to this situation? "System" as in the computer with two network cards installed, configured, and working; one on each subnet you have set up. If IP forwarding is enabled, your system is acting as a gateway between the two networks. |
|
Quoted:
"System" as in the computer with two network cards installed, configured, and working; one on each subnet you have set up. If IP forwarding is enabled, your system is acting as a gateway between the two networks. I can disconnect the LAN cables from the PC to remove it from the network entirely. The voip items all see each other. |