Хорошо, похожеiptables
в одиночку НЕ подходит.
Я попробую smcroute
и/или pimd
из репозиториев Ubuntu. До сих пор я не смог заставить ни одну работу.
Использование smcroute:
iptables
-A INPUT -i lo -j ACCEPT
-A FORWARD -i slan1 -o olan1 -j ACCEPT
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -p igmp -j ACCEPT
-A FORWARD -i olan1 -o slan1 -p tcp -m tcp --dport 50000 -m conntrack --ctstate NEW -j ACCEPT
-A FORWARD -i olan1 -o slan1 -p udp -m udp --dport 50000 -m conntrack --ctstate NEW -j ACCEPT
-A PREROUTING -d 239.255.100.100/32 -j TTL --ttl-set 64
smcroute 2.3.1 от troglobit.
Извлечено в/opt
./configure
использовались параметры по умолчанию.
файл конфигурации в:
/usr/local/etc/smcroute.conf
#phyint olan1 enable ttl-threshold 1
phyint olan1 enable ttl-threshold 5
phyint slan1 enable ttl-threshold 5
mgroup from olan1 group 239.255.100.100
mgroup from slan1 group 239.255.100.100
mroute from olan1 group 239.255.100.100 to slan1
mroute from slan1 group 239.255.100.100 to olan
sudo smcrouted
sudo smcroutectl show groups
GROUP (S,G) INBOUND
(*, 239.255.100.100) slan1
(*, 239.255.100.100) olan1
sudo smcroutectl show routs
ROUTE (S,G) INBOUND PACKETS BYTES OUTBOUND
(*, 239.255.100.100) slan1 0 0 olan1
(*, 239.255.100.100) olan1 0 0 slan1
(10.10.10.154, 239.255.100.100) slan1 2 344 olan1
(192.168.2.53, 239.255.255.250) olan1 4 776
(10.10.10.101, 239.255.100.100) slan1 1 32 olan1
(192.168.2.101, 239.255.100.100) olan1 1 32 slan1
(10.10.10.1, 239.255.100.100) slan1 2 64 olan1
Не все...
На многопользовательском ПК с WinXP -пришлось изменить маршрут:
route add 224.0.0.0 mask 240.0.0.0 10.10.10.153
необходимо использовать номер интерфейса вместо IP-адреса сетевого адаптера...
sudo smcroutectl show routs
ROUTE (S,G) INBOUND PACKETS BYTES OUTBOUND
(*, 239.255.100.100) slan1 0 0 olan1
(*, 239.255.100.100) olan1 0 0 slan1
(192.168.2.53, 239.255.255.250) olan1 4 776
(10.10.10.153, 239.255.100.100) slan1 1 32 olan1
LAN Messenger 1.2.32 network preferences
Сделайте smcroute демоном с помощью Upstart в Ubuntu 14
/etc/init/smcroute.conf
# Upstart for custom compiled smcroute
## jc 2017 08 24
description "SMCRoute, a static multicast router"
author "jc"
# Stanzas
# Stanzas control when and how a process is started and stopped
# See a list of stanzas here: http://upstart.ubuntu.com/wiki/Stanzas#respawn
# When to start the service
# start on runlevel [2345]
start on (local-filesystems and net-device-up IFACE!=lo) or runlevel [2345]
# When to stop the service
#stop on runlevel [016]
stop on runlevel [!2345]
# Automatically restart process if crashed
expect fork
respawn
exec /usr/local/sbin/smcrouted -N -f /usr/local/etc/smcroute.conf -d 10 -l notice
Кажется, все работает.Пусть какое-то время все работает со случайными перезагрузками и случайными сбоями в сети, нормальные вещи.
ДЕЛО
У меня такая же проблема. Я пытаюсь установить монго дб. Я вызываю команду./mongod, и установка не может быть завершена. Зависает на той же команде:
2019-09-21T21:45:17.039+0600 I SHARDING [LogicalSessionCacheReap] Marking collection config.transactions as collection version:
Mac OS Мохаве 10.14 Весь мой след:
MacBook-Pro-dns:mongo user$./mongod
2019-09-21T21:45:16.178+0600 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2019-09-21T21:45:16.187+0600 I CONTROL [initandlisten] MongoDB starting : pid=8310 port=27017 dbpath=/data/db 64-bit host=MacBook-Pro-dns.local
2019-09-21T21:45:16.187+0600 I CONTROL [initandlisten] db version v4.2.0
2019-09-21T21:45:16.187+0600 I CONTROL [initandlisten] git version: a4b751dcf51dd249c5865812b390cfd1c0129c30
2019-09-21T21:45:16.187+0600 I CONTROL [initandlisten] allocator: system
2019-09-21T21:45:16.187+0600 I CONTROL [initandlisten] modules: none
2019-09-21T21:45:16.187+0600 I CONTROL [initandlisten] build environment:
2019-09-21T21:45:16.187+0600 I CONTROL [initandlisten] distarch: x86_64
2019-09-21T21:45:16.187+0600 I CONTROL [initandlisten] target_arch: x86_64
2019-09-21T21:45:16.187+0600 I CONTROL [initandlisten] options: {}
2019-09-21T21:45:16.189+0600 W STORAGE [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.
2019-09-21T21:45:16.189+0600 I STORAGE [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-09-21T21:45:16.189+0600 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
2019-09-21T21:45:16.189+0600 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=7680M,cache_overflow=(file_max=0M),session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress],
2019-09-21T21:45:16.699+0600 I STORAGE [initandlisten] WiredTiger message [1569080716:699859][8310:0x10e6245c0], txn-recover: Recovering log 1 through 2
2019-09-21T21:45:16.762+0600 I STORAGE [initandlisten] WiredTiger message [1569080716:762524][8310:0x10e6245c0], txn-recover: Recovering log 2 through 2
2019-09-21T21:45:16.825+0600 I STORAGE [initandlisten] WiredTiger message [1569080716:825486][8310:0x10e6245c0], txn-recover: Main recovery loop: starting at 1/22912 to 2/256
2019-09-21T21:45:16.826+0600 I STORAGE [initandlisten] WiredTiger message [1569080716:826288][8310:0x10e6245c0], txn-recover: Recovering log 1 through 2
2019-09-21T21:45:16.884+0600 I STORAGE [initandlisten] WiredTiger message [1569080716:884735][8310:0x10e6245c0], txn-recover: Recovering log 2 through 2
2019-09-21T21:45:16.932+0600 I STORAGE [initandlisten] WiredTiger message [1569080716:932134][8310:0x10e6245c0], txn-recover: Set global recovery timestamp: (0,0)
2019-09-21T21:45:17.002+0600 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
2019-09-21T21:45:17.019+0600 I STORAGE [initandlisten] Timestamp monitor starting
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten]
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database.
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted.
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten]
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten] ** WARNING: This server is bound to localhost.
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten] ** Remote systems will be unable to connect to this server.
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten] ** Start the server with --bind_ip <address> to specify which IP
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten] ** addresses it should serve responses from, or with --bind_ip_all to
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten] ** bind to all interfaces. If this behavior is desired, start the
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten] ** server with --bind_ip 127.0.0.1 to disable this warning.
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten]
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten]
2019-09-21T21:45:17.020+0600 I CONTROL [initandlisten] ** WARNING: soft rlimits too low. Number of files is 256, should be at least 1000
2019-09-21T21:45:17.031+0600 I SHARDING [initandlisten] Marking collection local.system.replset as collection version: <unsharded>
2019-09-21T21:45:17.034+0600 I STORAGE [initandlisten] Flow Control is enabled on this deployment.
2019-09-21T21:45:17.034+0600 I SHARDING [initandlisten] Marking collection admin.system.roles as collection version: <unsharded>
2019-09-21T21:45:17.034+0600 I SHARDING [initandlisten] Marking collection admin.system.version as collection version: <unsharded>
2019-09-21T21:45:17.035+0600 I SHARDING [initandlisten] Marking collection local.startup_log as collection version: <unsharded>
2019-09-21T21:45:17.036+0600 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
2019-09-21T21:45:17.039+0600 I SHARDING [LogicalSessionCacheRefresh] Marking collection config.system.sessions as collection version: <unsharded>
2019-09-21T21:45:17.039+0600 I NETWORK [initandlisten] Listening on /tmp/mongodb-27017.sock
2019-09-21T21:45:17.039+0600 I NETWORK [initandlisten] Listening on 127.0.0.1
2019-09-21T21:45:17.039+0600 I NETWORK [initandlisten] waiting for connections on port 27017
2019-09-21T21:45:17.039+0600 I SHARDING [LogicalSessionCacheReap] Marking collection config.transactions as collection version: <unsharded>```
Это не ясно, но если вы достигли Marking collection...
из команды mongod
, MongoDB запущен.
Чтобы начать работу, откройте новое окно терминала, перейдите в папку bin и запустите mongo
. Часть моего замешательства заключалась в том, что он, казалось, зависал (в bash ), но это не так. Введите help
и все должно работать.