Re: discarding oversize frame

[George Georgalis <george%galis.org@localhost>]

On Wed, Dec 19, 2012 at 1:38 PM, George Georgalis <george%galis.org@localhost> 
wrote:
> On Mon, Dec 17, 2012 at 2:40 PM, George Georgalis 
> <george%galis.org@localhost> wrote:
>>
>> On Sat, Dec 15, 2012 at 9:11 AM, David Young <dyoung%pobox.com@localhost> 
>> wrote:
>> > On Fri, Dec 14, 2012 at 06:10:17PM -0800, George Georgalis wrote:
>> >> Here's some data on the frame size:
>> >>  grep oversize /var/log/messages | sed 's/.*atom//' | sort -u
>> >>  /netbsd: wm0: discarding oversize frame (len=1434)
>> >>  /netbsd: wm0: discarding oversize frame (len=595)
>> >>  /netbsd: wm0: discarding oversize frame (len=662)
>> >>  /netbsd: wm0: discarding oversize frame (len=678)
>> >>  /netbsd: wm0: discarding oversize frame (len=746)
>> >
>> > Very strange.  I don't see why those are oversize.  mtu on wm0 is 1500?
>>
>> It is 1500, but I'm having issues getting a useful dhcp reply now so
>> if that changes it, I cannot answer just yet....
>
>
> Some progress here.... since continued unexpected errors, I switched
> to VMware Player.
>
> It would seem the problem now (and before?) is:
>
> Dec 19 05:29:24 atom dhcpcd[1267]: wm0: wm0: MTU set to 576
>
> Here's some more logs...
>
> Dec 19 05:13:10 atom syslogd[381]: last message repeated 19 times
> Dec 19 05:13:10 atom /netbsd: wm0: discarding oversize frame (len=599)
> Dec 19 05:13:13 atom /netbsd: wm0: discarding oversize frame (len=1434)
> Dec 19 05:13:44 atom /netbsd: wm0: discarding oversize frame (len=1434)
> Dec 19 05:15:45 atom /netbsd: wm0: discarding oversize frame (len=1434)
> Dec 19 05:25:59 atom syslogd[381]: last message repeated 346 times
> Dec 19 13:29:24 atom dhcpcd[295]: wm0: failed to renew, attempting to rebind
> Dec 19 13:29:24 atom dhcpcd[295]: wm0: acknowledged x.y.115.116 from
> 173.36.131.33
> Dec 19 13:29:24 atom dhcpcd[295]: wm0: leased x.y.115.116 for 257850 seconds
> Dec 19 05:29:24 atom dhcpcd[1267]: wm0: wm0: MTU set to 576
>
> that dhcp server won't change... all the tcp resets make the network
> pretty useless...
>
> Anyone got a workaround?


disabling dhcpcd and using dhclient instead seems to resolve all issues....


-George



-- 
George Georgalis, (415) 894-2710, http://www.galis.org/