June 30, 2014 at 15:52Beeline TV via Mikrotik in the province
Today, building IPVPN, VPLAN channels and much more is possible not only for companies using expensive equipment. Thanks to the functionality of modern low-cost routers, you can quickly and easily build or transfer existing network infrastructure. And the main thing is to do it cheaply, compactly and quickly both for small companies and for their own needs. Under the cut live example of the assembly and testing of the L2 channel between two providers in different cities for Beeline TV.
Interactive television with all the functions of recording, pause and rewind with a huge film library in a compartment with a prefix with a hard disk is all that can be difficult to break the habit of. And not all, let alone provincial towns, have Beeline TV. Let's try to build an L2 channel between two providers and test the Beeline TV service with all the subtleties.
To solve this problem, Beeline has an Internet channel. As well as a stable Internet channel from an provider in another city. A bandwidth of at least 4 Mbit for viewing SD channels and about 10 Mbit for channels in HD quality. Immediately I notice if you record channels in several pieces, then the bandwidth should be several times larger. But this is not a prerequisite. For a permanent circuit, a prerequisite is the presence of external static ip addresses on both channels. Cisco 800 series rest. Two of the cheapest Mikrotik routers will cope with the task. For example, RouterBOARD 951-2n. We will use the EoIP - Ethernet over IP functionality in Mikrotik. The absence of degradation of the service is determined by the absence of high jitter and losses between the two providers since at the transport level in the Beeline UDP home network. In the ip tunnel GRE.
A bit of theory. On the trunk, multicast traffic works through PIM - protocol-independent multicasting, and the Beeline home network uses IGMP - the multicast multicast protocol. As well as other competitors. Through VLC, of course, we will not see anything since the service itself has protection. Therefore, a method was chosen to transfer the ethernet infrastructure to CPE from another provider from which we will connect the prefix. The connection type of the terminal provider can be any, since IP is used as the transport.
Configuring Beeline L2TP session for Mikrotik is described, for example, here: routerz.ru/wp-content/uploads/2014/03/Instruction- on configuring-Mikrotik-RouterOS-for- working-in- network- Internet-provider-Korbina- Telecom- Beeline-07.07.2011.pdf
Let's consider directly EoIP. The cable from the Beeline access switch is inserted into the first port of Mikrotik ether1-gateway-Beeline.
We’ll lower the settings of the Internet channel of the second Mikrotik, as they can be any, depending on the type of connection. Everything is similar with EoIP.
Summing up the results of this short test, I note that service degradation has not been noticed! Unicast in the first 3-5 seconds when switching the channel flew instantly and after it, after signing the prefix to the group, the multicast was also successfully loaded. When watching HD channels, everything was also perfect. I want to note that EoIP was configured in different cities whose geography was determined by one area.
Interactive television with all the functions of recording, pause and rewind with a huge film library in a compartment with a prefix with a hard disk is all that can be difficult to break the habit of. And not all, let alone provincial towns, have Beeline TV. Let's try to build an L2 channel between two providers and test the Beeline TV service with all the subtleties.
To solve this problem, Beeline has an Internet channel. As well as a stable Internet channel from an provider in another city. A bandwidth of at least 4 Mbit for viewing SD channels and about 10 Mbit for channels in HD quality. Immediately I notice if you record channels in several pieces, then the bandwidth should be several times larger. But this is not a prerequisite. For a permanent circuit, a prerequisite is the presence of external static ip addresses on both channels. Cisco 800 series rest. Two of the cheapest Mikrotik routers will cope with the task. For example, RouterBOARD 951-2n. We will use the EoIP - Ethernet over IP functionality in Mikrotik. The absence of degradation of the service is determined by the absence of high jitter and losses between the two providers since at the transport level in the Beeline UDP home network. In the ip tunnel GRE.
A bit of theory. On the trunk, multicast traffic works through PIM - protocol-independent multicasting, and the Beeline home network uses IGMP - the multicast multicast protocol. As well as other competitors. Through VLC, of course, we will not see anything since the service itself has protection. Therefore, a method was chosen to transfer the ethernet infrastructure to CPE from another provider from which we will connect the prefix. The connection type of the terminal provider can be any, since IP is used as the transport.
The first Mikrotik is connected and tuned to Beeline
Configuring Beeline L2TP session for Mikrotik is described, for example, here: routerz.ru/wp-content/uploads/2014/03/Instruction- on configuring-Mikrotik-RouterOS-for- working-in- network- Internet-provider-Korbina- Telecom- Beeline-07.07.2011.pdf
Let's consider directly EoIP. The cable from the Beeline access switch is inserted into the first port of Mikrotik ether1-gateway-Beeline.
[Bee@MikroTik] > interface eoip add name=eoip-tunnel1 remote-address=x.x.x.x disabled=no tunnel-id=0
[Bee@MikroTik] > interface bridge add name=bridge_EoIP disabled=no protocol-mode=none
[Bee@MikroTik] > interface bridge port add bridge=bridge_EoIP interface=ether1-gateway-Beeline
[Bee@MikroTik] > interface bridge port add interface=eoip-tunnel1 bridge=bridge_EoIP
- Here, the tunnel itself is created in the first line, in which the static ip address of the remote router is written: xxxx Here, the tunnel id is set, which should be equal to the tunnel id on the other end.
- In the second line, create a new bridge interface on which we turn off RSTP otherwise the port on the access switch will be blocked for a loop at Beeline. I also want to note a new bridge is needed to isolate local_bridge in which, by default, DHCP distributes addresses to our LAN. And for the left DHCP, the beeline also blocks the port on the switch. Verified.
- In the third and fourth lines we add the ethernet interface into which the cable from the Beeline switch and the EoIP tunnel interface are inserted.
The second Mikrotik is connected and configured on another provider
We’ll lower the settings of the Internet channel of the second Mikrotik, as they can be any, depending on the type of connection. Everything is similar with EoIP.
- In the first line we create a tunnel in which we prescribe a static ip of the interface of the Beeline session: xxxx
- In the second line, create a new bridge. Disable RSTP.
- The third and fourth lines add to the bridge the interface of the EoIP tunnel and the ethernet interface into which our prefix is inserted:
[ISP@MikroTik] > interface eoip add name=eoip-tunnel1 remote-address=x.x.x.x disabled=no tunnel-id=0
[ISP@MikroTik] > interface bridge add name=bridge_EoIP disabled=no protocol-mode=none
[ISP@MikroTik] > interface bridge port add bridge=bridge_EoIP interface=ether1-gateway-ISP
[ISP@MikroTik] > interface bridge port add interface=eoip-tunnel1 bridge=bridge_EoIP
Summing up the results of this short test, I note that service degradation has not been noticed! Unicast in the first 3-5 seconds when switching the channel flew instantly and after it, after signing the prefix to the group, the multicast was also successfully loaded. When watching HD channels, everything was also perfect. I want to note that EoIP was configured in different cities whose geography was determined by one area.
Conclusion: in practice, it was possible to implement the work of one of the Internet services through EoIP on microtics.