* Bug and configuration MPLS error? [not found] <61671493137651@web14o.yandex.ru> @ 2017-04-25 17:28 ` Алексей Болдырев 2017-04-26 2:22 ` David Ahern 0 siblings, 1 reply; 4+ messages in thread From: Алексей Болдырев @ 2017-04-25 17:28 UTC (permalink / raw) To: netdev Короче, вот конфиг MPLS на одном из дистрибутивов: In short, here's the MPLS configuration on one of the distributions: 226 sysctl -w net.mpls.conf.lo.input=1 227 sysctl -w net.mpls.platform_labels=1048575 228 ip link add veth0 type veth peer name veth1 229 ip link add veth2 type veth peer name veth3 230 sysctl -w net.mpls.conf.veth0.input=1 231 sysctl -w net.mpls.conf.veth2.input=1 232 ifconfig veth0 10.3.3.1 netmask 255.255.255.0 233 ifconfig veth2 10.4.4.1 netmask 255.255.255.0 234 ip netns add host1 235 ip netns add host2 236 ip link set veth1 netns host1 237 ip link set veth3 netns host2 238 ip netns exec host1 ifconfig veth1 10.3.3.2 netmask 255.255.255.0 up 239 ip netns exec host2 ifconfig veth3 10.4.4.2 netmask 255.255.255.0 up 240 ip netns exec host1 ip route add 10.10.10.2/32 encap mpls 112 via inet 10.3.3.1 241 ip netns exec host2 ip route add 10.10.10.1/32 encap mpls 111 via inet 10.4.4.1 242 ip -f mpls route add 111 via inet 10.3.3.2 243 ip -f mpls route add 112 via inet 10.4.4.2 Результаты теста: Test Results: tcp по mpls: ~ # ip netns exec host2 iperf3 -c 10.10.10.1 -B 10.10.10.2 Connecting to host 10.10.10.1, port 5201 [ 4] local 10.10.10.2 port 34021 connected to 10.10.10.1 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 912 KBytes 7.46 Mbits/sec 0 636 KBytes [ 4] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 0 636 KBytes [ 4] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 0 636 KBytes [ 4] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 0 636 KBytes [ 4] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec 0 636 KBytes [ 4] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec 0 636 KBytes [ 4] 6.00-7.00 sec 0.00 Bytes 0.00 bits/sec 0 636 KBytes [ 4] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec 0 636 KBytes [ 4] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec 0 636 KBytes [ 4] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec 0 636 KBytes ---------------------------------------- [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 912 KBytes 747 Kbits/sec 0 sender [ 4] 0.00-10.00 sec 21.3 KBytes 17.5 Kbits/sec receiver iperf Done. ~ # udp по mpls: ~ # ip netns exec host2 iperf3 -c 10.10.10.1 -B 10.10.10.2 -u -b 10g Connecting to host 10.10.10.1, port 5201 [ 4] local 10.10.10.2 port 56901 connected to 10.10.10.1 port 5201 [ ID] Interval Transfer Bandwidth Total Datagrams [ 4] 0.00-1.00 sec 438 MBytes 3.67 Gbits/sec 56049 [ 4] 1.00-2.00 sec 491 MBytes 4.12 Gbits/sec 62829 [ 4] 2.00-3.00 sec 492 MBytes 4.12 Gbits/sec 62919 [ 4] 3.00-4.00 sec 490 MBytes 4.11 Gbits/sec 62762 [ 4] 4.00-5.00 sec 491 MBytes 4.12 Gbits/sec 62891 [ 4] 5.00-6.00 sec 492 MBytes 4.13 Gbits/sec 62994 [ 4] 6.00-7.00 sec 503 MBytes 4.22 Gbits/sec 64322 [ 4] 7.00-8.00 sec 503 MBytes 4.22 Gbits/sec 64321 [ 4] 8.00-9.00 sec 502 MBytes 4.21 Gbits/sec 64279 [ 4] 9.00-10.00 sec 511 MBytes 4.28 Gbits/sec 65352 ---------------------------------------- [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 4] 0.00-10.00 sec 4.80 GBytes 4.12 Gbits/sec 0.001 ms 0/628718 (0%) [ 4] Sent 628718 datagrams iperf Done. UDP как видим, проходит нормально. UDP as seen, is normal. Вот параметры интерфейсов: Here are the interface parameters: P: veth0 Link encap:Ethernet HWaddr 72:0D:9E:D7:BC:B3 inet addr:10.3.3.1 Bcast:10.3.3.255 Mask:255.255.255.0 inet6 addr: fe80::700d:9eff:fed7:bcb3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:65535 Metric:1 RX packets:126 errors:0 dropped:0 overruns:0 frame:0 TX packets:629026 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9592 (9.3 KiB) TX bytes:5178498619 (4.8 GiB) veth2 Link encap:Ethernet HWaddr CE:24:F8:1F:99:C1 inet addr:10.4.4.1 Bcast:10.4.4.255 Mask:255.255.255.0 inet6 addr: fe80::cc24:f8ff:fe1f:99c1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:65535 Metric:1 RX packets:629015 errors:0 dropped:0 overruns:0 frame:0 TX packets:135 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5181014123 (4.8 GiB) TX bytes:9564 (9.3 KiB) PE1: ~ # ip netns exec host2 ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) veth3 Link encap:Ethernet HWaddr 36:00:C2:29:0D:F9 inet addr:10.4.4.2 Bcast:10.4.4.255 Mask:255.255.255.0 inet6 addr: fe80::3400:c2ff:fe29:df9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:65200 Metric:1 RX packets:136 errors:0 dropped:0 overruns:0 frame:0 TX packets:629015 errors:0 dropped:1 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9596 (9.3 KiB) TX bytes:5181014123 (4.8 GiB) PE2: lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) veth1 Link encap:Ethernet HWaddr DA:B2:AD:31:68:77 inet addr:10.3.3.2 Bcast:10.3.3.255 Mask:255.255.255.0 inet6 addr: fe80::d8b2:adff:fe31:6877/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:65200 Metric:1 RX packets:629027 errors:0 dropped:0 overruns:0 frame:0 TX packets:126 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5178498651 (4.8 GiB) TX bytes:9592 (9.3 KiB) Тоже самое, только на более свежом ядре: http://forum.nag.ru/forum/index.php?showtopic=128927&st=0 The same thing, only on amore recent nucleus: Ядро: Core: / # uname -r 4.8.6 Конфиг ядра: Kernel Config: https://pastebin.com/raw/EE1k05cT Это баг ядра, или ошибка конфигурирования? Is it a kernel bug, or a configuration error? ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug and configuration MPLS error? 2017-04-25 17:28 ` Bug and configuration MPLS error? Алексей Болдырев @ 2017-04-26 2:22 ` David Ahern 2017-04-26 12:40 ` Алексей Болдырев 0 siblings, 1 reply; 4+ messages in thread From: David Ahern @ 2017-04-26 2:22 UTC (permalink / raw) To: Алексей Болдырев, netdev On 4/25/17 11:28 AM, Алексей Болдырев wrote: > 226 sysctl -w net.mpls.conf.lo.input=1 > 227 sysctl -w net.mpls.platform_labels=1048575 > 228 ip link add veth0 type veth peer name veth1 > 229 ip link add veth2 type veth peer name veth3 > 230 sysctl -w net.mpls.conf.veth0.input=1 > 231 sysctl -w net.mpls.conf.veth2.input=1 > 232 ifconfig veth0 10.3.3.1 netmask 255.255.255.0 > 233 ifconfig veth2 10.4.4.1 netmask 255.255.255.0 > 234 ip netns add host1 > 235 ip netns add host2 > 236 ip link set veth1 netns host1 > 237 ip link set veth3 netns host2 > 238 ip netns exec host1 ifconfig veth1 10.3.3.2 netmask 255.255.255.0 up > 239 ip netns exec host2 ifconfig veth3 10.4.4.2 netmask 255.255.255.0 up > 240 ip netns exec host1 ip route add 10.10.10.2/32 encap mpls 112 via inet 10.3.3.1 > 241 ip netns exec host2 ip route add 10.10.10.1/32 encap mpls 111 via inet 10.4.4.1 > 242 ip -f mpls route add 111 via inet 10.3.3.2 > 243 ip -f mpls route add 112 via inet 10.4.4.2 your setup is incomplete. # ip netns exec host2 ping 10.10.10.1 PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data. ^C --- 10.10.10.1 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1038ms If you run tcpdump on veth1 in host1 you see the packets come in but no response: # ip netns exec host1 tcpdump -n -i veth1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on veth1, link-type EN10MB (Ethernet), capture size 262144 bytes 19:20:24.599529 IP6 fe80::347d:e3ff:fe93:944b > ff02::2: ICMP6, router solicitation, length 16 19:20:27.413901 IP 10.4.4.2 > 10.10.10.1: ICMP echo request, id 978, seq 1, length 64 19:20:28.439574 IP 10.4.4.2 > 10.10.10.1: ICMP echo request, id 978, seq 2, length 64 and the lack of response is b/c: 1. host1 has no address for 10.10.10.1 and 2. even if it did, there is no return route to 10.4.4.2: # ip -netns host1 ro ls 10.3.3.0/24 dev veth1 proto kernel scope link src 10.3.3.2 10.10.10.2 encap mpls 112 via 10.3.3.1 dev veth1 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug and configuration MPLS error? 2017-04-26 2:22 ` David Ahern @ 2017-04-26 12:40 ` Алексей Болдырев 2017-04-26 18:18 ` David Ahern 0 siblings, 1 reply; 4+ messages in thread From: Алексей Болдырев @ 2017-04-26 12:40 UTC (permalink / raw) To: David Ahern, netdev 26.04.2017, 05:23, "David Ahern" <dsahern@gmail.com>: > On 4/25/17 11:28 AM, Алексей Болдырев wrote: >> 226 sysctl -w net.mpls.conf.lo.input=1 >> 227 sysctl -w net.mpls.platform_labels=1048575 >> 228 ip link add veth0 type veth peer name veth1 >> 229 ip link add veth2 type veth peer name veth3 >> 230 sysctl -w net.mpls.conf.veth0.input=1 >> 231 sysctl -w net.mpls.conf.veth2.input=1 >> 232 ifconfig veth0 10.3.3.1 netmask 255.255.255.0 >> 233 ifconfig veth2 10.4.4.1 netmask 255.255.255.0 >> 234 ip netns add host1 >> 235 ip netns add host2 >> 236 ip link set veth1 netns host1 >> 237 ip link set veth3 netns host2 >> 238 ip netns exec host1 ifconfig veth1 10.3.3.2 netmask 255.255.255.0 up >> 239 ip netns exec host2 ifconfig veth3 10.4.4.2 netmask 255.255.255.0 up >> 240 ip netns exec host1 ip route add 10.10.10.2/32 encap mpls 112 via inet 10.3.3.1 >> 241 ip netns exec host2 ip route add 10.10.10.1/32 encap mpls 111 via inet 10.4.4.1 >> 242 ip -f mpls route add 111 via inet 10.3.3.2 >> 243 ip -f mpls route add 112 via inet 10.4.4.2 > > your setup is incomplete. > > # ip netns exec host2 ping 10.10.10.1 > PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data. > ^C > --- 10.10.10.1 ping statistics --- > 2 packets transmitted, 0 received, 100% packet loss, time 1038ms > > If you run tcpdump on veth1 in host1 you see the packets come in but no > response: > > # ip netns exec host1 tcpdump -n -i veth1 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on veth1, link-type EN10MB (Ethernet), capture size 262144 bytes > 19:20:24.599529 IP6 fe80::347d:e3ff:fe93:944b > ff02::2: ICMP6, router > solicitation, length 16 > 19:20:27.413901 IP 10.4.4.2 > 10.10.10.1: ICMP echo request, id 978, seq > 1, length 64 > 19:20:28.439574 IP 10.4.4.2 > 10.10.10.1: ICMP echo request, id 978, seq > 2, length 64 > > and the lack of response is b/c: > 1. host1 has no address for 10.10.10.1 and > 2. even if it did, there is no return route to 10.4.4.2: > > # ip -netns host1 ro ls > 10.3.3.0/24 dev veth1 proto kernel scope link src 10.3.3.2 > 10.10.10.2 encap mpls 112 via 10.3.3.1 dev veth1 As for ping, you need to enter this: Ip netns exec host2 ping 10.10.10.1 -A 10.10.10.2 Here I published the results of testing on new (>4.9) cores. (in Russian): http://forum.nag.ru/forum/index.php?s=d09f0e5186fda59b3099eb81ad07ee63&showtopic=128927 But on the old kernels: http://forum.nag.ru/forum/index.php?showtopic=128927&view=findpost&p=1396067 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug and configuration MPLS error? 2017-04-26 12:40 ` Алексей Болдырев @ 2017-04-26 18:18 ` David Ahern 0 siblings, 0 replies; 4+ messages in thread From: David Ahern @ 2017-04-26 18:18 UTC (permalink / raw) To: Алексей Болдырев, netdev On 4/26/17 6:40 AM, Алексей Болдырев wrote: > > > 26.04.2017, 05:23, "David Ahern" <dsahern@gmail.com>: >> On 4/25/17 11:28 AM, Алексей Болдырев wrote: >>> 226 sysctl -w net.mpls.conf.lo.input=1 >>> 227 sysctl -w net.mpls.platform_labels=1048575 >>> 228 ip link add veth0 type veth peer name veth1 >>> 229 ip link add veth2 type veth peer name veth3 >>> 230 sysctl -w net.mpls.conf.veth0.input=1 >>> 231 sysctl -w net.mpls.conf.veth2.input=1 >>> 232 ifconfig veth0 10.3.3.1 netmask 255.255.255.0 >>> 233 ifconfig veth2 10.4.4.1 netmask 255.255.255.0 >>> 234 ip netns add host1 >>> 235 ip netns add host2 >>> 236 ip link set veth1 netns host1 >>> 237 ip link set veth3 netns host2 >>> 238 ip netns exec host1 ifconfig veth1 10.3.3.2 netmask 255.255.255.0 up >>> 239 ip netns exec host2 ifconfig veth3 10.4.4.2 netmask 255.255.255.0 up >>> 240 ip netns exec host1 ip route add 10.10.10.2/32 encap mpls 112 via inet 10.3.3.1 >>> 241 ip netns exec host2 ip route add 10.10.10.1/32 encap mpls 111 via inet 10.4.4.1 >>> 242 ip -f mpls route add 111 via inet 10.3.3.2 >>> 243 ip -f mpls route add 112 via inet 10.4.4.2 >> >> your setup is incomplete. >> >> # ip netns exec host2 ping 10.10.10.1 >> PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data. >> ^C >> --- 10.10.10.1 ping statistics --- >> 2 packets transmitted, 0 received, 100% packet loss, time 1038ms >> >> If you run tcpdump on veth1 in host1 you see the packets come in but no >> response: >> >> # ip netns exec host1 tcpdump -n -i veth1 >> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode >> listening on veth1, link-type EN10MB (Ethernet), capture size 262144 bytes >> 19:20:24.599529 IP6 fe80::347d:e3ff:fe93:944b > ff02::2: ICMP6, router >> solicitation, length 16 >> 19:20:27.413901 IP 10.4.4.2 > 10.10.10.1: ICMP echo request, id 978, seq >> 1, length 64 >> 19:20:28.439574 IP 10.4.4.2 > 10.10.10.1: ICMP echo request, id 978, seq >> 2, length 64 >> >> and the lack of response is b/c: >> 1. host1 has no address for 10.10.10.1 and >> 2. even if it did, there is no return route to 10.4.4.2: >> >> # ip -netns host1 ro ls >> 10.3.3.0/24 dev veth1 proto kernel scope link src 10.3.3.2 >> 10.10.10.2 encap mpls 112 via 10.3.3.1 dev veth1 > > As for ping, you need to enter this: > Ip netns exec host2 ping 10.10.10.1 -A 10.10.10.2 > Here I published the results of testing on new (>4.9) cores. (in Russian): > http://forum.nag.ru/forum/index.php?s=d09f0e5186fda59b3099eb81ad07ee63&showtopic=128927 > But on the old kernels: > http://forum.nag.ru/forum/index.php?showtopic=128927&view=findpost&p=1396067 > host1 does not have 10.10.10.1 as a local address. host2 does not have 10.10.10.2 as a local address. Given that, host1 has no business replying to a ping destined to 10.10.10.1, and host2 will not use 10.10.10.2 as a source address. I don't have time right now to build and test on older kernels, but based on the network config I do not see how it can work. If you add: ip -netns host1 addr add dev lo 10.10.10.1/32 ip -netns host2 addr add dev lo 10.10.10.2/32 Then it works. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-04-26 18:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <61671493137651@web14o.yandex.ru>
2017-04-25 17:28 ` Bug and configuration MPLS error? Алексей Болдырев
2017-04-26 2:22 ` David Ahern
2017-04-26 12:40 ` Алексей Болдырев
2017-04-26 18:18 ` David Ahern
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.