OpenVZ Forum


Home » International » Russian » Описание capability option
Re: Описание capability option [message #5385 is a reply to message #5379] Fri, 18 August 2006 11:23 Go to previous messageGo to previous message
Anonymous Coward
Andrey Mirkin wrote on Fri, 18 August 2006 13:34

Quote:


Что стоит в:
[ve0]# /proc/sys/net/ipv4/conf/*/rp_filter



Эти параметры надо было проверить в ве0.


Стоит правильно и там - в 1
Quote:


На бридже, на veth и eth0 в ве0 надо попробовать поставить rp_filter в 0

Поставил. С первым VE102 все нормально. Все работает.
А VE106 не видит шлюз. Настройки для VE102 и VE106 одинаковые.
[root@serv ~]# vzctl exec 102 ip a
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: venet0: <BROADCAST,POINTOPOINT,NOARP> mtu 1500 qdisc noop
    link/void
5: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:12:34:56:78:9b brd ff:ff:ff:ff:ff:ff
    inet 10.10.106.2/24 brd 10.10.106.255 scope global eth0
    inet6 fe80::212:34ff:fe56:789b/64 scope link
       valid_lft forever preferred_lft forever
[root@serv ~]# vzctl exec 102 ip r
10.10.106.0/24 dev eth0  proto kernel  scope link  src 10.10.106.2
default dev eth0  scope link
[root@serv ~]# vzctl exec 106 ip a
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: venet0: <BROADCAST,POINTOPOINT,NOARP> mtu 1500 qdisc noop
    link/void
5: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:16:34:56:78:9b brd ff:ff:ff:ff:ff:ff
    inet 10.10.106.6/24 brd 10.10.106.255 scope global eth0
    inet6 fe80::216:34ff:fe56:789b/64 scope link
       valid_lft forever preferred_lft forever
[root@serv ~]# vzctl exec 106 ip r
10.10.106.0/24 dev eth0  proto kernel  scope link  src 10.10.106.6
default dev eth0  scope link


С VE0 10.10.106.6 - пингуется
[root@serv ~]# vzctl exec 102 ping 10.10.106.1
PING 10.10.106.1 (10.10.106.1) 56(84) bytes of data.
64 bytes from 10.10.106.1: icmp_seq=1 ttl=64 time=0.049 ms
64 bytes from 10.10.106.1: icmp_seq=2 ttl=64 time=0.015 ms

[root@serv ~]# vzctl exec 102 ping 10.10.106.3
PING 10.10.106.3 (10.10.106.3) 56(84) bytes of data.
64 bytes from 10.10.106.3: icmp_seq=1 ttl=64 time=0.072 ms
64 bytes from 10.10.106.3: icmp_seq=2 ttl=64 time=0.019 ms

[root@serv ~]# vzctl exec 102 ping 10.10.106.35
PING 10.10.106.35 (10.10.106.35) 56(84) bytes of data.
64 bytes from 10.10.106.35: icmp_seq=1 ttl=63 time=0.144 ms
64 bytes from 10.10.106.35: icmp_seq=2 ttl=63 time=0.109 ms
64 bytes from 10.10.106.35: icmp_seq=3 ttl=63 time=0.118 ms

[root@serv ~]# vzctl exec 102 ping 10.10.106.6
PING 10.10.106.6 (10.10.106.6) 56(84) bytes of data.
From 10.10.106.2 icmp_seq=2 Destination Host Unreachable
From 10.10.106.2 icmp_seq=3 Destination Host Unreachable
From 10.10.106.2 icmp_seq=4 Destination Host Unreachable

[root@serv ~]# vzctl exec 106 ping 10.10.106.6
PING 10.10.106.6 (10.10.106.6) 56(84) bytes of data.
64 bytes from 10.10.106.6: icmp_seq=1 ttl=64 time=0.034 ms
64 bytes from 10.10.106.6: icmp_seq=2 ttl=64 time=0.008 ms

[root@serv ~]# vzctl exec 106 ping 10.10.106.1
PING 10.10.106.1 (10.10.106.1) 56(84) bytes of data.
64 bytes from 10.10.106.1: icmp_seq=1 ttl=64 time=0.054 ms
64 bytes from 10.10.106.1: icmp_seq=2 ttl=64 time=0.023 ms

[root@serv ~]# vzctl exec 106 ping 10.10.106.3
PING 10.10.106.3 (10.10.106.3) 56(84) bytes of data.
64 bytes from 10.10.106.3: icmp_seq=1 ttl=64 time=0.058 ms
64 bytes from 10.10.106.3: icmp_seq=2 ttl=64 time=0.020 ms

[root@serv ~]# vzctl exec 106 ping 10.10.106.35
PING 10.10.106.35 (10.10.106.35) 56(84) bytes of data.
From 10.10.106.6 icmp_seq=2 Destination Host Unreachable
From 10.10.106.6 icmp_seq=3 Destination Host Unreachable

Ну и со шлюза:
[root@admin ~]# ping 10.10.106.1
PING 10.10.106.1 (10.10.106.1) 56(84) bytes of data.
64 bytes from 10.10.106.1: icmp_seq=1 ttl=64 time=0.262 ms
64 bytes from 10.10.106.1: icmp_seq=2 ttl=64 time=0.107 ms

[root@admin ~]# ping 10.10.106.2
PING 10.10.106.2 (10.10.106.2) 56(84) bytes of data.
From 10.10.106.1: icmp_seq=1 Redirect Host(New nexthop: 10.10.106.2)
64 bytes from 10.10.106.2: icmp_seq=1 ttl=64 time=0.140 ms
From 10.10.106.1: icmp_seq=2 Redirect Host(New nexthop: 10.10.106.2)
64 bytes from 10.10.106.2: icmp_seq=2 ttl=64 time=0.124 ms

[root@admin ~]# ping 10.10.106.6
PING 10.10.106.6 (10.10.106.6) 56(84) bytes of data.

--- 10.10.106.6 ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 6999ms

[root@admin ~]# ping 10.10.106.3
PING 10.10.106.3 (10.10.106.3) 56(84) bytes of data.
64 bytes from 10.10.106.3: icmp_seq=1 ttl=64 time=592 ms
64 bytes from 10.10.106.3: icmp_seq=2 ttl=64 time=0.114 ms
64 bytes from 10.10.106.3: icmp_seq=3 ttl=64 time=0.113 ms


Т.е. получается что пакеты со второго veth не проходят в бридже.
Даже не знаю что и делать... Crying or Very Sad
Может надо как-то NAT делать?
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Проблема с сетевым стеком под нагрузкой.
Next Topic: Функциональность OpenVZ
Goto Forum:
  


Current Time: Wed Nov 06 12:19:03 GMT 2024

Total time taken to generate the page: 0.03421 seconds