Bojin Network is a personal network for education and research, operated by Bojin Li under AS198734.
We explore BGP, IPv6 and anycast on the public Internet, while using the network for our self-hosted services and development environments. From edge routers to service gateways, it is both everyday infrastructure and an evolving network lab.
We have an open peering policy and welcome interconnection with other network operators.
AS198734 operates both IPv4 and IPv6, using the following address space:
Family
Prefix
Purpose
IPv4
44.31.223.0/24
Service network and anycast ingress
IPv6
2a0e:aa07:e0a0::/44
IPv6 aggregate address space
IPv6
2a0e:aa07:e0a0::/47
More-specific announcement within the aggregate
Our AS-SET, RIPE::AS198734:AS-BOJIN, can be used to build peering route filters.
Edge and Core
Our IPv4 network has BGP ingress points in New York, Las Vegas and Zurich, all announcing 44.31.223.0/24. WireGuard tunnels connect these edges to a service core hosted at OVH in the eastern United States, forwarding incoming traffic to the backend services.
The core uses VyOS for routing and forwarding, with Proxmox hosting the service VMs. Service addressing is separate from the provider-assigned underlay addresses: services use our own public prefixes rather than the hosts' native public addresses.
BGP selects the ingress edge. Return traffic is steered back through the corresponding ingress edge using connection marks and policy-based routing. We tie BFD monitoring of the edge-to-core paths to route advertisements: if a path fails, the affected edge withdraws its announcement so that traffic can enter through another edge. Outbound connections also have fallback routes.
The distributed ingress points provide routing redundancy, while the services remain centralized at the core.
Peering
We have an open peering policy, with no requirements for traffic ratios, presence at multiple sites or a peering contract. Personal experimental networks, education and research networks, and commercial networks are all welcome to peer with AS198734 wherever we share an interconnection point.
Internet Exchanges
We participate in IPv6 peering at the following exchanges. We connect to route servers and also welcome bilateral BGP sessions with networks at a shared exchange.
Exchange
Location
IPv6 Peering Address
ZXIX Hong Kong
Hong Kong
2406:840:1f:1000:0:19:8734:1
ixFabric - Sydney
Sydney, Australia
2a0e:8f01:1000:12::10d
ixFabric - Amsterdam
Amsterdam, Netherlands
2a0e:8f01:1000:11::12c
ixFabric - London
London, United Kingdom
2a0e:8f01:1000:10::122
ixFabric - Frankfurt
Frankfurt, Germany
2a0e:8f01:1000:24::124
4b42 Internet Exchange Point
Zurich, Switzerland
2001:7f8:d0::3:84e:1
FogIXP
Switzerland
2001:7f8:ca:1:0:19:8734:1
ONIX
Toronto, Canada
2001:504:125:e1::ec
Peering Policy
Have a valid public ASN and authorization to use and announce your prefixes.
Keep PeeringDB, IRR and applicable RPKI ROA information accurate, and provide a reachable NOC email address.
Announce only your own routes and any downstream routes agreed upon by both parties. Do not send a default route unless agreed in advance.
Send traffic over the peering only to destinations within the other party's advertised prefixes, and follow the exchange's technical and acceptable-use rules.
Request a Session
Please email your ASN, PeeringDB link, shared exchange, session addresses and IRR AS-SET to noc@bojin.li. A suggested subject line is Peering - AS<your number> - <exchange name>.
If you have an expected prefix count, BFD requirements or other special requests, please include those too. We will confirm the session parameters and prefix limits by email.
This network is personally maintained and operated on a best-effort basis. Thank you for your patience; ideas and conversations about network engineering and routing experiments are always welcome.
Bojin Network is a personal network for education and research, operated by Bojin Li under AS198734.
We explore BGP, IPv6 and anycast on the public Internet, while using the network for our self-hosted services and development environments. From edge routers to service gateways, it is both everyday infrastructure and an evolving network lab.
We have an open peering policy and welcome interconnection with other network operators.
Item
Details
ASN
AS198734
AS Name
BOJIN-AS
Registry
RIPE NCC
IRR AS-SET
RIPE::AS198734:AS-BOJIN
Peering Policy
Open Peering
PeeringDB
Bojin Network
Our Network
Address Space
AS198734 operates both IPv4 and IPv6, using the following address space:
Family
Prefix
Purpose
IPv4
44.31.223.0/24
Service network and anycast ingress
IPv6
2a0e:aa07:e0a0::/44
IPv6 aggregate address space
IPv6
2a0e:aa07:e0a0::/47
More-specific announcement within the aggregate
Our AS-SET, RIPE::AS198734:AS-BOJIN, can be used to build peering route filters.
Edge and Core
Our IPv4 network has BGP ingress points in New York, Las Vegas and Zurich, all announcing 44.31.223.0/24. WireGuard tunnels connect these edges to a service core hosted at OVH in the eastern United States, forwarding incoming traffic to the backend services.
The core uses VyOS for routing and forwarding, with Proxmox hosting the service VMs. Service addressing is separate from the provider-assigned underlay addresses: services use our own public prefixes rather than the hosts' native public addresses.
BGP selects the ingress edge. Return traffic is steered back through the corresponding ingress edge using connection marks and policy-based routing. We tie BFD monitoring of the edge-to-core paths to route advertisements: if a path fails, the affected edge withdraws its announcement so that traffic can enter through another edge. Outbound connections also have fallback routes.
The distributed ingress points provide routing redundancy, while the services remain centralized at the core.
Peering
We have an open peering policy, with no requirements for traffic ratios, presence at multiple sites or a peering contract. Personal experimental networks, education and research networks, and commercial networks are all welcome to peer with AS198734 wherever we share an interconnection point.
Internet Exchanges
We participate in IPv6 peering at the following exchanges. We connect to route servers and also welcome bilateral BGP sessions with networks at a shared exchange.
Exchange
Location
IPv6 Peering Address
ZXIX Hong Kong
Hong Kong
2406:840:1f:1000:0:19:8734:1
ixFabric - Sydney
Sydney, Australia
2a0e:8f01:1000:12::10d
ixFabric - Amsterdam
Amsterdam, Netherlands
2a0e:8f01:1000:11::12c
ixFabric - London
London, United Kingdom
2a0e:8f01:1000:10::122
ixFabric - Frankfurt
Frankfurt, Germany
2a0e:8f01:1000:24::124
4b42 Internet Exchange Point
Zurich, Switzerland
2001:7f8:d0::3:84e:1
FogIXP
Switzerland
2001:7f8:ca:1:0:19:8734:1
ONIX
Toronto, Canada
2001:504:125:e1::ec
Peering Policy
Request a Session
Please email your ASN, PeeringDB link, shared exchange, session addresses and IRR AS-SET to noc@bojin.li. A suggested subject line is Peering - AS<your number> - <exchange name>.
If you have an expected prefix count, BFD requirements or other special requests, please include those too. We will confirm the session parameters and prefix limits by email.
Contact
Purpose
Email
Network Operations and Peering
noc@bojin.li
Abuse and Security Incidents
noc@bojin.li
This network is personally maintained and operated on a best-effort basis. Thank you for your patience; ideas and conversations about network engineering and routing experiments are always welcome.
PeeringDB · bgp.tools · HE BGP Toolkit · RIPE Database
WHOIS Snapshot
The following registry snapshot is provided for reference and is not updated automatically. See the RIPE Database for current records.
View WHOIS records