On May 18, 11:51am, erplefoo@gmail.com (Sean Davis) wrote:
-- Subject: Re: fxp0: can't handle af118

| I'm seeing the same thing with tl(4):
| May 18 11:45:31 eros /netbsd: tl1: can't handle af8
| 
| I am also using a catch-all return-rst rule...
| 
| It appears to stem from sys/net/if_ethersubr.c (revision 1.114) line 462-465:
|   462    default:
|   463       printf("%s: can't handle af%d\n", ifp->if_xname,
|   464          dst->sa_family);
|   465       senderr(EAFNOSUPPORT);
| 
| if the address family is broken, but different, for fxp, it sounds
| like it's not getting set somewhere and a value from elsewhere is
| leaking in, or something similar. I'll see if I can figure out what,
| but it's been ages since I've looked through the ethernet code.
| 
| -Sean


I think the code that is broken is the code that prepares the dst packet
somewhere in ip_nat or ip_fil.

christos