Skip to content

FreeSBC v0.6.3

Latest

Choose a tag to compare

@github-actions github-actions released this 28 Oct 02:41
· 4 commits to main since this release
4c41e83

FreeSBC v0.6.3 fixes two bugs. On Linux, freesbc run no longer refuses a loopback private.ip such as 127.0.0.3 that was never added to lo. A carrier's re-INVITE now reaches the switch with X-FreeSBC-Carrier. Configuration is unchanged: a v0.6.2 file loads as is.

curl -fsSL https://github.com/rasonyang/freesbc/releases/latest/download/install.sh | sh

Breaking changes

None.

Fixes

  • run rejected an unaliased 127/8 private.ip on Linux (#275, closes #274). Linux routes all of 127.0.0.0/8 to lo, so an address such as 127.0.0.3 works without an alias, for example with the switch on the same host. check accepted it, but run looked only at the addresses listed on the interfaces and exited 1 with private.ip 127.0.0.3 is not assigned to any local interface. Now an IPv4 loopback address is accepted when it falls within the loopback interface's prefix and the kernel lets it bind. macOS still needs sudo ifconfig lo0 alias <ip> up, and the error message now says so. Other addresses and IPv6 are unchanged.
  • A carrier's re-INVITE reached the switch without X-FreeSBC-Carrier (#273, closes #263). A carrier's ACK and other in-dialog requests were already stamped. A re-INVITE is now stamped too, and it counts in freesbc_edge_carrier_requests_total as an inbound INVITE. Client dialogs get no header, as before.

Known limitations and follow-ups

  • #266: GET /api/config leaves admin.allowed_hosts and admin.pprof out of the redacted snapshot. The running values are correct; they just aren't shown. Fixed on main by #276; the fix ships in the next release.
  • #257: the next monthly three-host run re-measures the carrier-in ceiling with the 8 MiB buffer, and the GC cuts of #170 and #173. Until then 3500 CPS is the loss-free carrier-in figure on 4 vCPU.