Network problems with sendto() syscall
Joerg Wallerich
joerg at net.t-labs.tu-berlin.de
Sun Aug 26 04:41:45 PDT 2007
Hi all,
since moving to 7-CURRENT I have a serious problem with
the network stack when using the sendto() syscall.
The problem appears as soon as I work with bootpd(8). As
soon as bootpd tries to answer a BOOTP request, the
sendto() call fails with EAFNOSUPPORT, I get kernel log
messages like
'fxp0: can't handle af18'
and then I can no longer access the IP address I sent the
BOOTP request from.
The call to sendto() in bootpd seems OK, so I doubt that the
problem lies with bootpd. The NIC driver seems to be OK as
well, as the problems appears with three different drivers
(fxp, nfe, rl). I even get things like
'kernel: looutput: af=18 unexpected'
in the logs when using bootptest on the local machine.
This problem can be reproduced on my hardware using a
vanilla installation of the latest snapshot of 7-CURRENT (200708).
Does anyone see this behavior besides myself?
Thanks,
Joerg
--
---------------------------------------------------------------
- Joerg Wallerich joerg at net.t-labs.tu-berlin.de -
- Technische Universitaet Berlin -
---------------------------------------------------------------
More information about the freebsd-current
mailing list