Date: Tue, 05 Dec 2023 13:11:45 +0100 From: Kristof Provost <kp@FreeBSD.org> To: Benoit Chesneau <benoitc@enki-multimedia.eu> Cc: freebsd-net@freebsd.org Subject: Re: vxlan with IPv6 underlay ? Message-ID: <793EA8DF-BD26-414A-A12D-866356D339DB@FreeBSD.org> In-Reply-To: <bmkPdpqYkXzCqs5CYfBIZO6sXwmR1hU38pCr5cRlBeTxM4VIbzTj_A0YU6yFP2CbVxXHoOLeqHpdBY1reGJS_VvNBesk3J1HBWblpjijl2o=@enki-multimedia.eu> References: <bmkPdpqYkXzCqs5CYfBIZO6sXwmR1hU38pCr5cRlBeTxM4VIbzTj_A0YU6yFP2CbVxXHoOLeqHpdBY1reGJS_VvNBesk3J1HBWblpjijl2o=@enki-multimedia.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 Dec 2023, at 11:25, Benoit Chesneau wrote: > Hi, > > Is IPv6 underlay fully supported with FreebBSD ? I have created the a t= unnel and associated an Ipv6 address to each side. I'm able to ping betwe= en each devicesl. But when I want to curl from the remote side it timeout= =2E Locally on the remote side it is OK. Is this expected ? Should I rath= er create a bridge with vxlan as a member and bind nginx to it ? > > ``` > $ ifconfig vxlan0 create vxlanid 108 vxlanlocal AAAA:BBBB:110b:102::100= vxlanremote AAAA:BBBB:110b:102::12 > $ ifconfig vxlan0 > vxlan0: flags=3D1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP= > metric 0 mtu 1430 > options=3D80020<JUMBO_MTU,LINKSTATE> > ether 58:9c:fc:10:ff:eb > groups: vxlan > vxlan vni 108 local [AAAA:BBBB:102::100]:4789 remote [AAAA:BBBB:110b:10= 2::12]:4789 > media: Ethernet autoselect (autoselect <full-duplex>) > status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > $ ifconfig vxlan0 inet6 AAAA:BBBB:110b:300::1/64 > ```` > > Ping from remote is ok: > ``` > ifconfig vxlan0 > vxlan0: flags=3D1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP= > metric 0 mtu 1430 > options=3D680323<RXCSUM,TXCSUM,JUMBO_MTU,TSO4,TSO6,LINKSTATE,RXCSUM_IPV= 6,TXCSUM_IPV6> > ether 58:9c:fc:10:df:1f > inet6 fe80::5a9c:fcff:fe10:df1f%vxlan0 prefixlen 64 scopeid 0xf > inet6 AAAA:BBBB:110b:300::2 prefixlen 64 > groups: vxlan > vxlan vni 108 local [AAAA:BBBB110b:102::12]:4789 remote [AAAA:BBBB:110b= :102::100]:4789 > media: Ethernet autoselect (autoselect <full-duplex>) > status: active nd6 options=3D21<PERFORMNUD,AUTO_LINKLOCAL> > $ ping6 AAAA:BBBB:110b:300::1 > PING6(56=3D40+8+8 bytes) AAAA:BBBB:110b:300::2 --> AAAA:BBBB::110b:300:= :1 > 16 bytes from 2a0e:e701:110b:300::1, icmp_seq=3D0 hlim=3D64 time=3D0.07= 1 ms > 16 bytes from 2a0e:e701:110b:300::1, icmp_seq=3D1 hlim=3D64 time=3D0.07= 8 ms > 16 bytes from 2a0e:e701:110b:300::1, icmp_seq=3D2 hlim=3D64 time=3D0.07= 6 ms > 16 bytes from 2a0e:e701:110b:300::1, icmp_seq=3D3 hlim=3D64 time=3D0.10= 4 ms > 16 bytes from 2a0e:e701:110b:300::1, icmp_seq=3D4 hlim=3D64 time=3D0.07= 7 ms^C > ``` > > But when I run `curl -6 -v 'http://[AAAA:BBBB:110b:300::1]'` it timeout= =2E > That smells like an MTU issue. Make sure you=E2=80=99re not blocking ICMP= v6, and check with larger ping messages. Best regards, Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?793EA8DF-BD26-414A-A12D-866356D339DB>