| raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278394 --- Comment #18 from Gregory Neil Shapiro <gshapiro@FreeBSD.org> --- Verified: #23 ip_output (m=3Dm@entry=3D0xfffff80007e3e000, opt=3Dopt@entry=3D0x0, ro= =3D<optimized out>, flags=3Dflags@entry=3D0, imo=3D0x0, inp=3Dinp@entry=3D0x0) at ../../../netinet/ip_output.c:699 699 switch (ip_output_pfil(&m, ifp, flags, inp, dst, &fibnum, (kgdb) print *dst $6 =3D {sin_len =3D 16 '\020', sin_family =3D 2 '\002', sin_port =3D 0, sin= _addr =3D {s_addr =3D 4017795422}, sin_zero =3D "\000\000\000\000\000\000\000"} s_addr is 94.177.122.239, which is the vxlanremote IP for vxlan0. Checking BGP route map: 94.177.122.0/24 unicast [4IXP4RS1 18:24:23.600 from 185.1.125.1] * (10= 0) [AS58057i] via 185.1.125.5 on vxlan0 Once that route was exported to the kernel, routing to 94.177.122.239 went = out over vxlan0. Configuration wise, I can avoid the crash with a static route for 94.177.122.239/32 out of the default gateway instead of the tunnel. Howeve= r, would be good to fix the crash. Might even be interesting for all of the tunnel interfaces (not just vxlan)= to check if they are about to send a packet for the tunnel endpoint inside the tunnel and realize that won't work (e.g., if dst =3D=3D vxlanremote). Is t= hat what if_tunnel_check_nesting() does? --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>