From nobody@FreeBSD.ORG Fri Nov 12 05:40:17 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id AF72114C9E; Fri, 12 Nov 1999 05:40:17 -0800 (PST)
Message-Id: <19991112134017.AF72114C9E@hub.freebsd.org>
Date: Fri, 12 Nov 1999 05:40:17 -0800 (PST)
From: mb@imp.ch
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: IEEE 802 encapsulation for arp on ethernet isn't supported
X-Send-Pr-Version: www-1.0

>Number:         14841
>Category:       kern
>Synopsis:       IEEE 802 encapsulation for arp on ethernet isn't supported
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    adrian
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Nov 12 05:50:00 PST 1999
>Closed-Date:    Fri Jul 09 06:14:51 GMT 2004
>Last-Modified:  Fri Jul 09 06:14:51 GMT 2004
>Originator:     Martin Blapp
>Release:        FreeBSD 4.0 CURRENT
>Organization:
Improware AG
>Environment:
not important
>Description:
In RFC 1122, Requirements for Internet Hosts -- Communication Layers);
Chapter II, 2.3.3 (Ethernet and IEEE 802 Encpasulation) is written:

[...]
Every Internet host connected to a 10Mbps Ethernet cable;

- MUST be able to send and recieve packets using RFC-894
  encapsulation.
- SHOULD be able to recieve RFC-1042 packets intermixed
  with RFC-894 packets.
[...]

It seems that FreeBSD does not support snap encapsulation on
Ethernet. Of seven different OS's, only FreeBSD had problems
with setting the arp replies. It's not usual that if we ask
with type ether, the replay is type snap, but it can happen.
>How-To-Repeat:
(using snap encapsulation on router as specified RFC-1042)

# tcpdump -s 1500 -v -v
snap arp arp reply ibmrouter is-at 0:60:92:10:6d:20 hardware #6

# arp -n -a
? (192.168.115.252) at incomplete [ethernet]


(using ether encapsulation on router as specified in RFC-894)

# tcpdump -s 1500 -v -v
arp reply ibmrouter is-at 0:60:92:10:6d:20 (0:60:92:10:6d:20)

# arp -n -a
? (192.168.115.252) at 0:60:92:10:6d:20 [ethernet]
>Fix:
I'm still investigating the problem. Help is welcome.
It seems that ATM does only support snap encapsulation
for tcp, so it should also be possible to implement
on Ethernet.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->adrian 
Responsible-Changed-By: adrian 
Responsible-Changed-When: Fri Nov 12 06:31:50 PST 1999 
Responsible-Changed-Why:  
I'll nab a cisco and look at this. 
State-Changed-From-To: open->closed 
State-Changed-By: bms 
State-Changed-When: Fri Jul 9 06:14:32 GMT 2004 
State-Changed-Why:  
This is what if_ef is for. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=14841 
>Unformatted:
