Skip to content
Business connectivity

BGP & Routing

Assess routing control for networks with specialist requirements.

KernWi-Fi can review BGP and routing requirements for suitable business, carrier and multi-site environments. The assessment starts with your network resources, intended upstream connections, equipment capabilities and operational responsibilities.

Availability and final service inclusions are confirmed after qualification and design.

Your options

Design the routing policy before enabling the session

Suitability

Establish whether BGP is needed

BGP exchanges reachability information between autonomous systems. Many business connections can use a simpler design; specialist routing should solve a defined network requirement.

Resources and authority

Confirm the right to originate routes

Review the autonomous system number, prefixes and authority to use them. Provider requirements and acceptable announcements must be agreed before any routing session is configured.

Route policy

Define what is accepted and announced

Discuss default routes, selected routes or full tables only where supported. Filters, prefix limits and policy boundaries need to match the service and router capacity.

Route-origin records

Review registration and authorisation

Check the applicable routing-registry records and RPKI route-origin authorisations with the resource holder. Creating or changing those records requires the appropriate authority.

Multiple upstreams

Assess the complete resilience design

BGP can be part of a multi-upstream network, but it does not by itself create physical diversity or uninterrupted operation. Access paths, addressing and failover behaviour still require assessment.

Operations

Plan testing, monitoring and changes

Define session checks, route visibility, escalation and change approval. Any monitoring or managed routing functions are included only where specified in the accepted proposal.

Assessment and design

Specialist routing needs clear boundaries

The service design must confirm protocol support, accepted prefixes, routing policy and equipment responsibilities. A full internet routing table, particular communities or specific traffic-engineering features are not assumed.

Before implementation, agree an authorised change window, validation and rollback plan. Routing-policy changes can affect reachability, so control of customer and upstream equipment must be clearly assigned.

Network resources

Provide the ASN, prefix inventory and resource-holder details through an agreed secure process.

Routing objective

Describe the upstreams, desired route exchange and resilience goals.

Router capability

Review interfaces, software support, route scale and processing capacity.

Operational control

Agree policy ownership, authorised changes, acceptance checks and escalation.

From enquiry to handover

A clear path to the right solution

  1. Review the requirementsDiscuss locations, applications, existing services and the intended outcome.
  2. Confirm the designAssess suitable services and agree equipment, responsibilities, pricing and terms.
  3. Agree delivery and checksPlan authorised changes, acceptance checks and the support handover before implementation.

BGP & Routing questions

Do I need BGP for a static IP address?

Usually a static-address service can operate without a customer BGP session. The appropriate routing method depends on the service and network requirements.

Can I use my existing ASN and addresses?

They can be assessed, subject to ownership or authority, provider requirements, routing policy and service compatibility.

Does BGP guarantee seamless failover?

No. Convergence, reachability, stateful applications, addressing and underlying service paths can affect the result. The design needs suitable testing.

Are full routes and advanced policy controls included?

No such features are assumed. Route options, filters, limits, supported attributes and management scope must be explicitly confirmed.

Supporting network equipment

Equipment selected for the network design

KernWi-Fi works with MikroTik and UniFi platforms. The appropriate equipment, configuration and management arrangements depend on the site, service handoff and agreed project requirements.

MikroTik CCR2004 · Representative routing equipment
MikroTik CCR2004 · Representative routing equipment

Equipment shown is illustrative and is not automatically included with a service. Product imagery: MikroTik and Ubiquiti.

Discuss your requirements

Discuss BGP & Routing

Tell us about your locations, applications, existing services and the outcome you need. KernWi-Fi can assess suitable options and prepare a proposal with a clear scope.