ZEBRA: ifam_read() doesn't read all socket data (on FreeBSD)

[ocochard]

Testing FRR 4.0 on FreeBSD, and lot's of (cosmetic only?) warning/error messages during checkup config or startup:

[root@router1]~# zebra -C /usr/local/etc/frr/zebra.conf
2018/03/14 15:40:33 warnings: ZEBRA: ifam_read() doesn't read all socket data
2018/03/14 15:40:33 errors: ZEBRA: if_ioctl(SIOCGIFMEDIA) failed: Invalid argument
2018/03/14 15:40:33 warnings: ZEBRA: ifam_read() doesn't read all socket data
2018/03/14 15:40:33 errors: ZEBRA: if_ioctl(SIOCGIFMEDIA) failed: Invalid argument
2018/03/14 15:40:33 warnings: ZEBRA: ifam_read() doesn't read all socket data
2018/03/14 15:40:33 errors: ZEBRA: if_ioctl(SIOCGIFMEDIA) failed: Invalid argument
2018/03/14 15:40:33 warnings: ZEBRA: Disabling MPLS support (no kernel support)
2018/03/14 15:40:33 errors: ZEBRA: if_ioctl(SIOCGIFMEDIA) failed: Invalid argument

[donaldsharp]

We need to be a bit smarter about what we try to read data against on a *bsd system for if_ioctl. @rwestphal can you comment here with a bit more data

[pautiina]

Hello.Same problem have and on frr 3.0.3 stable.
This happens only at startup, and then sometimes.

FRRouting 3.0.3 (gate).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
configured with:
     '--enable-user=frr' '--enable-group=frr' '--enable-vty-group=frrvty' '--sysconfdir=/usr/local/etc/frr' '--localstatedir=/var/run/frr' '--disable-pimd' '--enable-fpm' '--disable-ldpd' '--without-libpam' '--disable-shell-access' '--disable-tcmalloc' '--disable-tcp-zebra' '--enable-vtysh' '--prefix=/usr/local' '--mandir=/usr/local/man' '--disable-silent-rules' '--infodir=/usr/local/info/' '--build=amd64-portbld-freebsd11.1' 'build_alias=amd64-portbld-freebsd11.1' 'PKG_CONFIG=pkgconf' 'CC=cc' 'CFLAGS=-O2 -fno-strict-aliasing -pipe  -fstack-protector' 'LDFLAGS= -L/usr/local/lib -L/usr/local/lib -fstack-protector' 'LIBS=' 'CPPFLAGS=-I/usr/local/include -I/usr/local/include' 'CPP=cpp'

2018/03/15 23:15:54 ZEBRA: if_ioctl(SIOCGIFMEDIA) failed: Device not configured
2018/03/15 23:15:55 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/15 23:15:55 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/15 23:15:55 ZEBRA: if_ioctl(SIOCGIFFLAGS) failed: Device not configured
2018/03/15 23:15:55 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/15 23:15:55 ZEBRA: if_ioctl(SIOCGIFFLAGS) failed: Device not configured
2018/03/15 23:15:55 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/15 23:15:55 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)

2018/03/16 11:12:02 ZEBRA: if_ioctl(SIOCGIFMEDIA) failed: Invalid argument
2018/03/16 11:12:02 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/16 11:12:02 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/16 11:12:03 ZEBRA: if_ioctl(SIOCGIFFLAGS) failed: Device not configured
2018/03/16 11:12:03 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/16 11:12:03 ZEBRA: if_ioctl(SIOCGIFFLAGS) failed: Device not configured
2018/03/16 11:12:03 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/16 11:12:03 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/16 11:12:03 ZEBRA: if_ioctl(SIOCGIFFLAGS) failed: Device not configured
2018/03/16 11:12:03 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)
2018/03/16 11:12:03 ZEBRA: if_ioctl(SIOCGIFFLAGS) failed: Device not configured
2018/03/16 11:12:03 ZEBRA: Can't lookup mtu by ioctl(SIOCGIFMTU)

[ocochard]

Same behaviour on 6.0

[pautiina]

I feel there will be a new port soon:)

This will be the 4th port. Interestingly, with each new version will be a new port?

[ocochard]

The "problem" with the multiple port, was because:

1. frr4 was not very stable, so I've preferred to kept net/frr3 and add a new net/frr4
2. It's great to provide a minimum of 2 main versions
   But I didn't know at the moment of frr4, that each new version will be 'major' versions, pushing me to create a new port each time :-(
   So, once frr6 will be out, I will delete net/frr3 and net/frr4 (I need to check how to do it properly).

[pautiina]

I think need read this PR #2725 and then think about delete frr version port

[pautiina]

This error is also present in the master branch.

[rzalamena]

This issue was fixed and referenced in another issue ( #2338 (comment) ).

If you still have problems, please open a new issue.