Hi,
Here's a hint:
"The Apollo Domain and XNS networking protocols will no longer be offered
after Cisco IOS Release 12.2. Information about these protocols will not
appear in future releases of the Cisco IOS software documentation set."
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/pr
Bob Bishop wrote:
> Here's a hint:
>
> "The Apollo Domain and XNS networking protocols will no longer be offered
> after Cisco IOS Release 12.2. Information about these protocols will not
> appear in future releases of the Cisco IOS software documentation set."
> http://www.cisco.com/en/US/product
* De: Terry Lambert <[EMAIL PROTECTED]> [ Data: 2003-03-05 ]
[ Subjecte: Re: Removal of netns - politically correct version ]
> On the other hand, there's no compelling reason to dike it out,
> if it can be made to work. I would argue that ISA support is
> more or less just as obsolete, as
That's 2GB machine. How much RAM I need more?
mbuf clusters is full(observed by netstat -m) at peak time(3-4
hours). netstat -m output below is when the connection is low, but
please see the peak value of mbuf clusters.
From: Bosko Milekic <[EMAIL PROTECTED]>
Subject: Re: Performance tuning hint
On Tue, 4 Mar 2003, CHOI Junho wrote:
>
> That's 2GB machine. How much RAM I need more?
The statistics clearly show that you do.
--
This .signature sanitized for your protection
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
I think if you add the following rule to the ipfw rules on 192.168.0.1 ( the
squid-running host ) you can have your proxy working.
skipto 510 tcp from 192.168.0.1 to any dst-port 80
From: Darcy Buskermolen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Transparent Proxy
Date: Tue, 25 Feb 2
I was recently following a thread on tech-netbsd that was discussing
the routing tables when the gateway address was on a 10.x.x.x network
while the machine was assigned a 209.122.66.x address. The long and short
of the discussion (as I understand the discussion) was that this was
that while it c
I thank everybody who took the time to reply to me, and I found the problem,
my fwd/skipto rules needed to be after the divert rules.
On Wednesday 05 March 2003 03:19, soheil soheil wrote:
> I think if you add the following rule to the ipfw rules on 192.168.0.1 (
> the squid-running host ) you
>
> I was recently following a thread on tech-netbsd that was discussing the
> routing tables when the gateway address was on a 10.x.x.x network while
> the machine was assigned a 209.122.66.x address. The long and short of
> the discussion (as I understand the discussion) was that this was that
>
Well it's not the way I wanted it, but it's the way I have to try and work
with.
I tried the route add net 10.0.0.0 -interface (whatever)
and that didn't work for me.
-- In Response to your message -
> Date: Wed, 5 Mar 2003 09:57:55 -0800 (PST)
> To: <[EMAIL PROTECTED
> Well it's not the way I wanted it, but it's the way I have to try and
> work with.
>
> I tried the route add net 10.0.0.0 -interface (whatever)
> and that didn't work for me.
That's not the syntax I gave you, and obviously it needs to have your
local interface information inserted. I can confi
Sorry, my typo. I did try
route add -net 10.0.0.0 -interface xl0
and
route add -net 10.17.47.37 -interface xl0
As I recall both didn't respond with a error message, but when I tried to
get out it didn't work.
I'll try again tonight and see what happens.
Thanks
-- In Response to
Hi,
I am setting SO_RCVBUF for UDP socket to 64000 using
setsockopt, when sending 8K data using sendto, and
recvfrom back from inetd echo service, the length
returned from recvfrom is always 4K, why is this ?How
can I read a large data back from UDP ( > 4K ) then ?
Appreciate the help
Dave
Dear Hackers,
I'm very pleased to announce that another release is available for
download at
http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030305.tar.gz
The Bluetooth sockets layer has been cleaned up. People should not
see any WITNESS complains with new code. Locking issues have
Guys;
I have to agree with Terry that the fixes for netns
should be committed, and furthermore they should be
MFC (using his first patch perhaps). It's a nightmare
to try to rescue anything from the Attic, at least it
would be nice to have it in better shape before
killing it.
The flame fest on r
On Wed, Mar 05, 2003 at 04:03:49AM -0800, Terry Lambert wrote:
> Peter Wemm wrote:
> > Terry Lambert wrote:
> > > Here are two patches. The first fixes missing pieces in /sys/conf/files
> > > and /sys/conf/options, the second fixes all the files that need it in
> > > /sys/netns/.
> >
> > You seem
Terry Lambert writes:
> Mark Murray wrote:
> > Only if it kills this _really_ dumb debate. In time, it will no longer
> > compile, and then the situation will be the same as just punting to the
> > Attic without the "fix".
>
> Only if some idiot breaks the API contract again.
>
> Whatever happene
Terry Lambert writes:
> Let' start wth the libalias/natd incremental checksum update code;
> the code is based on RFC1141, instead of RFC1624. As a result,
> it get updated incorrectly occasionally, because it's using two's
> complement instead of one's complement math. Per RFC1642:
>
>RFC 1
Hi
At 08:53 5/3/03, Terry Lambert wrote:
[...]
The code is still useful as a simple implementation, much more
easily understood by the student than the current TCP/IP stack,
for certain.
The same is true for netipx (wc -l *.[ch] is almost identical).
--
Bob Bishop +44 (0)118 97
> On the other hand, there's no compelling reason to dike it out,
> if it can be made to work.
work == "not just compiled, but QAed against known-working implementations
and correctly documented".
Have fun. Looking forward to the patches and logs.
mcl
To Unsubscribe: send mail to [EMAIL PROT
On Wed, 5 Mar 2003, Terry Lambert wrote:
> The code is still useful as a simple implementation, much more
> easily understood by the student than the current TCP/IP stack,
> for certain.
And it will still be available. It'll just be available in the Attic. The
fact that it will get more broken in
Juli Mallett wrote:
> * De: Terry Lambert <[EMAIL PROTECTED]> [ Data: 2003-03-05 ]
> [ Subjecte: Re: Removal of netns - politically correct version ]
> > On the other hand, there's no compelling reason to dike it out,
> > if it can be made to work. I would argue that ISA support is
> > mor
Mark Linimon wrote:
> > On the other hand, there's no compelling reason to dike it out,
> > if it can be made to work.
>
> work == "not just compiled, but QAed against known-working implementations
> and correctly documented".
>
> Have fun. Looking forward to the patches and logs.
Just to be pe
Doug Barton wrote:
> On Wed, 5 Mar 2003, Terry Lambert wrote:
> > The code is still useful as a simple implementation, much more
> > easily understood by the student than the current TCP/IP stack,
> > for certain.
>
> And it will still be available. It'll just be available in the Attic. The
> fact
On Wed, 5 Mar 2003, Terry Lambert wrote:
> If you want to make it about "failure to attract a maintainer", then
> do that.
Actually several people have made this argument, along with the corollary
"failure to attract a userbase."
--
This .signature sanitized for your protection
To Unsubsc
> It took about 3 years for the updates to get out there so IPv6
> was usable
i have yet to see a cisco ios image supporting ipv6 that was usable
in production environment. and i have tried hard.
but i will admit to not having seen apollo networking for over a
decade. but i probably have not be
Doug Barton wrote:
> On Wed, 5 Mar 2003, Terry Lambert wrote:
> > If you want to make it about "failure to attract a maintainer", then
> > do that.
>
> Actually several people have made this argument, along with the corollary
> "failure to attract a userbase."
I would claim that non-working code
On Wed, 5 Mar 2003, Terry Lambert wrote:
> Doug Barton wrote:
> > On Wed, 5 Mar 2003, Terry Lambert wrote:
> > > The code is still useful as a simple implementation, much more
> > > easily understood by the student than the current TCP/IP stack,
> > > for certain.
> >
> > And it will still be avai
Terry Lambert writes:
> Peter Wemm wrote:
> > Terry Lambert wrote:
> > > Is there a compelling reason for removing this working code to
> > > the Attic?
> >
> > Terry: will you please check your facts? It takes around 30 seconds
> > to find out that it doesn't even compile.
>
> [ ... lots of tri
* De: Mark Murray <[EMAIL PROTECTED]> [ Data: 2003-03-05 ]
[ Subjecte: Re: Removal of netns - politically correct version ]
> Terry Lambert writes:
> > Peter Wemm wrote:
> > > Terry Lambert wrote:
> > > > Is there a compelling reason for removing this working code to
> > > > the Attic?
> >
>
> i have yet to see a cisco ios image supporting ipv6 that was usable
> in production environment. and i have tried hard.
This is getting OT but on the subject of repelling users, they´re probably
trying hard to repel their users to the vendor J boxen.
>
> but i will admit to not having seen ap
Juli Mallett writes:
> > > This crap is *s* trivial to fix, it's easier to fix than
> > > to watch you guys bitch about it not being fixable.
> >
> > Will it be runnable (as in tested), rather than a compile-only fix?
>
> compile-only would be a good state to leave the code in the attic.
O
Mark Murray wrote:
> Terry Lambert writes:
> > Peter Wemm wrote:
> > > Terry: will you please check your facts? It takes around 30 seconds
> > > to find out that it doesn't even compile.
> >
> > [ ... lots of trivial to fix warnings and errors ... ]
> >
> > Tell you what, I'll fix these and post a
Terry Lambert writes:
> Mark Murray wrote:
> > Will it be runnable (as in tested), rather than a compile-only fix?
>
> Is "tested" a requirement fo code to be committed or to have it
> stay in the tree?
Both.
> Be careful of your answer, unless you are willing to remove all
> code that does not
Peter Wemm wrote:
> Terry Lambert wrote:
> > Here are two patches. The first fixes missing pieces in /sys/conf/files
> > and /sys/conf/options, the second fixes all the files that need it in
> > /sys/netns/.
>
> You seem to have posted the wrong patch.
>
> This is against 4.x, not -current, and
Petri Helenius wrote:
> > seems to me that one useful question is whether the netns code
> > being there non-trivially complicates maintenance and/or
> > reliability of other code, and can i compile or module it out if
> > the bits it occupies really bothers me?
> >
> This is probably the right que
Mark Murray wrote:
> Only if it kills this _really_ dumb debate. In time, it will no longer
> compile, and then the situation will be the same as just punting to the
> Attic without the "fix".
Only if some idiot breaks the API contract again.
Whatever happened to "you broke it, you fix it"?
Hop
David O'Brien wrote:
> > Here is a single patch vs. 5.x.
> >
> > I believe this makes it actually work.
>^
>huh? This is untested?
Will you accept interoperability between two FreeBSD boxes? A
FreeBSD box and a NetBSD box?
> > Please apply this to the code, even if you are inte
On Wed, Mar 05, 2003 at 12:24:39PM -0800, Terry Lambert wrote:
>
> For heaven's sake! *It has only been 3 days* since the code
> was threatened! What do you expect *in 3 days*!?!
>
The code has been broken for 7 years. You've
had ample time to fix and *maintain* this code.
Points moot, anywa
Steve Kargl wrote:
> On Wed, Mar 05, 2003 at 12:24:39PM -0800, Terry Lambert wrote:
> > For heaven's sake! *It has only been 3 days* since the code
> > was threatened! What do you expect *in 3 days*!?!
> >
>
> The code has been broken for 7 years. You've
> had ample time to fix and *maintain* t
"=?iso-8859-1?q?Pedro=20F.=20Giffuni?=" wrote:
> Guys;
>
> I have to agree with Terry that the fixes for netns
> should be committed, and furthermore they should be
> MFC (using his first patch perhaps). It's a nightmare
> to try to rescue anything from the Attic, at least it
> would be nice to ha
Mark Murray wrote:
> Terry Lambert writes:
> > Mark Murray wrote:
> > > Will it be runnable (as in tested), rather than a compile-only fix?
> >
> > Is "tested" a requirement fo code to be committed or to have it
> > stay in the tree?
>
> Both.
Cool. Then I have a long list of things that can be
De: Terry Lambert <[EMAIL PROTECTED]> [ Data: 2003-03-05 ]
[ Subjecte: Re: Removal of netns - politically correct version ]
> On the other hand, there's no compelling reason to dike it out,
> if it can be made to work. I would argue that ISA support is
> more or less just as obsolete, as i
M. Warner Losh wrote:
ISA support is not obsolete. All new PCs still have ISA busses. They
might not have ISA Expansion Bus Slots, but they all[*] still connect
their serial ports, parallel ports, and mouse/keyboard ports via ISA.
Not to mention i8254 which gets to be major pain if ACPI would
Mark Murray wrote:
> > How long can this remain unfixed before the code is diked out,
> > and the checksum is recalculated fully, instead?
>
> Terry, you sound rather foolish when you argue like this. This
> is semantic tomfoolery and off topic. End of thread.
This is not a argument over mere imp
45 matches
Mail list logo
