2018-10-29 - MUM Romania 2018

Asociatia Interlan attends MUM Romania, which takes place at Radisson Blu Hotel in Bucharest. The purpose of the meeting is to present strategies for deploying new and innovative MikroTik RouterOS and RouterBoard hardware applications.

 

2018-10-29 - Romania TV channel is available via multicast stream on the Interlan Tvx Platform

The Romania TV channel has become available via multicast streaming on the InterLAN TVX platform.

The complete list of TV channels available on InterLAN TVX Platform can be found here.

2018-10-24 - A New Succesful Edition Of Ronog Conference Ended!

The RONOG 5 conference took place on 23 October 2018 at the JW Marriott Bucharest Grand Hotel. RONOG conference brings together professionals sharing the same interests while sharing a diversity of ideas, experiences and opinions with the most important people supporting the telecom community.
The event brought together representatives of the internet access service providers, data transmissions, Voice and TV over IP, cable TV, hosting companies and Internet domains as well as national telecom regulators, public authority institutions, security equipment vendors and security solutions.
As a positive outcome from the high content and presentations performed at RONOG 5, various media press agencies published online articles: Media Expres, Comunicate Wall-Street.ro, Softlead, Market Watch, Agerpres, Mediafax, Agora.

2018-10-16 - CERT-RO Annual Conference

InterLAN attends the 8th edition of the annual conference ‘’The New Global Challenges in Cyber Security, organized by CERT-RO and ITU, that takes place between 15-17 of  october 2018 at National Library, Bucharest. The topics for this year range from policy developments at European and International level, capacity building tools and initiatives, to the implementation of the new technologies in the cyber security field, as well as insight in the global threat landscape.

 

 

2018-10-15 - RIPE 77

RIPE 77 Meeting takes place between 15 and 19 October in Amsterdam, Netherlands. InterLAN delegates attends RIPE 77 and participates during 5 days of  presentations, tutorials, workshops and open discussions.

 

 

 

2018-10-11 - Growth is in the air – Interlan Internet Exchange ecosystem upgraded at 100 Gbps in Frankfurt!

InterLAN Internet Exchange, the largest neutral IXP in Romania for data traffic and internet exchange consistently reached in the recent months an aggregate traffic peak of over 150 Gbps.
As a result of traffic growth in Frankfurt, the interconnection capacity was increased to 100 Gbps.
InterLAN brings together and serves more than 100 operators: internet access service providers, content providers, internet domain name service providers, educational networks, banking and financial companies, social media platforms, public institutions. InterLAN hosts 5 out of 13 DNS root name servers: D-Root (University of Maryland), E-Root (NASA AMES Research Center), F-Root (Internet Systems Consortium) Root (operated by Verisign), K-Root (operated by RIPE NCC) and L-Root (operated by ICANN).
Currently, InterLAN Internet Exchange platform has 135 connected ports with an aggregate capacity of nearly 800 Gbps.

2018-10-08 - Blizzard Entertainment becomes a traffic partner in InterLAN Internet Exchange

Blizzard Entertainment becomes a traffic partner in InterLAN Internet Exchange. Blizzard Entertainment is a premier developer and publisher of entertainment software. The company became one of the most popular and well-respected makers of computer games. By focusing on creating well-designed, highly enjoyable entertainment experiences, Blizzard Entertainment has maintained an unparalleled reputation for quality since its inception.

 

2018-10-02 - TVSAT Media Group becomes a traffic partner in InterLAN Internet Exchange

TVSAT Media Group becomes a traffic partner in InterLAN Internet Exchange.

 

2018-09-13 - A New Press Conference Regarding NETCITY Project organized by Asociatia Interlan

Asociatia Interlan together with ANISP, organized a press conference related with NETCITY Project in Bucharest.

The talks and debates were conducted by both president of the associations, Eric Andrei Baleanu (Asociatia Interlan) and Catalin Cuturelea (ANISP) along with other representatives of telecom industry: Dan Georgescu (Counselor of the Minister of Communications and President of AOTR – Association of Telecommunications Operators in Romania), Mihai Constantin (AOMR – Association of Mobile Operators in Romania), Marian Bumbar (General Counselor, Member of the Public Utilities Committee), Tiberiu Gîndu (ANISP, Executive Director) as well as other representatives of network operators.

 

During the conference, the representatives of the operators complained that the failure to comply with the legal conditions regarding the implementation of the ANCOM Opinion issued in 2013 for the metropolitan Netcity network and the carelessness of the national regulator of telecommunications (ANCOM), which faild to issue a decision in this respect two years ago, lead to the extinction of the small and medium-sized operators on the market and, implicitly, the disappearence of competition with direct negative effects on end-users.

Eric Andrei Băleanu stated that 10 years ago Romania was placed first in Europe and on third place in the world at Internet connection speeds, and in the present days we are currently out of the top 10. Nicolae Căpuşeanu (Dynamic Distribution) and Adrian Calineata (Pronet Soluții IT) pointed out the problems faced by small operators in relation to Netcity, and how this non-compliant project threatens their bankruptcy business.

More details you can find here:

• Media Expres: Asociațiile de internet contestă dezvoltarea Netcity în viziunea PMB
• Hotnews.ro: Furnizorii de internet acuză că dispar tot mai multe rețele de cartier în București din cauza tarifelor abuzive de acces la rețeua Netcity și a lipsei de intervenție a ANCOM
• Profit.ro: Asociația Internet Service Providerilor reclamă: Rețeaua Netcity distorsionează piața comunicațiilor din Capitală și falimentează operatorii de cartier
• Economica.net: Asociaţia furnizorilor de internet: Netcity distorsionează piața comunicațiilor din Capitală și falimentează operatorii de cartier
• Agerpres: Nereglementarea proiectului Netcity va duce la dispariția operatorilor medii de pe piață

