NOC / Technical Support: noc@jinix.id | Peering Requests: peering@jinix.id | Web: www.jinix.id
JNIX (Jakarta Neutral Internet Exchange) is a neutral, not-for-profit peering fabric operating from APJII Lantai 1 MMR, Jakarta. This page contains everything you need to connect and to configure BGP with our route servers.
Exchange Details
| IXP Name | JNIX — Jakarta Neutral Internet Exchange |
|---|---|
| IXP ASN | AS32200 |
| Peering LAN (IPv4) | 89.28.203.160/27 |
| VLAN Tag | 1073 |
| MTU | 1500 bytes |
| Location | APJII Lantai 1 MMR, Jakarta, Indonesia |
| Member Portal | https://ixp.jinix.id/ |
| Looking Glass | https://ixp.jinix.id/lg |
Route Servers
Route server peering is free, optional and strongly recommended — it gives you reachability to every other route server client from a single BGP session. Bilateral peering with individual members is of course also permitted.
| Router | Protocol | Peer IP | Peer AS | Software |
|---|---|---|---|---|
rs1 |
IPv4 | 89.28.203.161 |
32200 |
BIRD 2.x |
AS32200 into the AS path. If your router enforces that the
first AS in the path must equal the peer AS (Juniper enforce-first-as,
Cisco bgp enforce-first-as), you must disable it on the
route server session or the session will not stay up.
Quick Start
Configure your router interface on VLAN 1073 with the IPv4 address allocated to you, then:
- Peer with
89.28.203.161, remote AS32200 - Do not enable BGP multihop — the route server is on-link
- Announce only prefixes you originate or that belong to your customers
- Set your next hop to your own peering LAN address (default eBGP behaviour)
Port & Layer-2 Requirements
- One MAC address per port. Additional MACs will be suppressed.
- Only ARP (0x0806), IPv4 (0x0800) and IPv6 (0x86dd) ethertypes are permitted on the peering LAN.
- No link-local or discovery protocols towards the fabric: STP/BPDU, CDP, LLDP, MNDP, VTP, DTP, LACP (except on an agreed LAG), or keepalives.
- No IPv6 Router Advertisements, no DHCP server, no proxy ARP.
- Do not bridge the peering VLAN into your own network — route on it. Bridging is the single most common cause of IXP-wide incidents.
- Do not announce the peering LAN prefix
89.28.203.160/27to anyone. - Traffic to another member must only be sent after that member has announced the destination prefix to you (no default routing across the fabric).
Route Server Filtering Policy
Every prefix you send to the route servers is validated. Routes failing any check are dropped:
| Check | Behaviour |
|---|---|
| IRRDB prefix & origin filtering | Built from the AS-SET registered against your account and refreshed every 6 hours. Keep your IRR objects accurate or your prefixes will be rejected. |
| RPKI origin validation | RPKI invalid routes are dropped. Valid and unknown are accepted and tagged. |
| First AS in path must equal your AS | Rejected otherwise |
| Next hop must be your own peering IP | Rejected otherwise (next-hop hijack protection) |
| Prefix length | IPv4 accepted between /8 and /24 |
| Bogons / martians | Rejected |
| Transit-free (tier-1) ASNs in path | Rejected — prevents transit leaks |
| AS path length | Rejected above 64 hops |
| Max prefix | Default 500 per session. Contact us to raise it. |
BGP Communities
Use these large communities on routes you announce to the route servers
to control who receives them. <peer-as> is the AS number of the member concerned.
| Large Community | Action |
|---|---|
32200:0:<peer-as> | Do not announce to this member |
32200:0:0 | Do not announce to anyone |
32200:1:<peer-as> | Announce to this member (use together with 32200:0:0) |
32200:101:<peer-as> | Prepend your AS once towards this member |
32200:102:<peer-as> | Prepend twice |
32200:103:<peer-as> | Prepend three times |
Use 0 in place of <peer-as> to apply the action to all members.
The equivalent 16-bit communities 0:<peer-as> (block) and
32200:<peer-as> (allow) are also honoured.
Routes handed to you by the route servers carry these informational large communities:
| Large Community | Meaning |
|---|---|
32200:1000:1 | RPKI valid |
32200:1000:2 | RPKI unknown |
32200:1000:3 | RPKI not checked |
32200:1001:1 | IRRDB valid |
32200:1010:<asn> | Route learned from this member |
32200:1011:<asn> | Origin AS of the route |
Joining JNIX
- Email peering@jinix.id with your ASN, your IRR AS-SET, your PeeringDB record and your requested port speed.
- Arrange a cross connect to the JNIX switch at APJII Lantai 1 MMR.
- We allocate your peering LAN address and build your port and route server sessions.
- Configure BGP as above and confirm your sessions on the looking glass.
Please keep your PeeringDB record and IRR objects up to date — we use both to build your prefix filters.
Reporting a Problem
Email noc@jinix.id. To help us resolve it quickly, include:
- Your ASN and peering LAN IP address
- The affected peer ASN or route server, and prefixes involved
- Relevant BGP session state and log output
- Timestamps with timezone