Re: 7.5: Fatal errors from eigrpd

This is most probably fallout from the imsg / ibuf API changes done
in 7.5. I need to setup a test system to see if I can figure out what goes
wrong.

On Mon, Apr 08, 2024 at 08:15:52PM +0200, Mark Leonard wrote:
> (Gah! Here's the post again in plaintext. Apologies.)
>
> Hello all,
>
> I'm running eigrpd in a VMWare environment and after upgrading to 7.5 from
> 7.4 I'm noticing eigrpd is failing with a couple different errors. In 7.4
> and prior I never had any problems.
>
> I tried to include everything that I thought might be relevant but if
> there's any other information I can provide please let me know.
>
> Has anyone else come across anything similar?
>
> Thanks,
> Mark
>
>
>
> examples:
>
> test1# eigrpd -dv
> startup
> eigrp_if_start: lo1 as 1 family ipv4
> eigrp_if_start: em0 as 1 family ipv4
> if_join_ipv4_group: interface em0 addr 224.0.0.10
> rt_new: prefix aa.bb.cc.1/32
> route_new: prefix aa.bb.cc.1/32 via connected distance (28160/0)
> rt_new: prefix 198.18.101.0/24
> route_new: prefix 198.18.101.0/24 via connected distance (28160/0)
> fatal in eigrpe: send_packet: get hdr failed
> rt_del: prefix aa.bb.cc.1/32
> route_del: prefix aa.bb.cc.1/32 via connected
> rt_del: prefix 198.18.101.0/24
> route_del: prefix 198.18.101.0/24 via connected
> route decision engine exiting
> kernel routing table decoupled
> waiting for children to terminate
> terminating
>
> and
>
> RouterTest# eigrpd -dv
> startup
> eigrp_if_start: em1 as 1 family ipv4
> if_join_ipv4_group: interface em1 addr 224.0.0.10
> rt_new: prefix 198.18.101.0/24
> route_new: prefix 198.18.101.0/24 via connected distance (28160/0)
> rt_del: prefix 198.18.101.0/24
> route_del: prefix 198.18.101.0/24 via connected
> route decision engine exiting
> kernel routing table decoupled
> waiting for children to terminate
> eigrp engine terminated; signal 11
> terminating
>
>
> This is happening on two of two upgraded VMs.
>
> SHA256 (/usr/sbin/eigrpd) =
> 3b85d7ac155afe4edd355f8b1d8c81f77c6254d96410af8b22f4018b756282a6
> (just in case)
>
> I've tried with net.inet.tcp.tso=0 and net.inet.tcp.tso=1. Same result.
>
> test1# uname -a
> OpenBSD test1.local 7.5 GENERIC.MP#82 amd64
>
> The configs I'm running are pretty basic:
>
> RouterTest# eigrpd -n
> configuration OK
> RouterTest# eigrpd -nv
>
>
> router-id 198.18.101.1
> fib-update yes
> rdomain 0
> fib-priority-internal 28
> fib-priority-external 28
> fib-priority-summary 28
>
>
> address-family ipv4 {
> autonomous-system 1 {
> k-values 1 0 1 0 0 0
> active-timeout 3
> maximum-hops 100
> maximum-paths 4
> variance 8
> default-metric 100000 10 255 1 1500
>
>
> interface em1 {
> hello-interval 5
> holdtime 15
> delay 10
> bandwidth 100000
> split-horizon yes
> }
> }
> }
>
>
> address-family ipv6 {
>
> }

--
:wq Claudio