kern/64659: natd not work

Maxim Konovalov maxim at macomnet.ru
Fri Mar 26 11:40:15 PST 2004


The following reply was made to PR kern/64659; it has been noted by GNATS.

From: Maxim Konovalov <maxim at macomnet.ru>
To: Dmitry Brazhnikov <Dmitry.Brazhnikov at ncc.volga.ru>
Cc: bug-followup at freebsd.org
Subject: Re: kern/64659: natd not work
Date: Fri, 26 Mar 2004 22:34:56 +0300 (MSK)

 On Wed, 24 Mar 2004, 08:06-0800, Dmitry Brazhnikov wrote:
 
 >
 > >Number:         64659
 > >Category:       kern
 > >Synopsis:       natd not work
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       high
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Wed Mar 24 08:10:19 PST 2004
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Dmitry Brazhnikov
 > >Release:        5.2.1
 > >Organization:
 > NCC
 > >Environment:
 > FreeBSD mail.stopol.tlt.ru 5.2.1-RELEASE-p3 FreeBSD 5.2.1-RELEASE-p3 #3: Mon Mar 22 22:27:20 SAMT 2004     root at mail.stopol.tlt.ru:/usr/src/sys/i386/compile/MAIL  i386
 >
 >
 > >Description:
 > I read man natd
 > I build kernel with options
 > IPFIREWALL & IPDIVERT for natd install and reboot system.
 > After reboot nat not work.
 > Using FreeBSD from 2.2.7
 >
 > ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0x6500-0x651f irq 10 at device 9.0 on pci0
 > ed0: address 00:60:52:09:24:d7, type NE2000 (16 bit)
 > rl0: <D-Link DFE-530TX+ 10/100BaseTX> port 0x6600-0x66ff mem 0xe3000000-0xe30000ff irq 9 at device 11.0 on pci
 > 0
 > rl0: Ethernet address: 00:50:ba:5f:a0:f9
 > miibus0: <MII bus> on rl0
 > rlphy0: <RealTek internal media interface> on miibus0
 > rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 >
 >
 > >How-To-Repeat:
 > rebuild kernel and run natd
 > >Fix:
 > i don`t know - trouble in natd or kernel.
 
 This is not a correct Problem Report.  Please be more specific about
 your setup, show your ipfw(8) rules and natd(8) logs.  And I am pretty
 sure Severity: serious and Priority: high are not adequate.  We have
 a good article about writing PR:
 
 http://www.freebsd.org/doc/en/articles/problem-reports/
 
 Thanks.
 
 --
 Maxim Konovalov


More information about the freebsd-bugs mailing list