Re: transparent Squid 2.5Stable10 + FreeBSD 5.3

- Original Message - From: "Ryan Rathje " <[EMAIL PROTECTED]> To: Sent: Monday, June 20, 2005 11:40 PM Subject: transparent Squid 2.5Stable10 + FreeBSD 5.3 > ipfw add allow all from any to 192.168.1.2 80 > ipfw add fwd 192.168.1.2 tcp from any to 192.168.1.2 3128 > ipfw add fwd 192.168.

Policy routing idea (Was: ipfw: Would it be possible to continue processing rest of rules after match ?)

Hi, I sent this to ipfw mailing list some time ago, but got no response. I would like to adjust ipfw behaviour with fwd rules to make policy routing easier (ie. make it separete from filtering rules). I would just like some input if this makes any sense (or is possible at all with current design)

Re: Issues with a Large Fat pipe Network simulation

Luigi Rizzo wrote: When testing without any extra delay on 'network' and send/recvspaces of 65535 bytes, we can sustain around 800mbit/s. The interrupts on 'network' may be the limiting factor here. However, when we set the send/recv space to 65535*2, we can only sustain around 200-300mbit/s. It

Re: Issues with a Large Fat pipe Network simulation

On Mon, Jun 20, 2005 at 10:11:27PM +0200, Pieter de Boer wrote: > Hello there, ... > When testing without any extra delay on 'network' and send/recvspaces of > 65535 bytes, we can sustain around 800mbit/s. The interrupts on > 'network' may be the limiting factor here. However, when we set the > sen

EM Driver problems

I have been using fxp network based cards, without issues. I have recently changed over to em cards, and get kernel panics about once every few days with them (mainly sbdrop panics). I already have nsfclusters set to 32k, and freebsd vm memory set to 850megs, with 4g memory installed. After p

Issues with a Large Fat pipe Network simulation

Hello there, For a project about TCP (performance) enhancements, we have been trying to simulate a network with a high bandwidth*delay product. Although we haven't started our real tests just yet, we already stumbled upon some issues :). For one (advertising an invalid window scale in some situati

Re: transparent Squid 2.5Stable10 + FreeBSD 5.3

Quoting Ryan Rathje <[EMAIL PROTECTED]>: Here's my FreeBSD setup Nic1 -> outside (123.456.789.10) Nic2 -> internal (192.168.1.2) Here's my client Win2k setup IP: 192.168.1.5 MASK: 255.255.255.0 GW: 192.168.1.2 - I have FreeBSD 5.3 installed with the modif

Re: transparent Squid 2.5Stable10 + FreeBSD 5.3

See http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/71910 Don't know why it still plays up after 5.2.1 Edwin -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://weblog.barnet.com.au/edwin/

transparent Squid 2.5Stable10 + FreeBSD 5.3

Here's my FreeBSD setup Nic1 -> outside (123.456.789.10) Nic2 -> internal (192.168.1.2) Here's my client Win2k setup IP: 192.168.1.5 MASK: 255.255.255.0 GW: 192.168.1.2 - I have FreeBSD 5.3 installed with the modified kernel options options IPFILTER

Current problem reports assigned to you

Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description --- o [2003/07/11] kern/54383 net [nfs] [patch] NFS root configurations w

Re: Routes not deleted after link down

Michal Vanco (vanco) writes: > On Sunday 19 June 2005 21:54, Sten Daniel Sørsdal wrote: > > Gleb Smirnoff wrote: > > > My vote is that we should implement this functionality and make it > > > switchable via sysctl. I'd leave the default as is. > > > > > > What is opinion of other networkers? > > >

Re: Routes not deleted after link down

On Sunday 19 June 2005 21:54, Sten Daniel Sørsdal wrote: > Gleb Smirnoff wrote: > > My vote is that we should implement this functionality and make it > > switchable via sysctl. I'd leave the default as is. > > > > What is opinion of other networkers? > > How about also adding a sysctl for setting