Добрый день гуру! Помогите разобраться с этой же проблемой.
Клиент получает ип, но трафик ходит с перебоями. Все вышеперечисленное не помогло.
[ipoe]
username=lua:username
lua-file=/etc/accel-ppp.lua
lease-time=300
max-lease-time=300
attr-dhcp-client-ip=Framed-IP-Address
attr-dhcp-router-ip=DHCP-Router-IP-Address
attr-dhcp-mask=DHCP-Mask
attr-l4-redirect=L4-Redirect
shared=1
ifcfg=1
mode=L2
start=dhcpv4
proto=100
interface=re:eth2.100
ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:22:64:42:6b:e3 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:1b:21:57:58:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.2/24 brd 192.168.100.255 scope global eth1
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:1b:21:57:58:01 brd ff:ff:ff:ff:ff:ff
5: eth2.8@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:1b:21:57:58:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.90.18/24 brd 192.168.90.255 scope global eth2.8
6: eth2.100@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:1b:21:57:58:01 brd ff:ff:ff:ff:ff:ff
inet 10.1.100.1/24 brd 10.1.100.255 scope global eth2.100
7: eth2.107@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:1b:21:57:58:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.77.10/24 brd 192.168.77.255 scope global eth2.107
8: ifb0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc htb state UNKNOWN qlen 32
link/ether 22:89:db:db:94:69 brd ff:ff:ff:ff:ff:ff
9: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
link/ether 36:62:38:b4:d9:b2 brd ff:ff:ff:ff:ff:ff
11: ipoe0: <POINTOPOINT,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb state UNKNOWN qlen 100
link/ether 00:1b:21:57:58:01 peer ff:ff:ff:ff:ff:ff
inet 10.1.100.1 peer 10.1.100.2/32 scope global ipoe0
ip route show
default via 192.168.100.1 dev eth1
10.1.100.0/24 dev eth2.100 proto kernel scope link src 10.1.100.1
10.1.100.2 dev ipoe0 proto kernel scope link src 10.1.100.1
192.168.77.0/24 dev eth2.107 proto kernel scope link src 192.168.77.10
192.168.90.0/24 dev eth2.8 proto kernel scope link src 192.168.90.18
192.168.100.0/24 dev eth1 proto kernel scope link src 192.168.100.2
буду рад любой помощи.
Проблема с Ipoe
Re: Проблема с Ipoe
Неужели за три дня этот пост никто не видел... У меня скоро разовьется фобия пустого места.
Re: Проблема с Ipoe
а можно чуть подробнее о перебоях? Например периодичность, продолжительность и т.д.
Re: Проблема с Ipoe
ping от абонента на любой из ресурсов рунета проходит с потерями пакетов с произвольной периодичностью (может быть пять ответов и два потерянных пакетов, а может и на оборот), стабильной связи нет.
Re: Проблема с Ipoe
а если отключить шейпер проблема сохраняется?
Re: Проблема с Ipoe
AheroN, рекомендация из вики следовали, в частности "таблица arp"
http://accel-ppp.org/wiki/doku.php?id=r ... комендации
http://accel-ppp.org/wiki/doku.php?id=r ... комендации
Re: Проблема с Ipoe
Или arp переполняется, или conntrack.
И то, и другое к аццелю как бы отношения не имеет.
И то, и другое к аццелю как бы отношения не имеет.
Re: Проблема с Ipoe
Все было выполнено и проверено. Результата не дало. Попробую отключить шейпер и проверитьdimka88 wrote:AheroN, рекомендация из вики следовали, в частности "таблица arp"
http://accel-ppp.org/wiki/doku.php?id=r ... комендации
Re: Проблема с Ipoe
У меня была такая проблема именно в шейпере, с тех пор используем внешние скрипты tc. Из плюсов после отказа: нарезаем разные полосы на разные направления (интернет, пиринг, внутренние ресурсы, контент провайдеры); возможность использовать разные шейперы (hfsc, sfq, htb и т.д.)
Re: Проблема с Ipoe
Отключил шейпер, проблема остается та же...
вывод с клинского влана
root@Accel-IPoE-1:/etc# tcpdump -vvvv -i eth2.100
tcpdump: listening on eth2.100, link-type EN10MB (Ethernet), capture size 65535 bytes
11:12:12.009039 IP (tos 0x0, ttl 64, id 1775, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 867, length 40
11:12:12.030421 IP (tos 0x60, ttl 58, id 46969, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 867, length 40
11:12:13.007480 IP (tos 0x0, ttl 64, id 1776, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 868, length 40
11:12:13.031663 IP (tos 0x60, ttl 58, id 47148, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 868, length 40
11:12:14.005989 IP (tos 0x0, ttl 64, id 1777, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 869, length 40
11:12:14.027345 IP (tos 0x60, ttl 58, id 47316, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 869, length 40
11:12:15.020271 IP (tos 0x0, ttl 64, id 1778, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 870, length 40
11:12:15.041701 IP (tos 0x60, ttl 58, id 47373, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 870, length 40
11:12:15.987352 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.1.100.1 (00:1b:21:57:58:01 (oui DCBX)) tell 10.1.100.2, length 46
11:12:15.987362 ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.1.100.1 is-at 00:1b:21:57:58:01 (oui DCBX), length 28
11:12:16.018672 IP (tos 0x0, ttl 64, id 1779, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 871, length 40
11:12:16.040037 IP (tos 0x60, ttl 58, id 47438, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 871, length 40
11:12:17.017336 IP (tos 0x0, ttl 64, id 1780, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 872, length 40
11:12:17.038688 IP (tos 0x60, ttl 58, id 47512, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 872, length 40
11:12:17.815504 IP (tos 0x0, ttl 64, id 1781, offset 0, flags [none], proto UDP (17), length 71)
10.1.100.2.57036 > dns.yandex.ru.domain: [udp sum ok] 8894+ A? teredo.ipv6.microsoft.com. (43)
11:12:17.839590 IP (tos 0x60, ttl 57, id 63849, offset 0, flags [none], proto UDP (17), length 173)
dns.yandex.ru.domain > 10.1.100.2.57036: [udp sum ok] 8894 NXDomain q: A? teredo.ipv6.microsoft.com. 1/1/0 teredo.ipv6.microsoft.com. [21m1s] CNAME teredo.ipv6.microsoft.com.nsatc.net. ns: nsatc.net. [1m4s] SOA admin.nsatc.net. dns.level3.net. 1453844167 10800 2700 3600000 900 (145)
11:12:18.827178 IP (tos 0x0, ttl 64, id 1782, offset 0, flags [none], proto UDP (17), length 71)
10.1.100.2.57036 > dns.yandex.ru.domain: [udp sum ok] 8894+ A? teredo.ipv6.microsoft.com. (43)
11:12:18.851034 IP (tos 0x60, ttl 57, id 63985, offset 0, flags [none], proto UDP (17), length 173)
dns.yandex.ru.domain > 10.1.100.2.57036: [udp sum ok] 8894 NXDomain q: A? teredo.ipv6.microsoft.com. 1/1/0 teredo.ipv6.microsoft.com. [21m] CNAME teredo.ipv6.microsoft.com.nsatc.net. ns: nsatc.net. [1m3s] SOA admin.nsatc.net. dns.level3.net. 1453844167 10800 2700 3600000 900 (145)
11:12:19.841417 IP (tos 0x0, ttl 64, id 1783, offset 0, flags [none], proto UDP (17), length 71)
10.1.100.2.57036 > dns.yandex.ru.domain: [udp sum ok] 8894+ A? teredo.ipv6.microsoft.com. (43)
11:12:19.865195 IP (tos 0x60, ttl 57, id 64018, offset 0, flags [none], proto UDP (17), length 173)
dns.yandex.ru.domain > 10.1.100.2.57036: [udp sum ok] 8894 NXDomain q: A? teredo.ipv6.microsoft.com. 1/1/0 teredo.ipv6.microsoft.com. [20m59s] CNAME teredo.ipv6.microsoft.com.nsatc.net. ns: nsatc.net. [1m2s] SOA admin.nsatc.net. dns.level3.net. 1453844167 10800 2700 3600000 900 (145)
11:12:21.853952 IP (tos 0x0, ttl 64, id 1784, offset 0, flags [none], proto UDP (17), length 71)
10.1.100.2.57036 > dns.yandex.ru.domain: [udp sum ok] 8894+ A? teredo.ipv6.microsoft.com. (43)
11:12:21.877654 IP (tos 0x60, ttl 57, id 64227, offset 0, flags [none], proto UDP (17), length 173)
dns.yandex.ru.domain > 10.1.100.2.57036: [udp sum ok] 8894 NXDomain q: A? teredo.ipv6.microsoft.com. 1/1/0 teredo.ipv6.microsoft.com. [20m57s] CNAME teredo.ipv6.microsoft.com.nsatc.net. ns: nsatc.net. [1m] SOA admin.nsatc.net. dns.level3.net. 1453844167 10800 2700 3600000 900 (145)
11:12:21.994660 IP (tos 0x0, ttl 64, id 1785, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 873, length 40
11:12:22.016008 IP (tos 0x60, ttl 58, id 48174, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 873, length 40
вывод с клинского влана
root@Accel-IPoE-1:/etc# tcpdump -vvvv -i eth2.100
tcpdump: listening on eth2.100, link-type EN10MB (Ethernet), capture size 65535 bytes
11:12:12.009039 IP (tos 0x0, ttl 64, id 1775, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 867, length 40
11:12:12.030421 IP (tos 0x60, ttl 58, id 46969, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 867, length 40
11:12:13.007480 IP (tos 0x0, ttl 64, id 1776, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 868, length 40
11:12:13.031663 IP (tos 0x60, ttl 58, id 47148, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 868, length 40
11:12:14.005989 IP (tos 0x0, ttl 64, id 1777, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 869, length 40
11:12:14.027345 IP (tos 0x60, ttl 58, id 47316, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 869, length 40
11:12:15.020271 IP (tos 0x0, ttl 64, id 1778, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 870, length 40
11:12:15.041701 IP (tos 0x60, ttl 58, id 47373, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 870, length 40
11:12:15.987352 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.1.100.1 (00:1b:21:57:58:01 (oui DCBX)) tell 10.1.100.2, length 46
11:12:15.987362 ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.1.100.1 is-at 00:1b:21:57:58:01 (oui DCBX), length 28
11:12:16.018672 IP (tos 0x0, ttl 64, id 1779, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 871, length 40
11:12:16.040037 IP (tos 0x60, ttl 58, id 47438, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 871, length 40
11:12:17.017336 IP (tos 0x0, ttl 64, id 1780, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 872, length 40
11:12:17.038688 IP (tos 0x60, ttl 58, id 47512, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 872, length 40
11:12:17.815504 IP (tos 0x0, ttl 64, id 1781, offset 0, flags [none], proto UDP (17), length 71)
10.1.100.2.57036 > dns.yandex.ru.domain: [udp sum ok] 8894+ A? teredo.ipv6.microsoft.com. (43)
11:12:17.839590 IP (tos 0x60, ttl 57, id 63849, offset 0, flags [none], proto UDP (17), length 173)
dns.yandex.ru.domain > 10.1.100.2.57036: [udp sum ok] 8894 NXDomain q: A? teredo.ipv6.microsoft.com. 1/1/0 teredo.ipv6.microsoft.com. [21m1s] CNAME teredo.ipv6.microsoft.com.nsatc.net. ns: nsatc.net. [1m4s] SOA admin.nsatc.net. dns.level3.net. 1453844167 10800 2700 3600000 900 (145)
11:12:18.827178 IP (tos 0x0, ttl 64, id 1782, offset 0, flags [none], proto UDP (17), length 71)
10.1.100.2.57036 > dns.yandex.ru.domain: [udp sum ok] 8894+ A? teredo.ipv6.microsoft.com. (43)
11:12:18.851034 IP (tos 0x60, ttl 57, id 63985, offset 0, flags [none], proto UDP (17), length 173)
dns.yandex.ru.domain > 10.1.100.2.57036: [udp sum ok] 8894 NXDomain q: A? teredo.ipv6.microsoft.com. 1/1/0 teredo.ipv6.microsoft.com. [21m] CNAME teredo.ipv6.microsoft.com.nsatc.net. ns: nsatc.net. [1m3s] SOA admin.nsatc.net. dns.level3.net. 1453844167 10800 2700 3600000 900 (145)
11:12:19.841417 IP (tos 0x0, ttl 64, id 1783, offset 0, flags [none], proto UDP (17), length 71)
10.1.100.2.57036 > dns.yandex.ru.domain: [udp sum ok] 8894+ A? teredo.ipv6.microsoft.com. (43)
11:12:19.865195 IP (tos 0x60, ttl 57, id 64018, offset 0, flags [none], proto UDP (17), length 173)
dns.yandex.ru.domain > 10.1.100.2.57036: [udp sum ok] 8894 NXDomain q: A? teredo.ipv6.microsoft.com. 1/1/0 teredo.ipv6.microsoft.com. [20m59s] CNAME teredo.ipv6.microsoft.com.nsatc.net. ns: nsatc.net. [1m2s] SOA admin.nsatc.net. dns.level3.net. 1453844167 10800 2700 3600000 900 (145)
11:12:21.853952 IP (tos 0x0, ttl 64, id 1784, offset 0, flags [none], proto UDP (17), length 71)
10.1.100.2.57036 > dns.yandex.ru.domain: [udp sum ok] 8894+ A? teredo.ipv6.microsoft.com. (43)
11:12:21.877654 IP (tos 0x60, ttl 57, id 64227, offset 0, flags [none], proto UDP (17), length 173)
dns.yandex.ru.domain > 10.1.100.2.57036: [udp sum ok] 8894 NXDomain q: A? teredo.ipv6.microsoft.com. 1/1/0 teredo.ipv6.microsoft.com. [20m57s] CNAME teredo.ipv6.microsoft.com.nsatc.net. ns: nsatc.net. [1m] SOA admin.nsatc.net. dns.level3.net. 1453844167 10800 2700 3600000 900 (145)
11:12:21.994660 IP (tos 0x0, ttl 64, id 1785, offset 0, flags [none], proto ICMP (1), length 60)
10.1.100.2 > dns.yandex.ru: ICMP echo request, id 1, seq 873, length 40
11:12:22.016008 IP (tos 0x60, ttl 58, id 48174, offset 0, flags [none], proto ICMP (1), length 60)
dns.yandex.ru > 10.1.100.2: ICMP echo reply, id 1, seq 873, length 40