Is it Possible to Have Multiple ATA's in a LAN, with a single External IP?
Shale:
Quote from: Torvette on June 13, 2013, 07:02:28 am
So this was interesting.
For this deployment, the ATAs were set in 'router mode' (never again; there is no need for this!). There was a dedicated switch between the ATAs' external (WAN) NIC and the router. The LAN side had a distinct switch.
I looked up 'router mode'. The Admin Guide has this: Quote
IP Routing and LAN Switching Features (OBi202 Only)
OBi202 has two Ethernet ports labelled as the Internet port and the LAN port. The OBi works as a router by default. All the native voice services and features use the WAN port only when the OBi202 is in router mode. The OBi can also be set to work as a 3-port switch (a.k.a. Bridge mode), by changing its OperationMode parameter from Router to Bridge. Note: One of the switch ports is for OBi202 internal use only.
I think maybe you are saying that one OBi202's WAN port connected to the modem in router mode, and its LAN port was connected to an unmanaged switch. The other OBI2022's WAN port, and everything else, was connected to that switch, and that setup did not work right. So the "never again" applies to just having 2 OBis with that configuration?
Torvette:
It's a 'never again' because it was over-engineered.
The idea was to ensure QoS for voice traffic was pushed all the way to the perimeter of the network; I agree with this idea in principle, but anytime you are adding extra hops , extra equipment, extra layers and extra complexity to the environment, there has to be realized benefit. The only benefit here was a skipped trip to the barber, since I was able to pull my own hair out trying to resolve the issue.
In most cases of SOHO, setting the ATA in 'bridge mode' is absolutely acceptable. If this was an enterprise environment, with multiple internal WAN sites, and all sorts of data competing against the ATAs for bandwidth, I can see the need to further isolate and enhance the VoIP traffic into VLANs and QoS from start to finish.
Shale:
So what would your future plan be?
For example, with a single OBi202 and a dumb modem, put OBi202 into bridge mode,
Modem -> OBi202 > switch
That's not going to work because nobody is doing DHCP. Now if the modem has a built-in router, that should work.
Modem -> Router ->OBi202
That is what most of us do, with computer plugged into the router, but it does not have QOS unless the router does it. That may be what you refer to the not over-engineered setup. With nothing hooked to the OBi LAN port, then I don't think it matters whether OBi202 is in router or bridge mode.
Modem -> Router ->OBi202 -> computer
The other things, such as printer, would be plugged into the router.
Torvette:
Future Plan:
Modem -> Router/FW -> Switch -> (rest of the LAN, of which is the ATAs are but a node on the same subnet as the users, but with static IPs). In the case of Obi, you use the external NIC, not the internal NIC, for bridge mode.
There is no need for the Obi's to route/NAT/filter the users' day-to-day traffic. The router/FW was built for that feature set. The ATA's are just for VoIP (the fact that the Obi can do it is just a nice-.
to-have, not a requirement).
DHCP (for workstations, etc) is provided by the router/FW.
Navigation
[0] Message Index
[*] Previous page