Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Oct 2006 15:59:37 -0400
From:      "fulan Peng" <fulanpeng@gmail.com>
To:        "John Baldwin" <jhb@freebsd.org>
Cc:        freebsd-current@freebsd.org, Dan Nelson <dnelson@allantgroup.com>
Subject:   Re: Please help to forward port 80 to 8800 with ipfw
Message-ID:  <bf0f1bc90610131259v6a275bc8t84ec713f90158e7f@mail.gmail.com>
In-Reply-To: <200610131409.00126.jhb@freebsd.org>
References:  <bf0f1bc90610130746m311e56a0pa1531da9837a56c7@mail.gmail.com> <20061013151728.GA41884@dan.emsphone.com> <bf0f1bc90610131011i7c196bf4yb8e27462680a730e@mail.gmail.com> <200610131409.00126.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Thank you!
I added 2 lines in the configuration file:
options IPI_PREEMPTION
device   atpic
It worked.
uname -a shows the new kernel.
But, now there is a problem: all remote users cannot login and I even
cannot ping it from other machines.
The port 80 and port 8800 are all locked.
nestat -na |grep LIST shows all ports are listening.
ps -Aw cannot find anything wrong.
Cannot understand.
Please help me to unlock them.
Thanks a lot!


On 10/13/06, John Baldwin <jhb@freebsd.org> wrote:
> On Friday 13 October 2006 13:11, fulan Peng wrote:
> > After make LINT;make cleandepend;make depend;make; make install, I
> > really rebooted the machine serveral time.
> > I read somewhere says FreeBSD would not change its kernel unless you
> > manually copy the new kernel to somewhere. I think this is my problem.
> > I already tried to copy the GENERIC to my hostname file.
> > And I changed the ident to my hostname. I added
> > options IPFIREWALL
> > options IPFIREWALL_FORWARD
> > options IPFIREWALL_VERBOSE.
> > I did not pass the make.
> > Then I leave only one line there
> > options IPFIREWALL_FORWARD
> > Still won't pass the make command.
> > Please help me to get the new LINT kernel to work.
>
> You shouldn't be running a LINT kernel.  If you aren't sure how to install
> and boot a new kernel you probably should be running -stable (such as
> RELENG_6) rather than -current.  The specific breakage you are running into
> has since been fixed, and it could be worked around by adding 'device atpic'
> to your kernel config.
>
> --
> John Baldwin
>



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