From gary@palmer.demon.co.uk  Sun Nov 27 19:30:23 1994
Received: from post.demon.co.uk (post.demon.co.uk [158.152.1.72]) by freefall.cdrom.com (8.6.8/8.6.6) with SMTP id TAA22758 for <FreeBSD-gnats-submit@freefall.cdrom.com>; Sun, 27 Nov 1994 19:30:19 -0800
Received: from palmer.demon.co.uk by post.demon.co.uk id aa07216;
          28 Nov 94 3:07 GMT
Received: (from gary@localhost) by palmer.demon.co.uk (8.6.9/8.6.9) id DAA00235; Mon, 28 Nov 1994 03:03:38 GMT
Message-Id: <199411280303.DAA00235@palmer.demon.co.uk>
Date: Mon, 28 Nov 1994 03:03:38 GMT
From: Gary Palmer <gary@palmer.demon.co.uk>
Reply-To: gary@palmer.demon.co.uk
To: FreeBSD-gnats-submit@freefall.cdrom.com
Subject: Trying to set the mtu on a slip line causes a panic
X-Send-Pr-Version: 3.2

>Number:         30
>Category:       kern
>Synopsis:       Trying to set the mtu on a slip line causes a panic
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    core (FreeBSD core team)
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 27 19:40:01 1994
>Closed-Date:    Mon Nov 28 12:40:15 PST 1994
>Last-Modified:
>Originator:     Gary Palmer
>Release:        FreeBSD 2.0.3-Alpha3 i386
>Organization:
>Environment:

486dx33 PC, 2 16450 SIO ports on ISA.

>Description:

-current kernel of about 7 hours ago seems to have a problem setting the
MTU for a SLIP line. My network provider recommmends a MTU for SLIP of 536
(for various reasons to do with their internal network), and trying to
auto-set the MTU to that value in /etc/hostname.sl0 causes a kernel panic
(page fault). Trying from the command line after booting has similar
results.

>How-To-Repeat:

ifconfig sl0 inet hostname gateway mtu 536

>Fix:
	
Unknown.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: wollman 
State-Changed-When: Mon Nov 28 12:40:15 PST 1994 
State-Changed-Why:  
David claims to have fixed the bug. 
>Unformatted:



