On Sat 26 Oct 2002 at 08:59:11 -0700, Jason R Thorpe wrote:
> On Sat, Oct 26, 2002 at 05:28:16PM +0200, Olaf Seibert wrote:
> 
>  > Thanks, I'll try that. A pity that isn't in 1.6 then.
> 
> It came to my attention after 1.6 was released.  It will be in 1.6.1.

Ok. I rebuilt my recently cvs-ed sources, forced simh-vax to link with
the new libpcap (1.3 (maybe that is not yet new enough?)), and now it
works better but I still get the warnings.

# dhclient
Internet Software Consortium DHCP Client V3.0rc10
Copyright 1995-2001 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

qe0: discarding oversize frame (len=1980)
qe0: discarding oversize frame (len=1980)
qe0: discarding oversize frame (len=1980)
qe0: discarding oversize frame (len=1980)
Oct 26 17:52:44  /netbsd: qe0: discarding oversize frame (len=1980)
Listening on BPF/qe0/08:00:2b:aa:bb:cc
Sending on   BPF/qe0/08:00:2b:aa:bb:cc
Sending on   Socket/fallback
DHCPDISCOVER on qe0 to 255.255.255.255 port 67 interval 3
qe0: discarding oversize frame (len=2090)
Oct 26 17:52:45  last message repeated 3 times
Oct 26 17:52:49  /netbsd: qe0: discarding oversize frame (len=2090)
DHCPOFFER from 10.0.0.5
DHCPREQUEST on qe0 to 255.255.255.255 port 67
DHCPACK from 10.0.0.5
New Network Number: 10.0.0.0
New Broadcast Address: 10.0.0.255

qe0: discarding oversize frame (len=1980)
qe0: discarding oversize frame (len=1980)
qe0: discarding oversize frame (len=1980)
Oct 26 17:52:52  /netbsd: qe0: discarding oversize frame (len=1980)
bound to 10.0.0.249 -- renewal in 36067 seconds.
# qe0: discarding oversize frame (len=2090)
Oct 26 17:52:52  last message repeated 2 times
Oct 26 17:53:04  /netbsd: qe0: discarding oversize frame (len=2090)

Pinging the host machine on the address that belongs to the same
interface as that simh-vax is using does not work however. Pinging other
hosts on that network cable works. Since the default route is via the
host machine, pinging anything else also fails. I see ARP requests going
out on the wire:

tcpdump: listening on ne0
01:01:40.401620 arp who-has azenomei.falu.nl tell dhcp249.falu.nl

but no answers. (tcpdump also running on the same host machine)

After manually installing an arp table entry, I see pings going out, but
no answers:

tcpdump: listening on ne0
01:03:26.177339 dhcp249.falu.nl > azenomei.falu.nl: icmp: echo request

I suppose that the packets just go out on the wire and are not processed
as incoming packets locally on the host. Except that I wonder then why
the dhcp worked - that server is also on the same machine.

Also, I tried a tcpdump inside simh-vax, and I suppose the promiscuous
mode setting has no effect, since I saw no packets until I specifically
sent some to it.

Pinging from the host, while tcpdump was running in simh-vax, gave this:

tcpdump: listening on qe0
qe0: discarding oversize frame (len=2090)
Oct 26 18:10:00  /netbsd: qe0: discarding oversize frame (len=2090)
18:10:00.570000 arp who-has 10.0.0.249 tell 10.0.0.5
qe0: discarding oversize frame (len=2090)
18:10:01.660000 arp who-has 10.0.0.249 tell 10.0.0.5
qe0: discarding oversize frame (len=2090)
18:10:02.690000 arp who-has 10.0.0.249 tell 10.0.0.5
qe0: discarding oversize frame (len=2090)
18:10:03.970000 arp who-has 10.0.0.249 tell 10.0.0.5
Oct 26 18:10:03  last message repeated 3 times

I suppose I should have seen the ARP replies at least from this side,
but I see none. Or would the "oversized frame" be a sent frame instead
of a received frame (as I was assuming)?


>         -- Jason R. Thorpe <thorpej@wasabisystems.com>
-Olaf.
-- 
___ Olaf 'Rhialto' Seibert - rhialto@       -- Woe betide the one who feels
\X/ polderland.nl  -- remorse without sin - Tom Poes, "Het boze oog", 4444.