igi added. Luigi claimed a 10% increase in forwarding speed
for drivers using it, I believe. :)
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
y patches been made to allow
bind to use this feature yet?
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
On Tue, 15 Oct 2002, Luigi Rizzo wrote:
> this smells a lot as a bad interaction between default window
> size and mtu -- loopback has 16k default, maybe tar uses a
> smallish window (32k is default now for net.inet.tcp.sendspace,
> but used to be 16k at the time), which means only 1 or 2 packet
On Tue, 15 Oct 2002, Luigi Rizzo wrote:
> On Tue, Oct 15, 2002 at 08:52:49PM -0500, Mike Silbersack wrote:
> ...
> > NetBSD introduced a "fix" for this recently, it seems sorta hackish, but
> > maybe we need to do something similar.
>
> this helps you if th
On Sat, 26 Nov 2005, Julian Elischer wrote:
In this world of P2P apps it would be neat to have a way that two P2P apps
could attach to each other even though each is through a firewall. Most
firewalls only allow
"outgoing" connections.
Go research Microsoft's uPnP firewall
ct to me... I assume you've tested this? If so, I'll commit
> it..
Oof. I haven't looked at the patch, but at least I know that Ed is a
committer. :)
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://
you have a weird hz setting on your machines?
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sary.
I'm sure we'll learn more once we see the source.
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
h a
single CPU. Experiment with polling, but be careful as you can start
to loose packets if the box cannot keep up. There are some
interesting networking enhancements coming soon to FreeBSD with the em
driver, but it will be a little while I think before it makes it to
RELENG_6
---Mike
-
Murugan wrote:
Hi
i need a sample(working) configuration files to set up a PPPoE server
in FreeBSD 4.9.
www.google.com
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
On Mon, 27 Feb 2006, Julian Stacey wrote:
Anyone know if modern FreeBSD still supports TCP_COMPAT_42 ?
TCP_COMPAT_42 just tweaked how we generated TCP initial sequence numbers.
The lack of it should not be impacting your ability to connect to machines
of any vintage.
Mike "
> Thanks Mike,
> Well I fixed a local problem of parity on my FreeBSD end, by changing to
> XTerm*eightBitInput:False
> XTerm*eightBitOutput: False
> xrdb -merge ~/.Xdefaults
> But rlogins & telnets to the 4.2B
of rlogin to see if that makes a difference?
Sorry about the delay in responding to this, I got sidetracked, and then I
got a cold. :)
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinf
On Tue, 7 Mar 2006, Julian H. Stacey wrote:
Looks to me like skyr decided to close the connection, and it closed as
expected. I think the problem is probably above the TCP layer - have you
tried an older version of rlogin to see if that makes a difference?
Hmm. Thanks Mike,
Until you wrote
connections (e.g.
10+ at once sending dump piped through ssh) it kept the CPU
utilization down. If you have just one or two, it doesnt really
matter
---Mike
----
Mike Tancsa, Sentex communications http://www.sentex.net
Providing Int
It's been nearly four years, I was wondering if anyone has had a thought
on this change yet. :)
Mike "Silby" Silbersack
-- Forwarded message --
Date: Tue, 30 Jul 2002 15:15:55 -0500 (CDT)
From: Mike Silbersack <[EMAIL PROTECTED]>
To: freebsd-net@fre
better performance / reliability over the stock ppp ?
The application is low bandwidth, but doesnt deal that well with
packet loss and the phone lines in these remote locations tend to be
noisy and drop connections frequently.
---Mike
wireless right now, we might have some sites that would need it
in the fture and this might be an approach. I imagine satellite users
run into this as well no ?
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mai
ely, these are very remote sites in industrial and
rural areas where xconnect boxes tend to be rusty posts. I will try
a lower MTU size to see how it deals with errors.
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freeb
At 05:26 AM 21/05/2006, Brian Candler wrote:
On Fri, May 19, 2006 at 12:38:31PM -0400, Mike Tancsa wrote:
> Thanks for the reply. Even at 28.8 I am seeing loss with
> the connection dropping and seeing dropped packets (e.g.
> May 19 12:04:43 soekris4801 ppp[3404]: tun0: Phase
At 01:15 PM 21/05/2006, Brian Candler wrote:
On Sun, May 21, 2006 at 11:09:23AM -0400, Mike Tancsa wrote:
> The internal USR seems to correctly see the carrier drop and PPP
> hence sees it. However, the 2 external Intels I am experimenting
> with on the USB serial ports do not.
U
chine.
Thanks, I have used them in the past. They are certainly quite a bit
more expensive than the USRs (3x) but I might be able to justify it
if they really do perform a lot better.
---Mike
___
freebsd-net@freebsd.org ma
pically these sites are
too remote for other types of transport. I think if I can get mp
working with reliable dcd I think that should do it.
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
driver should cover that card. Can you do a "pciconf -lv" and
show us the section which describes your network card? It may just be
that yours has a slightly different device ID.
Mike "Silby" Silbersack
___
freebsd-net@freebsd.o
re on.
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Nikolas Britton wrote:
No I have not tired this, I didn't even know Intel made FreeBSD
drivers... I went looking on the site early but couldn't find
anything. Do you know if they are any good?... I'll check it out,
thanks.
It is essentially the same driver that FreeBSD uses, but the one
provid
forsee us changing FreeBSD's default keepalive setting, but you're
more than welcome to change the setting on your own system.
Also note that ipfw2 sends keepalive packets on its own, maybe you could
switch to it and/or add that functionality to your favorite firewall
package. :)
Mik
Does anyone know a good CARP howto for FreeBSD? I've googled around, but
i cant find anything specific to FreeBSD.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL
Anton Yuzhaninov wrote:
Saturday, August 12, 2006, 8:30:00 PM, Mike Jakubik wrote:
MJ> Does anyone know a good CARP howto for FreeBSD? I've googled around, but
MJ> i cant find anything specific to FreeBSD.
You can use CARP howto for OpenBSD.
Yup, that and the FreeBSD man page
, it might needlessly terminate the connection.
So, in summary, there are many opinions about keepalives. That's why
everything about them is tunable. :)
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org
is to try it. :)
Note that the probes are retransmitted a few times (I think eight times)
before the connection is considered dead, so it would take longer
than two minutes.
Simon Walton
True, I had forgotten about that fact.
Mike "Silby&q
Max Laier wrote:
Have a look at: http://www.countersiege.com/doc/pfsync-carp/#big for one
idea. All requirements (carp, pf and pfsync) are available in FreeBSD as
well.
You can load balance with CARP, but AFAIK it only works on the local
network segment, i.e. it wont work past a router.
Max Laier wrote:
On Wednesday 30 August 2006 18:52, Mike Jakubik wrote:
Max Laier wrote:
Have a look at: http://www.countersiege.com/doc/pfsync-carp/#big for
one idea. All requirements (carp, pf and pfsync) are available in
FreeBSD as well.
You can load balance with CARP, but
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
So I set things back to
kern.timecounter.hardware: ACPI-fast
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Although it sounds silly, could you try recompiling 6.1 and 7.0 with a
non-SMP kernel and see how they perform? That would at least tell us if
it's a general performance problem in 6.x and 7.x, or if SMP is somehow
hurting performance in this case.
Mike "Silby&q
to
see if performance changes there as well?
How about local sockets?
Impressive improvements for TCP, in any case!
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscrib
mance
loss for those cases!
> In fact I have always thought we should:
>
> a) have no data portion in an mbuf.. just pointers i.e. always
> an EXT
>
> b) Have a 256/512 and 1k cluster too..
Implement and benchmark it. :)
Mike "Silby" Silbersack
_
On Tue, 3 Oct 2006 23:32:37 +0200, in sentex.lists.freebsd.net you
wrote:
>Perhaps a bit off-topic, but I'm looking for a cheap vlan switch.
>Anyone with a suggestion?
If you just want FastE a Cisco 2924 is very cheap on ebay.
---Mike
] local 1.1.1.1 port 57584 connected with 1.1.1.2 port 5001
[ 3] 0.0-10.0 sec 1.06 GBytes914 Mbits/sec
6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Mon Oct 9 23:22:10 EDT 2006
One is a Pentium(R) 4 CPU 3.00GHz and the other an AMD 3800 X2
Going the other wa
net.inet.tcp.inflight.enable on 6.x if you want
it to be the same setting as on 4. This kicks in when the hosts are
not directly connected and can hamper performance.
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman
ssues like duplex setting bugs, I would try the two boxes back to
back and make sure its the same subpar performance.
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
f you dont use INET6 or ipsec, I would remove them from the
kernel
---Mike
Mike Tancsa, Sentex communications http://www.sentex.net
Providing Internet Access since 1994
[EMAIL PROTECTED], (http://www.tancsa.com)
__
with various small
packets). I will load up some more boxes tomorrow and see how it goes.
I tested on an
acpi0: on motherboard
with the onboard NIC.
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
At 08:19 PM 11/8/2006, Jack Vogel wrote:
BUT, I've added the FAST_INTR changes back into the code, so
if you go into your Makefile and add -DEM_FAST_INTR you will
then get the taskqueue stuff.
It certainly does make a difference performance wise. I did some
quick testing with netperf and net
At 08:19 PM 11/8/2006, Jack Vogel wrote:
BUT, I've added the FAST_INTR changes back into the code, so
if you go into your Makefile and add -DEM_FAST_INTR you will
then get the taskqueue stuff.
Not sure why you would want FAST_INTR and polling in at the same
time, but I found that the two are
At 10:51 AM 11/9/2006, Scott Long wrote:
Mike Tancsa wrote:
At 08:19 PM 11/8/2006, Jack Vogel wrote:
BUT, I've added the FAST_INTR changes back into the code, so
if you go into your Makefile and add -DEM_FAST_INTR you will
then get the taskqueue stuff.
It certainly does make a diffe
At 05:00 PM 11/9/2006, Mike Tancsa wrote:
At 10:51 AM 11/9/2006, Scott Long wrote:
Mike Tancsa wrote:
At 08:19 PM 11/8/2006, Jack Vogel wrote:
BUT, I've added the FAST_INTR changes back into the code, so
if you go into your Makefile and add -DEM_FAST_INTR you will
then get the task
At 05:00 PM 11/10/2006, Jack Vogel wrote:
On 11/10/06, Mike Tancsa <[EMAIL PROTECTED]> wrote:
Some more tests. I tried again with what was committed to today's
RELENG_6. I am guessing its pretty well the same patch. Polling is
the only way to avoid livelock at a high pps rate.
ee what I can do over the weekend. I have some changes
to babysit again tomorrow night and will see what I can do between cycles.
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsu
At 01:42 AM 11/11/2006, Scott Long wrote:
driver. What will help me is if you can hook up a serial console to
your machine and see if it can be made to drop to the debugger while it
is under load and otherwise unresponsive. If you can, getting a process
dump might help confirm where each CPU is
At 11:41 AM 11/12/2006, Scott Long wrote:
Mike Tancsa wrote:
At 01:42 AM 11/11/2006, Scott Long wrote:
driver. What will help me is if you can hook up a serial console to
your machine and see if it can be made to drop to the debugger while it
is under load and otherwise unresponsive. If you
test with
#define EM_FAST_INTR 1
as well as taking out the nfs option from the kernel
driver. Anything else to tune with ?
---Mike
Scott
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubs
At 11:05 PM 11/12/2006, Scott Long wrote:
Mike Tancsa wrote:
However, if I turn on fastforwarding, its back to the old behavior
with it locking up. This was with the stock driver. I will try the
same test with
#define EM_FAST_INTR 1
as well as taking out the nfs option from the kernel
At 12:15 AM 11/13/2006, Scott Long wrote:
Is this with EM_INTR_FAST enabled also?
Yes. Havent done the stock case yet, but will do so later today.
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
At 12:15 AM 11/13/2006, Scott Long wrote:
Is this with EM_INTR_FAST enabled also?
Without it, the 2 streams are definitely lossy on the management interface
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org
At 12:50 PM 11/13/2006, Ivan Voras wrote:
Mike Tancsa wrote:
> At 12:15 AM 11/13/2006, Scott Long wrote:
>
>> Is this with EM_INTR_FAST enabled also?
>
> Yes. Havent done the stock case yet, but will do so later today.
Do you have a comparison with Linux under the same circum
At 08:24 PM 11/17/2006, John Polstra wrote:
Thanks for the reply, Mike. I think the PCI-Express risers in this
box are 8X. That's what the Dell spec sheet says, anyway.
Havent had too much experience with PCIe riser cards yet, but have
had some experience with bad PCI-X risers. Any w
the 11th, but I was briefly using
it from the 16th with MSI support and it was fine as well.
Do you have them on xover cables or a switch ?
---Mike
----
Mike Tancsa, Sentex communications http://www.sentex.net
Providing Internet
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
vers support jumbo frames; bce, bge, em, ixgb,
>lge, nge, sk stge, and vge. What is perceived as the most stable,
The Intel 1000PT PCIe cards work well under FreeBSD. I have been
stressing this card and it does well in RELENG_6
---Mike
---
ADAPTIVE_GIANT # Giant mutex is adaptive.
and adding
options NO_ADAPTIVE_MUTEXES
from the kernel. This should help a little with the non
fast_forwarding case.
---Mike
----
Mike Tancsa, Sentex communications http://www.sentex.net
Prov
On Mon, January 8, 2007 2:58 pm, Steven Hartland wrote:
> I've just been looking at an issue reported by some
> of our users that downloads from our one of our sites
> run on FreeBSD 6.1 and Apache 1.3 where strangely
> slow.
>
> After doing some digging around I found that two remote
> machines on
thing subtle. :)
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
developer working on an updated version
of BPF that will perform even better than it does already. I'll let him
reveal himself if he wishes. :)
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
usually a sign of a hardware lockup as
opposed to a software bug.
What is the chipset of the MB ? Does ichwd work with it to reset it ?
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To u
ren to fix its state table.
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
less
frequently, so maybe we'll have those in place for FreeBSD 6.3 if all goes
well.
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any
ill, I have not
seen any regressions with it yet since installing it last
Saturday. This is a fairly busy recursive DNS server
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsub
twork_ipv6 it was handled at all.
Currently, it goes through and deletes all
IPv6 addresses on the interface.
Cheers.
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55
[EMAIL PROTECTED] | Fre
change makes it operate more
correctly.
Could someone take a quick look over this to confirm that my patch makes
sense?
Thanks,
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
e to not create any firewall rules which depended on
there being any relation between the ephemeral ports and whatever you are
connecting to.
(In addition, there's nothing stopping a program from picking a port
1024 < x < 65535 of its own choosing.)
Mike "Silby" Silbersac
taken up...
#1, Don't do the status update every second, only have it run every 10
seconds or so.
#2, Reduce the number of PHY operations. mii_phy_tick reads the status
register, then nsphy_status rereads it basically immediately. I'll have
to examine how the other phy drivers operate
On Tue, 1 Oct 2002, Vinod wrote:
> i use the commands
> ipfw add pipe 1 ip from any to 10.0.1.0/24
> ipfw pipe 1 config bw 100Kbit/s
Make sure that you don't have ipfw allow all from any to any before the
rule which adds pipe 1. If so, packets will never enter the pipe
(redirected to -net so others can review this)
I can see how these source quench messages would cause problems if a DoS
is being routed through a FreeBSD router, and I think that your patch
makes sense. Are there any objections to me committing this in a few
days?
Mike "Silby" Silb
On Tue, 12 Nov 2002, Tony Finch wrote:
> Mike Silbersack <[EMAIL PROTECTED]> wrote:
> >
> >I can see how these source quench messages would cause problems if a DoS
> >is being routed through a FreeBSD router, and I think that your patch
> >makes sense. Are ther
On Wed, 13 Nov 2002 [EMAIL PROTECTED] wrote:
> > Mike Silbersack <[EMAIL PROTECTED]> wrote:
> > >
> > >I can see how these source quench messages would cause problems if a DoS
> > >is being routed through a FreeBSD router, and I think that your patch
>
but the server's
built-in anti-syn flood countermeasures should do fine.
Hence, I'm not sure that we can do anything better than what we are doing
now. Once the 5.0 codefreeze is over, I'll go in and take out the
misleading comment.
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
se cards properly. If so, we can probably
extract the necessary changes from the linux driver.
If both of those fail, you could search for relevant documentation and we
could work based off of that.
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
outside connection.
Just to clarify, both work correctly, as long as there is only one of them
in the box at a time?
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
o way to inspect the IP reassembly queue
actively, but you could use netstat -s to see "fragments received" - if
the number is high, then it's likely something is up.
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
the solution is to
make if_xl work with the card instead of if_ep. :)
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
#define TC_DEVICEID_HURRICANE_556 0x6055
from if_ep_pccard.c:
case 0x6055: /* 3C556 */
Is it possible that 3Com used the same chip in mini-pci and pccard
designs? This does seem possible, as 3c905 (pre-B, I don't know about the
mini-PCI version) cards support the 3c509 interf
Urk, this message got stuck in my drafts folder, sorry for the delay.
On Thu, 2 Jan 2003, Jeff Behl wrote:
> Thanks for the info. Could you explain how mbuf clusters and mbufs are
> related? i'd like to better understand how we can run out of one and
> not the other. also, is there an upper v
even though the firewall would appear to allow it?
Thanks,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
tering of traffic from the outside world happens on the
> external interface,
I my case the packets are being dropped on the outside interface, as shown
above.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
d news. I'll feel better about relaxing my rules a bit
until I can figure out why I'm seeing different behavior than Crist
and what is described in the ipfilter documentation
(http://coombs.anu.edu.au/~avalon/ipfil-flow.html - note the final
bullet item).
mike
To Unsubscribe:
repeat it.
I bet that this exploit might be limited to a small subset of dc supported
chipsets.
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
Do you have device.hints in /boot of your diskless tree?
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | Fingerprint: D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9
msg08179/pgp0.pgp
Description: PGP signature
I've got a client wanting to establish IPSEC tunnel / VPN between two
offices. One end running FreeBSD/IPSEC (KAME), the other end Linux
FreeS/WAN. The problem I'm having is most interoperability docs I've
found on the 'Net are dated back to 2000 or so - has anything changed?
This is my first ti
ux :-)
>
> -mi
Er, well, you could always write an article about the process of updating
rc.firewall.
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
e-process decrypted ESP packets. Perhaps change 1.214 can
be reworked or reverted? I'll file a PR.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
On Thursday 13 February 2003 01:44 pm, Andriy Gapon wrote:
>
> Mike, filing a PR is an excellent idea. I think that should have been from
> the start.
> Thank you.
FYI, it's PR#48159 in case you want to add anything.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
ry
But Terry, his homework is due Friday!!!
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
r:
---
From: G.P. de Boer
To: Mike Silbersack <[EMAIL PROTECTED]>
Subject: The "stale TCP-connects in LAST_ACK" problem
Hi Mike,
I've upgraded my system to 4.7-STABLE as you said, to see if the patches
Matt Dillon MFC'ed made my problem disappear.
I have good news: with a c
ers also (Cisco and Nortel) so it might be them.
>
> -- Sten
FreeBSD has no traffic prioritizing built in by default. Note that PSH
flags are always ACK'd immediately, whereas non-PSH flags are subject to
delayed ACKs. Are you perhaps measuring the occurance of that?
Mike "Si
1024
and even 1 byte per block all stop transmitting at 147456 bytes.
Does anyone know what is magical about 147456?
Thanks,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
s if you find any
more bugs!
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
/conf/GENERIC to the attic while
> you are at it. It can serve it's purpose from there, too.
This comment is not helpful.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
On Tue, 25 Feb 2003, Darcy Buskermolen wrote:
> I'm trying to deploy a transparent proxy server for a friend's office but have
> run into a couple of snags that I can't seam to find the correct answer for.
a) Draw a diagram,
b) Check IPFW rules (tcpdump is your friend),
c) Check out transproxy...
801 - 900 of 1032 matches
Mail list logo
