Website Review
What is E3Switch?
E3Switch is a hardware vendor that makes Ethernet-to-T3/E3/DS3 converters — devices that bridge standard Ethernet LANs and legacy TDM telecom circuits. According to its site, the products are plug-and-play, rack-mountable, and made in the USA, with a 30-day test drive offered.
Its converters are aimed at network engineers and carriers who still have DS3/E3 (roughly 45 Mbps / 34 Mbps) WAN links but want to move traffic over Ethernet. Rather than a single fixed product, the site organizes offerings by application:
- LAN extender — two units, one at each end, connecting two distant Ethernet networks over DS3/E3 transport.
- PPPoE LAN to ISP/Internet — one unit at the customer site talking to an ISP router at the central office; this is the single-ended internet-access case.
- Multi-TDM Gigabit LAN extender — bonds multiple DS3/E3 links between two Gigabit Ethernet networks with per-packet load balancing.
- WAN monitor — passively taps a DS3/E3 WAN and outputs traffic over Ethernet for recording or viewing, without a separate tap device.
- TDM over PSN — carries DS3/E3 across an intermediate Ethernet network, e.g. backhauling cellular traffic over Ethernet radios.
The key trade-off is application fit: the point-to-point modes need a unit at both ends, while the PPPoE mode is the one designed for connecting a single site to an ISP. If you're evaluating this for a specific link, start by identifying which of those five scenarios matches your topology — that determines the model family (for example, 1x-DS3-... or WANoE-...) before you compare anything else. You can review the application descriptions at E3Switch.
How do I choose between a point-to-point LAN extender and a PPPoE connection to an ISP?
The deciding factor is what sits at the far end of the DS3/E3 link: another Ethernet network you control, or an ISP/carrier router.
Point-to-point LAN extender — use when you own or control both ends. One E3Switch unit sits at each end of the DS3/E3 transport, and Ethernet goes in one side, DS3/E3 out the other, then back to Ethernet at the far end. Typical case: two distant offices, each with its own LAN, joined as if they were one network. It does not work as a single-ended connection to an ISP.
PPPoE to ISP — use when only your site has a unit and the other end is the carrier's central office or ISP router. Your Ethernet LAN goes in, DS3/E3 goes out to the provider, and PPPoE handles the session to the ISP. Typical case: one location getting internet access.
H3 When the choice is still close
- If you need internet access from one site, PPPoE is the intended path.
- If you need to bridge two of your own sites over DS3/E3, the LAN extender is the intended path.
- If you need more than one DS3/E3 for capacity, the multi-TDM Gigabit LAN extender bonds several TDM links with per-packet load balancing — but that is a two-ended design, not an ISP handoff.
- If you only need to watch traffic, the WAN monitor option is the passive alternative, with Ethernet output for recording or viewing.
A practical next step: sketch the two endpoints and label who controls the router at each. If the far end is a provider, choose PPPoE; if it is your own equipment, choose the LAN extender. E3Switch publishes model-number prefixes for each application on E3Switch, which is the quickest way to confirm you are ordering the right variant.
Can I bond multiple DS3 or E3 lines to get more bandwidth than a single T3?
Yes. Bonding multiple DS3/E3 (T3) lines into one logical Ethernet link is exactly what this class of equipment is built for. A single DS3 runs at roughly 45 Mbps; a bonded pair gives roughly 90 Mbps, and more lines scale accordingly, with per-packet load balancing across the TDM links.
Ethernet to Single/Dual/Multi T3/E3/DS3 Converters
H3 What bonding actually looks like
- One converter at each end of the DS3/E3 transport, with your Ethernet networks behind them.
- The intermediate WAN is the bonded DS3/E3 circuits; the converters present a single high-bandwidth Ethernet handoff.
- Typical use: linking two distant sites that each already have Ethernet LANs, where a single T3 no longer covers demand.
H3 Trade-offs to weigh
| Approach | Bandwidth | Best for |
|---|---|---|
| Single DS3/E3 | ~45 Mbps | Modest site-to-site or ISP handoff |
| Bonded multi-DS3/E3 | Multiples of ~45 Mbps | Site-to-site LAN extension, cellular backhaul |
| Ethernet over bonded TDM | Same as above, TDM carried inside Ethernet | Backhauling DS3/E3 over radios or Ethernet transport |
Caveats: bonding requires units at both ends, so it does not work as a single-ended connection to an ISP. Per-packet load balancing can reorder packets, which some latency-sensitive or single-flow applications handle less gracefully than aggregated throughput would suggest. If your goal is internet access rather than linking two of your own sites, the PPPoE-style single-ended configuration is the relevant one, not bonding.
Next step: count how many DS3/E3 circuits you can actually provision at both locations, since the achievable bandwidth is capped by the slowest end. If both ends can take the same number of lines, bonded multi-DS3/E3 is the straightforward answer; if only one end can, consider a different transport.
How do I passively monitor a DS3 or E3 WAN without a dedicated tap?
Use the WAN monitor application on an E3Switch unit: it accepts the DS3 or E3 WAN link and produces an Ethernet output that carries a copy of the WAN traffic for recording or viewing, so a separate WAN tap device is not needed.
The page lists this as its own application, separate from the LAN extender and PPPoE uses. The relevant model numbers are given as 1x-WANMON-... and 2x-WANMON-..., so the choice comes down to whether you are monitoring one WAN link or two. A passive monitor is the right fit when you need visibility into what is actually crossing the TDM circuit — for example, when an ISP or carrier disputes where errors or drops originate, or when you want a packet capture of WAN traffic without inserting an active device into the path.
For a concrete scenario: an engineer at a site with a DS3 handoff wants to capture traffic during an intermittent outage. Instead of asking the carrier to loop or tap the circuit, the WAN monitor sits on the link and feeds Ethernet to a capture host. The trade-off is that this is monitoring, not transport — if you need to move live customer traffic between two Ethernet networks, the LAN extender application is the relevant one, and if you need internet access from a single site, the PPPoE application is.
Next step: decide whether your goal is observation or carriage, then match the model prefix (1x vs 2x) to how many WAN links you need to watch. For the vendor's own application descriptions and model numbering, see E3Switch.
What equipment do I need at each end for TDM over PSN transport?
For TDM over PSN (DS3/E3 over Ethernet), you need one E3Switch unit at each end of the Ethernet transport. The DS3/E3 signal enters the unit at one site, is carried across the intermediate Ethernet network, and is reconstructed as DS3/E3 at the far end. The Ethernet link sits between the two units, not between a unit and a router or ISP.
E3Switch lists this as a point-to-point application under model numbers beginning WANoE-… on E3Switch. A typical use is backhauling cellular DS3/E3 traffic over Ethernet radios or other Ethernet transport.
What that means in practice
- Two units, one per site; the page does not describe a single-ended version of this application.
- Matching DS3 or E3 interfaces at both ends, depending on the circuit you are extending.
- An Ethernet path between the two units that can carry the aggregated TDM traffic.
- Rack space and power at both locations, since the units are described as rack-mountable.
Decide before ordering
Confirm the number of DS3/E3 links at each end and whether the intermediate Ethernet is point-to-point or passes through other equipment. If you instead need to reach an ISP from one customer site, that is the separate PPPoE application with a single unit. If you are connecting two distant Ethernet LANs, that is the LAN extender application, also with one unit per end.
How does per-packet load balancing work across bonded TDM links?
Per-packet load balancing distributes each Ethernet frame in turn across the bonded DS3/E3/T3 links, rather than assigning a whole traffic flow to one link. On E3Switch units this is described as fine-grained balancing over bonded TDM links in the Multi-TDM Gigabit LAN Extender application, where the units sit at both ends of the DS3/E3 transport.
In practice, the sending unit places packet 1 on link A, packet 2 on link B, packet 3 on link C, and so on. Because the links are treated as one logical pipe, a single large transfer can use the combined capacity of all bonded links instead of being capped at one link's rate. That is the main reason to choose it over per-flow balancing, which spreads flows but leaves any single flow limited to one link.
H3 Trade-offs to weigh
- Latency spread: packets in one flow can arrive out of order when links have different delays, so the receiving end must reorder them. This adds buffering and can hurt latency-sensitive traffic.
- Link quality: a slow or erroring link affects the whole bonded group more than it would under per-flow balancing.
- TDM framing: because the links are TDM circuits, the units must keep the aggregate in step across all bonded links, which is why a unit is needed at each end.
H3 A concrete decision scenario
Suppose a company needs to connect two offices that each have Gigabit Ethernet and has three DS3 circuits available between them. A per-packet bonded pair of units lets a single file transfer or backup job use all three circuits at once. If instead the traffic is many separate flows and low jitter matters more than single-flow speed, per-flow balancing is usually the safer choice.
Next step: confirm whether your application is point-to-point with a unit at each end (required for the bonded extender mode) or a single-ended ISP connection, since the PPPoE LAN-to-ISP mode is the one intended for a single unit talking to an ISP router.
User reviews (0)