Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Jan 1997 13:50:14 -0800 (PST)
From:      spatula@gulf.net
To:        freebsd-gnats-submit@freebsd.org
Subject:   kern/2526: kernel panic when trying to add a route with ip firewalling enabled
Message-ID:  <199701182150.NAA00731@freefall.freebsd.org>
Resent-Message-ID: <199701182200.OAA01091@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         2526
>Category:       kern
>Synopsis:       kernel panic when trying to add a route with ip firewalling enabled
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jan 18 14:00:01 PST 1997
>Last-Modified:
>Originator:     Nick Johnson
>Organization:
>Release:        3.0-970114-SNAP
>Environment:
3.0 with IP firewalling enabled, limited verbosity.
>Description:
When trying to enable an interface that was incorrectly configured
in syconfig, the kernel would panic upon the following command:

ifconfig ep0 inet <my machine's IP> <my gateway's IP>

The kernel debugger reports:

panic: ip_fw: chain
Debugger("panic")
Stopped at _debugger+0x35: moveb $0,_in_Debugger.118

Register contents were:

cs=0x8, ds=0x10, es=0x10, ss=0x10, eax=0x12
ecx=0xc0020000, edx=0xf0180869 _db_rite_bytes+0xd9
ebx=0x100, esp=0xefbffd50 _kstack+0x1d50, ebp=0xefbffd58 _kstack+0x1d58
esi=0xf0150d96 _ipfw_report+0x39e, edi=0xf135bfd0
eip=0xf01808f1 _Debugger+0x35, efl=0x246

>How-To-Repeat:
With IP firewalling enabled, and rules present that would block IP
from the local machine to its gateway, enable an interface from the
local machine to its gateway.
>Fix:
Disable IP Firewalling or do something like this:

ipfw flush
ipfw add allow all from any to any

>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701182150.NAA00731>