Skip to main content

neutron-bsdbridge

Neutron ML2 mechanism driver, L2 agent, DHCP agent and L3 agent for FreeBSD based on if_bridge(4) and pf(4).

Status

Features

  • ML2 mechanism driver that binds ports with vif_type=bridge and publishes to Nova
  • Implements one bridge per Neutron segment for vlan, flat and local networks.
  • L2 agent to manage bridge, taps and security group rules
  • Port security
  • DHCP agent running one dnsmasq per network inside separate VNET jails
  • L3 agent running each router inside a VNET jail with SNAT and floating IPs

Roadmap

  • vxlan segments
  • IPv6 tcp and udp security group rules
  • metadata agent
  • HA routers (CARP+pfsync)

Limitations

  • IPv6 tcp and udp rules are skipped and this traffic stays blocked
  • ARP is not inspected
  • Only IPv4 subnets are served by the DHCP agent
  • Only IPv4 subnets, routes and floating IPs are handled by the L3 agent
  • Distributed routers probably won't be supported

Host requirements

Make sure to configure net.link.bridge.pfil_member=1 on the host.

Add to the host pf.conf:

set state-policy if-bound
ether anchor "l2-neutron/port/*"
anchor "l2-neutron/port/*"

Configuration

neutron.conf

[DEFAULT]
service_plugins = router

ml2_conf.ini

[ml2]
mechanism_drivers = bsdbridge

bsdbridge_agent.ini

[bsdbridge]
physical_interface_mappings = physnet1:ix0

Map the physical network name in OpenStack to the actual uplink/trunk interfaces on the host.

For vlan networks, the L2 agent will create a vlan interface on top of the mapped physical interface and plug it to the respective bridge for you, but make sure that the actual network trunks those VLAN between hosts.

You can enable self-service/tenant networks based on VLANs by configuring a range of IDs that can be used:

[ml2]
tenant_network_types = vlan

[ml2_type_vlan]
network_vlan_ranges = physnet1:100:199

Now any networks created in non-admin projects will be allocated a vlan segment automatically (the ix0.<vid> uplink is created and plugged by the L2 agent). Same as above, ensure that the network fabric actually trunks this range of VLAN IDs to the interface on each host which is mapped in physical_interface_mappings.

Metadata

Release files for neutron-bsdbridge 0.9.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for neutron-bsdbridge 0.9.5
File Size Uploaded Provenance
neutron_bsdbridge-0.9.5.tar.gz 36.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for neutron-bsdbridge 0.9.5
File Interpreter ABI Platform
neutron_bsdbridge-0.9.5-py3-none-any.whl Python 3 none any Details

Total release size: 81.5 kB

Release files / neutron_bsdbridge-0.9.5.tar.gz

Download URL neutron_bsdbridge-0.9.5.tar.gz
Size 36.6 kB
Tags Source
SHA-256 checksum
How to use checksums
6d0b40f52fb3c7894c67813ac18abebfa819d9a418ae07050bf49a328e8c8366
BLAKE2b-256 checksum
How to use checksums
bd39ca68c5dbf567980929d1b56eeb277cd5750094805dc843188cbd56ebb272
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / neutron_bsdbridge-0.9.5-py3-none-any.whl

Download URL neutron_bsdbridge-0.9.5-py3-none-any.whl
Size 44.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2a96a09656b7e0c8a6dd43808df5c51d5b15eef33345134bf746d676fe0d27a8
BLAKE2b-256 checksum
How to use checksums
560be347772bd72e2f52e278ee46dc58ed525e0a3bb93791e522bb6197801ab8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for neutron-bsdbridge 0.9.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page