Port-amd64 archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: nd6_setmtu0: new link MTU on iwn0 (576) is too small for IPv6 which needs 1280
Date: Fri, 5 Dec 2014 09:41:20 +0000
From: Ottavio Caruso <ottavio2006-netbsd%yahoo.com@localhost>
Message-ID: <CAEJNuHwpdNOfn9krCtkZMRntMWs76=JuJHbiFRsW_TDQPsXuDA%mail.gmail.com@localhost>
| As per previous post, correct.
I think I've been seeing only about a half of the messages on
this thread... Were all of them sent to netbsd-users (cc'd or
whatever)? I don't think I was subscribed to port-amd64 (though I
am now).
| bash-4.3# tcpdump -r /tmp/dump.txt
| reading from file /tmp/dump.txt, link-type EN10MB (Ethernet)
| 10:32:09.975761 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
| BOOTP/DHCP, Request from 00:21:5c:55:ee:9d (oui Unknown), length 317
| 10:32:09.980990 IP 192.168.1.1.bootps > 192.168.1.108.bootpc:
| BOOTP/DHCP, Reply, length 548
The content of the second of those two is what would be useful to see,
but to see that, the tcpdump needs (at least) both the -s and -x options.
| Not sure why it mentions Ethernet while I have specified iwn0.
There's no practical difference (at this level) between 802.3 and
802.11 - the interface presented by the kernel is mostly the same.
That's an irrelevant minor issue.
kre
Home |
Main Index |
Thread Index |
Old Index