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.

deploy/bird/bird.conf

@@ -1,5 +1,6 @@
 # Default BIRD 2 config for EvoBGP Docker stack (operator extends with include "bird.d/*.conf";).
 router id 192.0.2.1;
+log stderr all;
 
 protocol device {
 }

deploy/compose/docker-compose.remote-speaker.yaml

@@ -7,9 +7,12 @@
 #     --env-file .env.remote-speaker --env-file .env.remote-speaker-tls up -d
 #
 # Profiles:
-#   production (default) — bird2 host + agent + evobgp-edge
+#   production (default) — bird2 (speaker-net, 179:179) + agent + evobgp-edge
 #   plain              — bird2 + agent без Traefik (lab)
 #   fallback           — + sync-bundle polling
+#
+# BGP TCP/179 as on the control plane. Overlay sets router id / local.
+# Logs: docker compose logs -f bird2 evobgp-agent
 
 name: evobgp-remote-speaker
 
@@ -24,13 +27,18 @@ services:
     profiles: ["production", "plain", "fallback"]
     image: ${EVOBGP_REGISTRY:-git.shx.one/denozord}/evobgp-bird2:${EVOBGP_IMAGE_TAG:-latest}
     restart: unless-stopped
-    network_mode: host
     cap_add:
       - NET_ADMIN
-    # sysctls нельзя с network_mode: host — включите ip_forward на VPS (см. docs/remote-speakers.md)
+    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: