Здравствуйте, гость ( Вход | Регистрация )
|
28.12.2008, 12:52
Сообщение
#1
|
|
Группа: Admin Сообщений: 2434 Регистрация: 8.10.2005 Из: Пушкино Пол: Сегмент: 7 |
В ситуации, когда доступ в сеть идет через linux-сервер, на котором делается nat для пользователей за ним и есть необходимость давать этим пользователям IPTV, которое работает при подключении напрямую, может помочь программа igmpproxy
ее необходимо скачать, собрать и запустить, при этом подготовив конфиг CODE ######################################################## # # Example configuration file for the IgmpProxy # -------------------------------------------- # # The configuration file must define one upstream # interface, and one or more downstream interfaces. # # If multicast traffic originates outside the # upstream subnet, the "altnet" option can be # used in order to define legal multicast sources. # (Se example...) # # The "quickleave" should be used to avoid saturation # of the upstream link. The option should only # be used if it's absolutely nessecary to # accurately imitate just one Client. # ######################################################## ##------------------------------------------------------ ## Enable Quickleave mode (Sends Leave instantly) ##------------------------------------------------------ quickleave ##------------------------------------------------------ ## Configuration for eth0 (Upstream Interface) ##------------------------------------------------------ phyint eth0 upstream ratelimit 0 threshold 1 altnet 77.246.100.0/24 # altnet 77.246.98.0/24 # altnet 77.246.96.0/24 # altnet 10.0.0.0/8 # altnet 192.168.0.0/24 ##------------------------------------------------------ ## Configuration for eth1 (Downstream Interface) ##------------------------------------------------------ phyint eth1 downstream ratelimit 0 threshold 1 ##------------------------------------------------------ ## Configuration for eth2 (Disabled Interface) ##------------------------------------------------------ #phyint eth1 disabled eth0 - интерфейс, который смотрит в нашу сеть(WAN) eth1 - интерфейс, который смотрит во внутреннюю сеть(LAN) в iptables должен быть разрешен igmp, а в sysctl rp_filter=0 net.ipv4.conf.eth0.rp_filter=0 net.ipv4.conf.eth1.rp_filter=0 также, в зависимости от настроек firewall, может понадобится разрешить трафик C 77.246.100.0/24 НА адреса 224.0.0.0/24 и 224.0.42.0/24, это пока единственные сети, которые используются для вещания IPTV. это все, что касается iptv |
|
23.1.2010, 10:35
Сообщение
#2
|
|
Рядовой Группа: Пользователи Сообщений: 33 Регистрация: 16.9.2009 Пол: Сегмент: 166 |
Код igmpproxy -h Usage: igmpproxy [-h] [-d] [-v [-v]] <configfile> -h Display this help screen -d Run in debug mode. Output all messages on stderr -v Be verbose. Give twice to see even debug messages. igmpproxy 0.1 /etc/sysctl.conf Код net.ipv4.conf.br0.rp_filter=0 net.ipv4.conf.eth1.rp_filter=0 net.ipv4.ip_forward=1 igmpproxy.conf Код ##------------------------------------------------------ ## Enable Quickleave mode (Sends Leave instantly) ## Эту строчку раскомментируют только в том случае, ## если внути всего лишь один клиент IP TV ##------------------------------------------------------ #quickleave ##------------------------------------------------------ ## Configuration for eth1 (Upstream Interface) ## Здесь указаны параметры для публичного интерфейса, ## на который придет поток от провайдера ##------------------------------------------------------ phyint eth1 upstream #ratelimit 0 threshold 1 altnet 77.246.100.0/24 # altnet 0.0.0.0/0 # altnet 10.20.0.0/16 # altnet 88.210.40.0/24 # altnet 80.240.211.0/22 ##------------------------------------------------------ ## Configuration for br0 (Downstream Interface) ## Типовая конфигурация для внутреннего интерфейса ##------------------------------------------------------ phyint br0 downstream #ratelimit 0 threshold 1 ##------------------------------------------------------ ## Configuration for eth2 (Disabled Interface) ## eth2 в системе есть, но не используется никем, отключаем ##------------------------------------------------------ #phyint eth2 disabled запускаю командой Код igmpproxy -d /etc/igmpproxy.conf получаю Код MC-Router API already in use; Errno(98): Address already in use на самом шлюзе IPTV есть, за шлюзом IPTV нету. Где могут быть грабли? PS Firewall на машине за шлюзом выключен. Сообщение отредактировал AlekSher - 24.1.2010, 11:27 |
|
24.1.2010, 12:19
Сообщение
#3
|
|
Рядовой Группа: Пользователи Сообщений: 33 Регистрация: 16.9.2009 Пол: Сегмент: 166 |
Всё грабли найдены... в виде другой службы... запуск прошел успешно, но TV нет...
CODE igmpproxy -v -d /etc/igmpproxy.conf adding VIF, Ix 0 Fl 0x0 IP 0x04a6de59 eth1, Threshold: 1, Ratelimit: 0 adding VIF, Ix 1 Fl 0x0 IP 0x600bdd0a eth2, Threshold: 1, Ratelimit: 0 adding VIF, Ix 2 Fl 0x0 IP 0x0101a8c0 br0, Threshold: 1, Ratelimit: 0 adding VIF, Ix 3 Fl 0x0 IP 0x0101a8c0 ppp0, Threshold: 1, Ratelimit: 0 adding VIF, Ix 4 Fl 0x0 IP 0x0101a8c0 ppp1, Threshold: 1, Ratelimit: 0 adding VIF, Ix 5 Fl 0x0 IP 0x0164a8c0 tap5, Threshold: 1, Ratelimit: 0 joinMcGroup: 224.0.0.2 on br0 joinMcGroup: 224.0.0.2 on ppp0 MRT_ADD_MEMBERSHIP failed; Errno(98): Address already in use joinMcGroup: 224.0.0.2 on ppp1 MRT_ADD_MEMBERSHIP failed; Errno(98): Address already in use RECV Membership query from 192.168.1.1 to 224.0.0.1 RECV Membership query from 192.168.1.1 to 224.0.0.1 RECV Membership query from 192.168.1.1 to 224.0.0.1 RECV V2 member report from 192.168.1.1 to 224.0.0.2 The IGMP message was from myself. Ignoring. RECV V2 member report from 192.168.1.1 to 224.0.0.251 The IGMP message was from myself. Ignoring. Inserted route table entry for 236.191.66.191 on VIF #-1 RECV Membership query from 192.168.1.1 to 224.0.0.1 RECV Membership query from 192.168.1.1 to 224.0.0.1 RECV Membership query from 192.168.1.1 to 224.0.0.1 RECV V2 member report from 192.168.1.1 to 224.0.0.2 The IGMP message was from myself. Ignoring. RECV V2 member report from 192.168.1.1 to 224.0.0.251 The IGMP message was from myself. Ignoring. Inserted route table entry for 238.24.200.222 on VIF #-1 Inserted route table entry for 227.226.43.193 on VIF #-1 Inserted route table entry for 226.43.193.235 on VIF #-1 Inserted route table entry for 235.215.105.76 on VIF #-1 RECV Membership query from 89.222.166.1 to 224.0.0.1 RECV Membership query from 89.222.166.1 to 224.0.0.1 RECV Membership query from 192.168.1.1 to 224.0.0.1 RECV Membership query from 192.168.1.1 to 224.0.0.1 RECV Membership query from 192.168.1.1 to 224.0.0.1 RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV V2 member report from 192.168.1.1 to 224.0.0.251 The IGMP message was from myself. Ignoring. RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV V2 member report from 89.222.166.4 to 224.0.0.251 The IGMP message was from myself. Ignoring. RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV V2 member report from 192.168.1.1 to 224.0.0.2 The IGMP message was from myself. Ignoring. RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.2.127.254 RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 RECV Leave message from 192.168.1.13 to 224.0.0.2 RECV Membership query from 192.168.1.1 to 224.0.42.1 Inserted route table entry for 224.0.1.60 on VIF #-1 Inserted route table entry for 236.30.215.181 on VIF #-1 Removing MFC: 89.222.166.61 -> 236.191.66.191, InpVIf: 0 MRT_DEL_MFC; Errno(2): No such file or directory CODE # Generated by iptables-save v1.4.4 on Sun Jan 24 13:20:57 2010
*nat :PREROUTING ACCEPT [3336:268047] :POSTROUTING ACCEPT [513:46073] :OUTPUT ACCEPT [513:46073] :VSERVER - [0:0] -A POSTROUTING ! -s 89.222.166.4/32 -o eth1 -j SNAT --to-source 89.222.166.4 COMMIT # Completed on Sun Jan 24 13:20:57 2010 # Generated by iptables-save v1.4.4 on Sun Jan 24 13:20:57 2010 *mangle :PREROUTING ACCEPT [26773:2489082] :INPUT ACCEPT [22557:1626245] :FORWARD ACCEPT [3921:980624] :OUTPUT ACCEPT [31378:37704662] :POSTROUTING ACCEPT [35352:38687144] COMMIT # Completed on Sun Jan 24 13:20:57 2010 # Generated by iptables-save v1.4.4 on Sun Jan 24 13:20:57 2010 *filter :INPUT DROP [1691:178544] :FORWARD DROP [0:0] :OUTPUT ACCEPT [31377:37704504] -A INPUT -m state --state INVALID -j DROP -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i lo -m state --state NEW -j ACCEPT -A INPUT -i br0 -m state --state NEW -j ACCEPT -A INPUT -d 224.0.0.0/4 -p igmp -j ACCEPT -A INPUT -d 224.0.0.0/4 -p udp -m udp ! --dport 1900 -j ACCEPT -A FORWARD -m state --state INVALID -j DROP -A FORWARD -d 224.0.0.0/4 -p udp -j ACCEPT -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i lo -m state --state NEW -j ACCEPT -A FORWARD -i br0 -m state --state NEW -j ACCEPT -A FORWARD -m conntrack --ctstate DNAT -j ACCEPT -A OUTPUT -m state --state INVALID -j DROP COMMIT # Completed on Sun Jan 24 13:20:57 2010 |
|
1.2.2010, 11:47
Сообщение
#4
|
|
Рядовой Группа: Пользователи Сообщений: 33 Регистрация: 16.9.2009 Пол: Сегмент: 166 |
ау техподдержка... вы где... помогите, пока на бесплатных оттестироваться
|
|
1.2.2010, 12:36
Сообщение
#5
|
|
Группа: Пользователи Сообщений: 2370 Регистрация: 17.7.2007 Пол: Сегмент: 33 |
А в чем помогать? igmpproxy работает на любых *nix без каких либо проблем. Если проблемы есть ковырять все по-очереди.
PS это полноценный ПК, или роутер с линухой? |
|
1.2.2010, 12:55
Сообщение
#6
|
||||||||||||||||||||||||
Рядовой Группа: Пользователи Сообщений: 33 Регистрация: 16.9.2009 Пол: Сегмент: 166 |
Это полноценный ПК с системой ubuntu 9.10 igmpproxy ставиться из Код deb http://ppa.launchpad.net/konishchevdmitry/ppa/ubuntu karmic main Вот в том то и проблема, всё по очереди делаю, а оно не работает... может я буковку где или циферку попутал, может iptables где режет. хотелось для уверенности ещё и конкретные рекомендации получить по настройке iptables. Проверяю на ноуте, через провод. Напрямую, если ваш провод воткнуть в ноут всё показывает Может для диагностики проблемы ещё какие данные сетевой статистики нужны, там netstat, tcpdump? |
|||||||||||||||||||||||
|
1.2.2010, 13:19
Сообщение
#7
|
|
Группа: Пользователи Сообщений: 2370 Регистрация: 17.7.2007 Пол: Сегмент: 33 |
У меня в iptables пусто. т.е. я не фильтрую ничего, начните с этого. А по мере необходимости - добавляйте.
|
|
1.2.2010, 19:17
Сообщение
#8
|
|
Группа: Admin Сообщений: 2434 Регистрация: 8.10.2005 Из: Пушкино Пол: Сегмент: 7 |
для конфигурации iptables рекомендую изучить shorewall
apt-get install shorewall-perl shorewall-common в /etc/shorewall должны лежать конфиги, берутся из /usr/share/doc/shorewall-common/examples и далее допиливаются под нужды в файл rules для мультикаста добавить типа такого CODE ACCEPT $FW mc udp 5000 ACCEPT net $FW igmp ACCEPT loc $FW igmp ACCEPT net loc igmp ACCEPT $FW net igmp ACCEPT $FW loc igmp ACCEPT net fw:224.0.0.0/4 ACCEPT net loc:224.0.0.0/4 ACCEPT $FW loc:224.0.0.0/4 mc - это зона, не имеющая отношения к внутренним сетям, нужна, т.к. мультикаст - это трафик от внешнего ip-адреса на мультикастовый адрес, который не принадлежит ни одному локальному интерфейсу. файл zones выглядит примерно так Код fw firewall net ipv4 loc ipv4 wan ipv4 mc ipv4 все основные описания конфигов есть в документации и на сайте shorewall затем в shorewall.conf прописать SHOREWALL_COMPILER=perl и оставить как есть MULTICAST=No и когда будет закончена конфигурация нужных правил, то прописать STARTUP_ENABLED=Yes и запустить его(не забыть про /etc/default/shorewall). |
|
1.2.2010, 21:38
Сообщение
#9
|
|
Рядовой Группа: Пользователи Сообщений: 33 Регистрация: 16.9.2009 Пол: Сегмент: 166 |
О спасибо, документацию нашел здесь будем пробовать |
|
10.2.2010, 22:12
Сообщение
#10
|
|
Мл.Сержант Группа: Пользователи Сообщений: 141 Регистрация: 8.6.2005 Из: Пушкино Пол: Сегмент: 31 |
По FreeBSD можете замечания высказать? IPTV не пользуюсь по причине сыроватости, да и хочется уже сразу приставку поставить. Может зря я впереди паровоза, но опять же если есть что сказать по делу внимательно выслушаю как официального источника по настройке. NAT использую от pf(пакетный фильтр)
Вопрос снят! Не увидел темы http://forum.beirel.ru/index.php?showtopic=5123 Сообщение отредактировал Boom - 11.2.2010, 20:20 |
|
17.11.2012, 19:39
Сообщение
#11
|
|
Рядовой Группа: Пользователи Сообщений: 33 Регистрация: 16.9.2009 Пол: Сегмент: 166 |
конфиг igmpproxy
Код ######################################################## # # Example configuration file for the IgmpProxy # -------------------------------------------- # # The configuration file must define one upstream # interface, and one or more downstream interfaces. # # If multicast traffic originates outside the # upstream subnet, the "altnet" option can be # used in order to define legal multicast sources. # (Se example...) # # The "quickleave" should be used to avoid saturation # of the upstream link. The option should only # be used if it's absolutely nessecary to # accurately imitate just one Client. # ######################################################## ##------------------------------------------------------ ## Enable Quickleave mode (Sends Leave instantly) ##------------------------------------------------------ quickleave phyint eth1 upstream ratelimit 0 threshold 1 #это просто копипастить. интерфейс для провайдела. altnet 239.255.255.250/32 altnet 77.246.100.0/24 altnet 89.222.166.0/24 #altnet 192.168.11.0/24 phyint br0 downstream ratelimit 0 threshold 1 #это интерфейс смотрящий в домашнюю сеть. altnet 192.168.11.0/24 #диапазон домашней сети. ##------------------------------------------------------ ## Configuration for eth2 (Disabled Interface) ##------------------------------------------------------ #phyint eth1 disabled #phyint tap0 disabled #phyint tap1 disabled #phyint tap2 disabled phyint tap3 disabled phyint lo disabled sysctl.conf Код # # /etc/sysctl.conf - Configuration file for setting system variables # See /etc/sysctl.d/ for additional system variables # See sysctl.conf (5) for information. # #kernel.domainname = example.com # Uncomment the following to stop low-level messages on console #kernel.printk = 3 4 1 3 ##############################################################3 # Functions previously found in netbase # # Uncomment the next two lines to enable Spoof protection (reverse-path filter) # Turn on Source Address Verification in all interfaces to # prevent some spoofing attacks #net.ipv4.conf.default.rp_filter=1 #net.ipv4.conf.all.rp_filter=1 # Uncomment the next line to enable TCP/IP SYN cookies # See http://lwn.net/Articles/277146/ # Note: This may impact IPv6 TCP sessions too #net.ipv4.tcp_syncookies=1 # Uncomment the next line to enable packet forwarding for IPv4 net.ipv4.ip_forward=1 # Uncomment the next line to enable packet forwarding for IPv6 # Enabling this option disables Stateless Address Autoconfiguration # based on Router Advertisements for this host #net.ipv6.conf.all.forwarding=1 ################################################################### # Additional settings - these settings can improve the network # security of the host and prevent against some network attacks # including spoofing attacks and man in the middle attacks through # redirection. Some network environments, however, require that these # settings are disabled so review and enable them as needed. # # Do not accept ICMP redirects (prevent MITM attacks) #net.ipv4.conf.all.accept_redirects = 0 #net.ipv6.conf.all.accept_redirects = 0 # _or_ # Accept ICMP redirects only for gateways listed in our default # gateway list (enabled by default) # net.ipv4.conf.all.secure_redirects = 1 # # Do not send ICMP redirects (we are not a router) #net.ipv4.conf.all.send_redirects = 0 # # Do not accept IP source route packets (we are not a router) #net.ipv4.conf.all.accept_source_route = 0 #net.ipv6.conf.all.accept_source_route = 0 # # Log Martian Packets #net.ipv4.conf.all.log_martians = 1 # net.ipv4.conf.default.rp_filter = 0 net.ipv4.conf.all.rp_filter = 0 net.ipv4.conf.eth0.rp_filter = 0 net.ipv4.conf.eth1.rp_filter = 0 net.ipv4.conf.br0.rp_filter = 0 #net.ipv4.conf.eth0.force_igmp_version=2 #net.ipv4.conf.br0.force_igmp_version=2 #net.ipv4.conf.eth1.force_igmp_version=2 Запускаю Код root@schsrv:/etc# igmpproxy -d -v /etc/igmpproxy.conf adding VIF, Ix 0 Fl 0x0 IP 0x04a6de59 eth1, Threshold: 1, Ratelimit: 0 adding VIF, Ix 1 Fl 0x0 IP 0x010ba8c0 br0, Threshold: 1, Ratelimit: 0 adding VIF, Ix 2 Fl 0x0 IP 0x0600a8c0 tap3, Threshold: 1, Ratelimit: 0 joinMcGroup: 224.0.0.2 on br0 RECV Membership query from 192.168.11.1 to 224.0.0.1 RECV V2 member report from 192.168.11.1 to 224.0.0.2 The IGMP message was from myself. Ignoring. RECV V2 member report from 192.168.11.88 to 239.255.255.250 Inserted route table entry for 239.255.255.250 on VIF #1 joinMcGroup: 239.255.255.250 on eth1 RECV V2 member report from 89.222.166.4 to 239.255.255.250 The IGMP message was from myself. Ignoring. Route activation request from 89.222.166.4 for 239.255.255.250 is from myself. Ignoring. The source address 192.168.11.88 for group 239.255.255.250, is not in any valid net for upstream VIF. RECV V2 member report from 192.168.11.88 to 224.0.42.1 Inserted route table entry for 224.0.42.1 on VIF #1 joinMcGroup: 224.0.42.1 on eth1 RECV V2 member report from 89.222.166.4 to 224.0.42.1 The IGMP message was from myself. Ignoring. Route activation request from 89.222.166.4 for 224.0.42.1 is from myself. Ignoring. RECV V2 member report from 192.168.11.88 to 224.0.42.1 Updated route entry for 224.0.42.1 on VIF #1 RECV V2 member report from 89.222.166.4 to 239.255.255.250 The IGMP message was from myself. Ignoring. RECV Leave message from 192.168.11.88 to 224.0.0.2 leaveMcGroup: 224.0.42.1 on eth1 RECV Membership query from 192.168.11.1 to 224.0.42.1 RECV V2 member report from 192.168.11.88 to 224.0.42.1 Updated route entry for 224.0.42.1 on VIF #1 joinMcGroup: 224.0.42.1 on eth1 RECV V2 member report from 89.222.166.4 to 224.0.42.1 The IGMP message was from myself. Ignoring. RECV V2 member report from 192.168.11.88 to 224.0.42.1 Updated route entry for 224.0.42.1 on VIF #1 The source address 192.168.11.88 for group 239.255.255.250, is not in any valid net for upstream VIF. RECV Leave message from 192.168.11.88 to 224.0.0.2 leaveMcGroup: 224.0.42.1 on eth1 RECV Membership query from 192.168.11.1 to 224.0.42.1 RECV V2 member report from 89.222.166.4 to 239.255.255.250 The IGMP message was from myself. Ignoring. Route activation request from 89.222.166.4 for 239.255.255.250 is from myself. Ignoring. RECV Membership query from 192.168.11.1 to 224.0.42.1 RECV Membership query from 192.168.11.1 to 224.0.42.1 Route is not active. No kernel updates done. RECV Membership query from 192.168.11.1 to 224.0.0.1 RECV V2 member report from 192.168.11.88 to 239.255.255.250 Updated route entry for 239.255.255.250 on VIF #1 RECV V2 member report from 192.168.11.1 to 224.0.0.2 The IGMP message was from myself. Ignoring. RECV V2 member report from 192.168.11.88 to 224.0.42.1 Inserted route table entry for 224.0.42.1 on VIF #1 joinMcGroup: 224.0.42.1 on eth1 RECV V2 member report from 89.222.166.4 to 224.0.42.1 The IGMP message was from myself. Ignoring. Route activation request from 89.222.166.4 for 224.0.42.1 is from myself. Ignoring. RECV V2 member report from 192.168.11.88 to 224.0.42.1 Updated route entry for 224.0.42.1 on VIF #1 RECV Leave message from 192.168.11.88 to 224.0.0.2 leaveMcGroup: 224.0.42.1 on eth1 RECV Membership query from 192.168.11.1 to 224.0.42.1 RECV Membership query from 192.168.11.1 to 224.0.42.1 The source address 192.168.11.88 for group 239.255.255.250, is not in any valid net for upstream VIF. Route is not active. No kernel updates done. RECV Membership query from 192.168.11.1 to 224.0.0.1 RECV V2 member report from 192.168.11.88 to 239.255.255.250 Updated route entry for 239.255.255.250 on VIF #1 RECV V2 member report from 192.168.11.88 to 224.0.42.1 Inserted route table entry for 224.0.42.1 on VIF #1 joinMcGroup: 224.0.42.1 on eth1 RECV V2 member report from 89.222.166.4 to 224.0.42.1 The IGMP message was from myself. Ignoring. Route activation request from 89.222.166.4 for 224.0.42.1 is from myself. Ignoring. RECV V2 member report from 192.168.11.88 to 224.0.42.1 Updated route entry for 224.0.42.1 on VIF #1 RECV Leave message from 192.168.11.88 to 224.0.0.2 leaveMcGroup: 224.0.42.1 on eth1 RECV Membership query from 192.168.11.1 to 224.0.42.1 RECV V2 member report from 192.168.11.1 to 224.0.0.2 The IGMP message was from myself. Ignoring. The source address 192.168.11.88 for group 239.255.255.250, is not in any valid net for upstream VIF. RECV Membership query from 192.168.11.1 to 224.0.42.1 ^Cselect() failure; Errno(4): Interrupted system call Got a interupt signal. Exiting. Route is not active. No kernel updates done. leaveMcGroup: 224.0.42.1 on eth1 MRT_DROP_MEMBERSHIP failed; Errno(99): Cannot assign requested address Route is not active. No kernel updates done. leaveMcGroup: 239.255.255.250 on eth1 All routes removed. Routing table is empty. Shutdown complete.... Кина не показывает. |
|
Текстовая версия | Сейчас: 26.9.2024, 8:14 |