Balkan Internet Exchange Points of presence

  • Telepoint - 122, Ovche Pole Str. Sofia
  • Daticum - 135, Tsarigradsko Shosse Blvd. Sofia
  • Neterra - 3 Grigorii Gorbatenko Str. Sofia
  • 3DC - Druzhba-1 district 10, 5030 Str. Sofia
  • TSBG - Kapitan Andreevo BG/TR Border
  • Synapsecom - 56, Pontou Str. Thessaloniki

Balkan Internet Exchange Statistics:

Balkan Internet Exchange

Balkan Internet Exchange Looking Glass:

http://b-ix.net/lg/

Technical Requirements

These Technical Requirements define the ways in which you may or may not make use of the BalkanIX services. This document will be regularly reviewed and revised to ensure maximum protection of service to BalkanIX participants. New versions of this document are effective after 10 working days of having been posted upon BalkanIX website.

1 Physical

1.1 Ethernet interfaces attached to BalkanIX ports shall be explicitly configured with duplex, speed and other configuration settings and shall not be auto-sensing.

2 MAC Layer

2.1 Frames forwarded to BalkanIX ports shall have one of the following ethertypes:

  • 0x0800 - IPv4
  • 0x0806 - ARP
  • 0x86dd - IPv6
2.2 All frames of a service forwarded to an individual BalkanIX port shall have the same source MAC address.
2.3 It is not permitted to use Spanning Tree Protocol enabled on a port connected to Balkan-IX.
2.4 It is not permitted to use proxy ARP enabled on a router port connected to Balkan-IX.
2.5 Frames forwarded to BalkanIX ports shall not be addressed to a multicast or broadcast MAC destination address except as follows:
  • broadcast ARP packets
  • multicast IPv6 Neighbor Discovery (ND) packets
2.6 Traffic for link-local protocols shall not be forwarded to BalkanIX ports except for the ARP but not proxy ARP and IPv6 ND. These link-local protocols include but are not limited to the following list:
  • IRDP
  • ICMP redirect
  • IEEE802 Spanning Tree
  • Vendor proprietary discovery protocols (e.g. CDP)
  • Interior Routing Protocols IGP (e.g. RIP, OSPF, IS-IS, IGRP, EIGRP) /Multicast.
  • BOOTP / DHCP
  • PIM-SM
  • PIM-DM
  • DVMRP

3 IP Layer

3.1 Interfaces connected to BalkanIX ports shall only use IP addresses and netmasks (prefix lengths) assigned to them by BalkanIX.
3.2 IP packets addressed to BalkanIX peering LAN directed broadcast address shall not be automatically forwarded to BalkanIX ports.

4 Routing

4.1 All exchange of routes across the BalkanIX network shall be via BGP4(+).
4.2 AS numbers used in BGP4(+) sessions across the BalkanIX network shall not be from range reserved for private use. Announcements from private IP address space (RFC1918) is not allowed. All peer should have valid Autonomous System Number registered.
4.3 All routes advertised shall be aggregated as far as possible.Не се допуска анонсирането на мрежи с мрежова маска по-малка от /24.
4.4 IP address space assigned to BalkanIX peering LAN shall not be advertised to other networks without explicit permission of BalkanIX. All routes advertised across the BalkanIX network shall point to the router advertising it unless an agreement has been made in advance in writing by BalkanIX and the members involved. All routes to be advertised in a peering session across BalkanIX shall be registered in the RIPE or other public routing registry. Participants may use more than one ASN for their BalkanIX peering provided that each ASN presented shares the same NOC and peering contact details..
4.5 Participant should announce only his network prefixes, own AS number and his customers networks and their AS Numbers. It is not allowed transit to other networks and AS numbers without explicit permissions from its owners.
4.6 Participants can establish BGP4 peering session with other participants based on mutual agreement from both parties, or to establish BGP session only with both route-servers RS. Balkan-IX recommends the use of RS for more efficient routing and easy configuration. Participant that do not want to use RS is invited to announce its networks only to RS only for statistical reasons, and they will not be propagated to any other peers in BalkanIX. More detailed information about the control of incoming and outgoing routing information in 6.

5 IP Traffic Exchange

5.1 IP traffic should be exchanged between peers only by the following ways:

  • by using route-servers (RS)
  • by direct BGP4 sessions
5.2 It is not allowed traffic between two ports used from one participant.
5.3 When maximum daily traffic is over 90% of the physical port speed for the last month, the participant is asked to increase its capacity to Balkan-IX.

6 Route-Server and Communities

6.1 Route-Server Details:

rs1.b-ix.netrs2.b-ix.net
ASN: 49401ASN: 49401
IPv4: 91.212.235.1/24IPv4: 91.212.235.121/24

6.2 All peers to Balkan Internet Exchange route-servers can use communities to control incoming and outgoing information. All transit communities, used from all participants are not modified or deleted.
Communities coming from Balkan Internet Exchange RS:
49401:1001Prefix is injected in Balkan-IX Sofia
49401:1003Prefix is injected in Balkan-IX Bucharest
49401:Prefix is announced from <peer AS>
49401:49401Prefix is announced to all peers
Communities that are accepted from Balkan Internet Exchange RS:
By default all incoming prefixes are announced to all peers, if they do not have BalkanIX specific community - 49401:.*
49401:0 Block the prefix to all peers
49401:<peer AS>Announce the prefix to <peer AS>
49401:49401Announce the prefix to all peers
49401:49401 + 49401:<peer AS>The prefix will be announced to all peers and will be blocked to peer with <peer AS>.