feat(docs): update speaker installation instructions and logging details

- Enhanced the speaker installation documentation to clarify the use of TCP port 179 and the logging commands for monitoring BIRD and evobgp-agent.
- Updated the speaker form dialog to include additional information about MikroTik connections and logging commands.
- Modified the BIRD configuration to include logging to stderr for better visibility during operations.
- Adjusted the Docker Compose configuration to ensure proper network settings and sysctl configurations for BGP functionality.

internal/speakerinstall/install.go

@@ -57,6 +57,7 @@ type renderData struct {
 
 const composeTemplate = `# EvoBGP replica: bird2 + evobgp-agent + Traefik (Let's Encrypt DNS-01 / Cloudflare).
 # Generated by control plane. Do not commit secrets. ACME state: volume evobgp_speaker_traefik_letsencrypt.
+# BGP: ports 179:179 like control plane (overlay sets router id). Logs: docker compose logs -f bird2 evobgp-agent
 
 name: evobgp-remote-speaker
 
@@ -70,12 +71,18 @@ services:
   bird2:
     image: {{.BirdImage}}
     restart: unless-stopped
-    network_mode: host
     cap_add:
       - NET_ADMIN
+    sysctls:
+      net.ipv4.ip_forward: "1"
+      net.ipv6.conf.all.forwarding: "1"
+    ports:
+      - "179:179/tcp"
     volumes:
       - bird_etc:/etc/bird
       - bird_run:/run/bird
+    networks:
+      - speaker-net
     logging: *default-logging
 
   evobgp-agent:
@@ -200,6 +207,8 @@ func dockerCommands(composeYAML string) string {
 	var b strings.Builder
 	b.WriteString(`# EvoBGP replica: bird2 + agent + Traefik (Let's Encrypt DNS-01 / Cloudflare)
 # docker login git.shx.one  # if images are private
+# BGP TCP/179 published like the control plane. Cloud security group must allow 179.
+# Logs: cd /opt/evobgp-speaker && docker compose logs -f bird2 evobgp-agent
 set -euo pipefail
 sysctl -w net.ipv4.ip_forward=1
 sysctl -w net.ipv6.conf.all.forwarding=1