Bandura Communications is a placeholder in the RIPE NCC registry.
Currently the following resources are assigned to Bandura Communications:
- AS202952
- Sponsored by freetransit.ch
- no IPv4
- IPv6 PA: 2a06:a005:1b90::/44 LOA
- IPv6 PA: 2a0e:8f02:21e0::/44
- Sponsored by freetransit.ch
- IPv6 PA: 2602:fafd:f06::/48 LOA
- Sponsored by IPvX Solutions LLC
Organisation ID |
ORG-BC256-RIPE |
AS-SET |
AS-BANDURA-COMMUNICATIONS-SET |
E-Mail |
noc@mk16.de |
Abuse E-Mail |
ripencc-abuse@mk16.de |
Maintainer ID |
MARK22K-MNT / MK25298-RIPE |
Maintainer PGP |
PGPKEY-699108C7 |
Maintainer E-Mail |
m.k@mk16.de |
Pingable |
cn-pingable.byeob.de |
Pingable IPv6 |
2a0e:8f02:21e0:: |
Pingable IPv6 |
2a06:a005:1b90:: |
PeeringDB
Network: https://www.peeringdb.com/net/30905
Organisation: https://www.peeringdb.com/org/33257
Peering
Peering policy: open - every peering is welcome, see peering request
Software: Bird2 (extended messages, graceful restart, enhanced refresh, long-lived graceful restart)
Announced networks
The following networks are distributed by my AS:
- 2a06:a005:1b90::/44
- 2a0e:8f02:21e0::/44
- 2602:fafd:f06::/48
This list is always tried to keep up to date.
BGP communities
Communitiy |
Name |
Description |
65535:65281 |
no-export |
do not advertise to any eBGP peers (implemented by bird) |
65535:65282 |
no-advertise |
do not advertise to any BGP peer (implemented by bird) |
65535:65283 |
no-export-subconfed |
do not advertise to any eBGP peer or to confederation (implemented by bird) |
see RFC1997, RFC8642
Large BGP communities
Output communities
202952:1:(1-9) |
Latency |
Community, which specifies the maximum latency. |
202952:2:(1-9) |
Bandwidth |
Community, which specifies the minimum bandwidth. |
202952:3:(1-4) |
Crypto / Encryption |
Community, which specifies how the transmitted data is encrypted. |
202952:4:(1-17) |
Region |
BGP communities for route origin (like in the dn42 wiki but subtracted with 40) |
202952:5:1 |
Connection via tunnel with very low latency and few hops or physical connection outside an IXP |
202952:5:2 |
Connection over Internet Exchange Points (Manually or via router server) |
202952:5:3 |
Connection over Tunnel |
202952:5:4 |
Connection over Virtual Internet Exchange Points (Manually or via router server) |
202952:5:5 |
Unknown type |
Downstream communities
202952:6:0 |
Peer does not accept downstream |
202952:6:1 |
Peer accepts downstream with notification |
202952:6:2 |
Peer accepts downstream without notification |
202952:7:1 |
Learned from downstream and should be annouced to upstreams |
202952:7:2 |
Learned from downstream of downstream and should be annouced to upstreams |
see Bird communities, Large BGP communities
202952:101:1 |
Can be used with tunnel class 3 or higher. Prevents a lower local_pref from being set due to the tunnel. |
Filters
The following filters are applied to imported routes:
- Any route that has an AS path containing bogen ASNs will be filtered.
- Any route that has an AS path length greater than 100 is filtered.
- IPv6 prefixes greater than /48 (for example /64) are filtered.
- Routes that have an invalid ROA (accepted unknown) are filtered.
- IP packets with a source address from our networks are denied.
Every route which belongs to this network has a valid ROA and RPKI entry. If this is not the case, I would be grateful if this could be reported to me.
Routing Policy
- Prefer route with the highest Local Preference attribute.
- Prefer route with the shortest AS path.
- Prefer the lowest value of the Multiple Exit Discriminator.
- Prefer routes received via eBGP over ones received via iBGP.
- Prefer older routes.
see BIRD 2.0 User’s Guide 6.3 BGP
bgp_med
bgp_med |
Description |
0 |
default |
+ [1-9] * 20 |
Bandwidth class |
+ [1-5] * 50 |
Connection type |
+ [1-9] * 300 |
Latency class |
bgp_local_pref
bgp_local_pref |
Description |
0 |
graceful shutdown |
100 |
default |
+ 700 |
Direct peer (AS path length = 1) |
- 200 |
When direct peer (AS path length = 1) and exported to iBGP |
+ 200 |
Connection type 1 and Direct peer (Exported only to iBGP peers with Connection Type 1 or 2) |
+ 50 |
Connection type 2 and Direct peer (Exported only to iBGP peers with Connection Type 1 or 2) |
+ 25 |
Connection type 3 and Direct peer (Exported only to iBGP peers with Connection Type 1 or 2) |
- 20 |
Connection type 3 or higher and not direct peer |
+/- manuel configured |
For example, in case of latency problems or slow connections. |
Addresses
Prefix |
Usage |
2a0e:8f02:21e0::/48 |
Full prefix |
- 2a0e:8f02:21e0::/64 |
Nodes |
- - 2a0e:8f02:21e0::/112 |
Node addresses |
- 2a0e:8f02:21e0:e::/64 |
End users |
- 2a0e:8f02:21e0:b::/64 |
Tunnelbroker |
- 2a0e:8f02:21e0:22::/64 |
Peering prefix (Lily Network) |
- 2a0e:8f02:21e0:23::/64 |
Peering prefix (Lily Network) |
2a0e:8f02:21e1::/48 |
Project zonewalking.de |
Prefix |
Usage |
2a06:a005:1b90::/44 |
Full prefix |
- 2a06:a005:1b90::/64 |
Nodes |
- - 2a06:a005:1b90::/112 |
Node addresses |
IXPs
Nodes
Name |
Location |
Bandwidth |
Provider |
Note |
arcadia.mk16.de |
Duesseldorf, Germany |
1Gbit/s (shared) |
First Root UG (haftungsbeschränkt) |
|
blinky.mk16.de |
Frankfurt, Germany |
100Mbit/s (shared) |
iFog GmbH |
|
august.mk16.de |
Kansas City, USA |
100MiB/s |
August Internet |
|
ixpsu.mk16.de |
China |
30Mbit/s (shared) |
IXP.SU |
weak resources |
ixkskb.mk16.de |
Taiwan |
250Mbit/s (shared) |
IX KSKB |
weak resources |
joey.mk16.de |
Frankfurt, Germany |
1Gbit/s (shared) |
Joey Julian Koenig |
|
moeix-sea.mk16.de |
Seattle, USA |
1 Gbits (shared) |
MoeQing Network Service |
|
IP addresses of my nodes:
Name |
IPv6 |
Anycast |
2a0e:8f02:21e0::, 2a06:a005:1b90:: |
arcadia.mk16.de |
2a0e:8f02:21e0::1, 2a06:a005:1b90::1 |
blinky.mk16.de |
2a0e:8f02:21e0::2, 2a06:a005:1b90::2 |
ixpsu.mk16.de |
2a0e:8f02:21e0::4, 2a06:a005:1b90::4 |
ixkskb.mk16.de |
2a0e:8f02:21e0::5, 2a06:a005:1b90::5 |
joey.mk16.de |
2a0e:8f02:21e0::6, 2a06:a005:1b90::6 |
august.mk16.de |
2a0e:8f02:21e0::7, 2a06:a005:1b90::7 |
moeix-sea.mk16.de |
2a0e:8f02:21e0::8, 2a06:a005:1b90::8 |
interix.mk16.de |
2a0e:8f02:21e0::9, 2a06:a005:1b90::9 |
Peerings
MANRS
Bandura Communications is a participant in MANRS. We implement Action 1-4, of which Action 1, 3 and 4 have been confirmed by MANRS. Confirmation of Action 2 by MANRS has been requested. Our participant site can be reached at https://www.manrs.org/participant/4084/.