jschoubben 06fd436eca The adopted broker declares its amqps bus port (5671) in listens ...

mesh-broker serves the amqps bus on 5671 (the control plane and every module's
events) but the lavinmq module declared only 5672, so the firewall's forward
chain — where the broker's published ports are matched — never opened 5671, and
a consumer on another node could not reach the bus over the overlay. Part of
issue 055.

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

2026-09-17 01:01:54 +02:00

..

bootstrap

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

provisioner

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

tools

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

client.ts

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

Dockerfile

Convert lavinmq: it is not only a broker, so it has to be built

2026-09-14 21:05:10 +02:00

index.ts

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

module.json

The adopted broker declares its amqps bus port (5671) in listens

2026-09-17 01:01:54 +02:00

package.json

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

tsconfig.json

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00