Hello,
Anybody already test vxlan in version 5.9???? I reproduced
the same test with version 5.8 and everything is ok.
My lab is simple:
vxlan0 192.168.1.17 Machine1 em0 200.98.41.17 <-> em1
200.98.44.18 Machine2 vxlan0 192.168.1.19
I can see the packet vxlan arriving in destination but there
is not return. Both directions is the same thing. I do the same test, same
network with version 5.8 and is ok.
machine1
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
priority: 0
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff000000
em0:
flags=18b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,MPSAFE>
mtu 1500
lladdr 00:50:56:bb:59:64
priority: 0
groups: egress
media: Ethernet autoselect (1000baseT full-duplex,master)
status: active
inet 200.98.41.17 netmask 0xffffff00 broadcast 200.98.41.255
em1: flags=18802<BROADCAST,SIMPLEX,MULTICAST,MPSAFE> mtu 1500
lladdr 00:50:56:bb:43:9d
priority: 0
media: Ethernet autoselect (1000baseT full-duplex,master)
status: active
enc0: flags=0<>
priority: 0
groups: enc
status: active
vxlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr fe:e1:ba:d0:f0:53
priority: 0
groups: vxlan
media: Ethernet autoselect
status: active
tunnel: inet 200.98.41.17 -> 200.98.44.18 vnetid 1
inet 192.168.1.17 netmask 0xffffff00 broadcast 192.168.1.255
#
# pfctl -d
pfctl: pf not enabled
#
Machine2
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
priority: 0
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff000000
em0: flags=18802<BROADCAST,SIMPLEX,MULTICAST,MPSAFE> mtu 1500
lladdr 00:50:56:bb:67:e5
priority: 0
media: Ethernet autoselect (1000baseT full-duplex,master)
status: active
em1:
flags=18b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,MPSAFE>
mtu 1500
lladdr 00:50:56:bb:46:a7
priority: 0
groups: egress
media: Ethernet autoselect (1000baseT full-duplex,master)
status: active
inet 200.98.44.18 netmask 0xffffff80 broadcast 200.98.44.127
enc0: flags=0<>
priority: 0
groups: enc
status: active
vxlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr fe:e1:ba:d0:e6:c1
priority: 0
groups: vxlan
media: Ethernet autoselect
status: active
tunnel: inet 200.98.44.18 -> 200.98.41.17 vnetid 1
inet 192.168.1.19 netmask 0xffffff00 broadcast 192.168.1.255
# pfctl -d
pfctl: pf not enabled
#
TCPDUMP
Machine1
[email protected]'s password:
Last login: Fri Jan 15 01:45:45 2016 from 200.221.130.5
OpenBSD 5.9-beta (GENERIC.MP) #1540: Fri Jan 8 10:48:32 MST 2016
Welcome to OpenBSD: The proactively secure Unix-like operating system.
Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code. With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.
# tcpdump -ni em0 port 4789
tcpdump: listening on em0, link-type EN10MB
02:00:23.386424 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
02:00:25.274328 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
02:00:27.400703 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
02:00:29.245143 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
02:00:31.393324 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
02:00:54.806495 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
02:00:56.867895 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
02:00:58.799075 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
Machine2
# tcpdump -ni em1 port 4789
tcpdump: listening on em1, link-type EN10MB
20:58:20.043878 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
20:58:35.189082 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
20:58:37.362855 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
20:58:39.120386 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
20:59:46.034194 200.98.44.18.4789 > 200.98.41.17.4789: udp 50 [tos 0x10]
20:59:53.259481 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
20:59:55.435700 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
20:59:57.193269 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
20:59:59.341469 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
21:00:01.316119 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
21:00:23.383898 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
21:00:25.271820 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
21:00:27.398216 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
21:00:29.242664 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
21:00:31.390838 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]
Tks,
Lobo
---
Este email foi escaneado pelo Avast antivÃrus.
https://www.avast.com/antivirus