2018-07-12 - Technical Regulations

I. Recommendations

1. Traffic Participants are encouraged to announce all their routes and accept all routes from InterLAN. For a better and easier connectivity it is recommended that participants perform BGP sessions with InterLAN route-servers. Participants in peering are advised to establish a page on their own website (e.g. website.com/peering), where the peering access procedure is detailed for whoever may be interested.

2. It is recommended that the devices used for interconnection be specialized equipment such as routers or Layer III class switches.

II. Obligations

1. The traffic that runs through the InterLAN infrastructure as a result of the exchange of information between participants should not be filtered or altered. The interception or the examination of this traffic will be made with the written approval of InterLAN technical department or at the written request of qualified authorities, according to the law in force.

2. Potential participants are entirely responsible in terms of connectivity with InterLAN POP where the interconnection will take place.

3. InterLAN alone will decide the route to transfer data packets from the partner in the InterLAN network.

4. Traffic participants will not act send illegal traffic or other traffic that hinders InterLAN peering use by other partners (e.g. ARP spoofing, sniffers installation, etc.).

5. Ethernet packets sent to the access ports in InterLAN by the partners will have only the following types:
a. 0x0800 – IPv4
b. 0x0806 – ARP
c. 0x86dd – Ipv6
d. 0x8100 – 802.1q

6. It is forbidden to activate Proxy ARP on the interfaces towards InterLAN.

7. All Ethernet frames representing Internet Exchange traffic sent to an access port in InterLAN will have necessarily the mac address/addresses associated with IPv4 and IPv6 allocated by InterLAN technical department.

8. An IP address used for the interconnection with InterLAN RSes and with the other partners will be assigned to each peering participant. The number of IP addresses assigned to a traffic participant can be altered according to interconnection needs, supported by submitted documents.

The assignment of additional IP addresses is done by the InterLAN technical department in following situations:

a. The need for back up BGP sessions
b. Private BGP sessions operation
c. Simultaneous active sessions of the same traffic partner (identified by ASN)

9. The traffic specific to local protocols should not be sent towards the access ports in InterLAN.

10. The following type of traffic and protocols are not allowed:

a. ICMP redirect
b. IEEE802 STP
c. IRDP – (Internet router discovery protocol)
d. BOOT/DHCP
e. DVMRP
f. UDLD
g. L2 keepalive
h. ICMPv6 ND-RA
i. Trunking protocols: VTP, DTP
j. Proprietary protocols, including but not limited to: CDP, EDP
k. Rounting protocols: OSPF, ISIS, IGRP, EIGRP, RIP
l. IGMP should not be enabled on IEX VLAN
m. xSTP should not be enabled on the port connected in InterLAN infrastructure

11. The outgoing broadcast traffic of a port should not exceed 20 pps / port / vlan.

12. MAC address numbers:
a. At client ports, only one MAC address is accepted for each IP address assigned as long as the client does not use other services than IX services. If the traffic is originated by more than one MAC address, the port will be disabled for 5 minutes.
b. More than one MAC address is accepted on the client ports depending on the services used (transit, multicast, multiple routers). The limit will be established with the customer, and if the rule is exceeded, the rule from the previous paragraph will apply. The limit may increase with the approval of InterLAN.

13. The routes exchange will be achieved only via BGP IPv4, IPv6 sessions.

14. The maximum length of a prefix announced by participants should not exceed 24-bit in the case of IPv4, and 96-bit in the case of IPv6.

15. All routes announced in InterLAN which originate from traffic participants public ASes must be registered in RIR’s database managing them (route-objects must exist).

16. Each peering participant must have a public ASN and at least one IP address class originated from his own ASN.

17. BGP sessions will announce only own IP address classes or customer’s classes and not those of other providers without their express consent along with InterLAN’s consent.

18. InterLAN’s peering reserved IP address space will be not announced in other networks except with the prior written approval of InterLAN technical department.

19. All routes announced in InterLAN will have set the nexthop to the partner making the announcement, unless the consent of technical department was obtained for the members announcing the routes with nexthop to other partners.

20. The announcement of private address classes (RFC1918) in InterLAN is not permitted.

21. A participant will send traffic to another participant’s port only in case when he has obtained permission from the latter via a route announced through InterLAN route-servers or a private BGP session.

22. The use of static routes is not allowed. All traffic routing decisions through the connection with InterLAN will be taken on the basis of by BGP session received routes.

23. Maintenance works must be notified to the InterLAN technical department at least 48 hours prior to the event, with a declared goal to take all necessary measures to prevent any compatibility and/or connectivity issues of the participants. In case of accidental equipment replacement as result of their failure, it is required to announce immediately, by any means, the InterLAN technical department.

III. BGP communities

Accepted (large):
39107:0:ASN – don’t advertise to peer with ASN
39107:1:ASN – advertise to peer with ASN
39107:0:0 – don’t advertise to any ASN
39107:1:0 – advertise to all ASN

Accepted:
39107:ASN – advertise only to peer with ASN
0:0 – don’t advertise to any ASN
0:ASN – don’t advertise to peer with ASN

0: communities have precedence over 39107: communities

Sent:
39107:100 – Members
39107:200 – Partners
39107:300 – Bucharest
39107:400 – Romania except Bucharest
39107:500 – International (outside Romania)
39107:600 – Content provider
39107:650 – Not content provider
39107:700 – Another IX
39107:ASN – ASN specific community – all routes are marked by this style of community