Project

General

Profile

Actions

Bug #1764

closed

Crash using natd

Added by justin over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

I upgraded from 2.4.1 to 2.6.3 on the computer that serves as my house
gateway - it does NAT using ipfw2. Shortly after reaching a console login
prompt, my system would crash.

http://www.shiningsilence.com/crash1.jpg

http://www.shiningsilence.com/crash2.jpg

Kernel and core in leaf:~/crash

(core may not be the same panic as when I took these photos; I had some
experimentation to do to get back online.)

It seemed that anything that would have to translate data back across the
exterior interface would cause it. Turning off various programs helped,
but the system would panic again if something external sent data destined
for a computer on the internal side of the network.

Removing these lines from /etc/rc.conf stopped the panics, but also lost
my gateway for internal systems.

gateway_enable="YES"
natd_enable="YES"
natd_interface="em0"

So: is anyone else still using ipfw2 on DragonFly? For NAT? Does it work?

It looks like my next best idea is to switch to pf.

Actions

Also available in: Atom PDF