Re: pxeboot btx halted problem

[Danny Braniss]

> On Mon, 21 Jan 2002, Ladislav Kostal wrote:
> > On Sun, 20 Jan 2002, Jason K. Fritcher wrote:
> > > I'm trying to get a machine to netboot with the pxeboot loader and a Intel
> > > PRO/100 S network card. I built pxeboot with tftp instead of nfs support,
> > > as I am only looking to load a kernel with a mfs filesystem in it.
> >
> > If you want, I can send you my setup. But it is for Scom 3c905C (what
> > should make no difference).
> 

im no expert in reading btx dump, but from past experience, upgrading the
firmware of the BIOS/NIC solved the problem.

danny



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: NATD, or another one I haven't seen before

[Barry Irwin]

I dont think this is neccesarily a new source code related bug.  During the
CodeRed / CodeRedII sagas of last year I had a number of NATD's lock up
On a range of boxes from 4.3 right to 4.0, they exhibited a massive growth
in memory usage 30MB+ and CPU time.  Packets were getting handled, but ere
taking forever, I was getting ping times on the order of 400 seconds.

This also occured on network segments in 4 different continents.  Again a
pile of arp traffic was seen on the external side of the firewalls.  My
initial response was that state table swere filling up because of all the
incomplete connections, but tests with synfloods by muself were unable to
duplicate the problem.

Barry


--
Barry Irwin [EMAIL PROTECTED]  +27214875150
Systems Administrator: Networks And Security
Itouch Labs http://www.itouchlabs.com   South Africa

On Mon 2002-01-21 (11:48), Robert D. Hughes wrote:
> 
> CVSUP from 1/16, running natd with command /sbin/natd -config /etc/natd.conf -n dc0. 
>Config file is:
> 
> log_denied
> log_facility security
> use_sockets
> same_ports 
> unregistered_only
> redirect_port tcp x.x.x.x:80 x.x.x.x:80
> redirect_port tcp x.x.x.x:443 x.x.x.x:443
> redirect_port tcp x.x.x.x:8880 x.x.x.x:8880
> redirect_port tcp x.x.x.x:2953 x.x.x.x:2953
> redirect_port tcp x.x.x.x:2954 x.x.x.x:2954
> dynamic
> punch_fw 1:1000
> 
> I'm going to try removing the log options and see if it improves. but since this is 
>a new issue with the recent cvs build, I did want to send out a query.
> 
> What I'm seeing is natd going to well over 90% cpu on this box, which has never 
>happened before to the best of my knowledge. What tcpdump is showing my is very large 
>amounts of arp traffic on the external interface from a large part of the 12.237/16 
>network (yeah, I know, lame provider). Has anyone else been running into similar 
>issues?
> 
> "Great spirits have always encountered violent opposition from mediocre minds." -- 
>Albert Einstein 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
> 
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message