I would go with (a) unless someone is religiously obsessed with having the
message stay.
Else go with (b) but see if you can fit it in with some "generic verbosity"
sysctl knob, as opposed to creating its own.
Later,
Bosko.
> /kernel: arp: 1.2.3.4 is on dc0 but got reply from 00:00:c5:79:d0:0c
/kernel: arp: 1.2.3.4 is on dc0 but got reply from 00:00:c5:79:d0:0c on dc1
Hi can we axe this message already? I see the possibility of using
two 100mbit cards on a switch with a gig uplink to be reason enough
to either axe it, or make it a sysctl to quiet the warnings.
I've also had this brok
> Well. It is not the case I think. Both transfers were for big files (~200MB
> each). I've zeroed the counters after start. Measurments are acuurate according
> to both rules as well as lftp status messages.
actually the counters you sent me only showed some 300Kbytes per transfer
(which amount
* C. Stephen Gunn <[EMAIL PROTECTED]> [010103 12:19] wrote:
> On Wed, 03 Jan 2001 10:10:09 PST, Alfred Perlstein wrote:
>
> > > You could change the printf()'s to log()'s, and allow syslogd
> > > to filter/combine/report them on your console. I'm sure you
> > > already know this, you could incre
On Wed, 03 Jan 2001 12:26:21 EST, Alex Pilosov wrote:
> Sometimes in the course of human events it is necessary to break with
> compatibility ;) I believe netgraph is sufficiently advanced and well-made
> system that it should be used as much as possible.
Microsoft might argue the same about Wi
On Wed, 3 Jan 2001, Luigi Rizzo spake thusly:
> So i believe you have done some mistake in your config or your
> measurement (e.g. some other bottleneck in the net limiting
> one flow to 60Kbit, leaving a full 60k to the other no matter how
> weight are assigned).
I really don't think so. Only th
when you enter ipfw rule don't use:
ipfw add divert natd all from any to any
but use:
ipfw add divert natd all from any to any via xl0
(xl0 is the natd interface that you have specified whit natd -n ... change
it with your interface name)
after, your traceroutes will be "normal" :-)
spe.
--
[E
Hi
I possess some servers freebsd functioning as roteadores and some of them
making nat.
I have the following one problem. When I make one traceroute for some
equipment that is after these servers, it returns the IP from the first
server who is making nat.
ex:
[fulano@vitoria /]# traceroute
* C. Stephen Gunn <[EMAIL PROTECTED]> [010103 06:22] wrote:
> On Tue, Jan 02, 2001 at 07:18:10AM -0800, Alfred Perlstein wrote:
>
> > I notice that if_fxp.c seems to fail silently when unable to
> > allocate network buffers, perhaps the fact that the kernel can
> > be doing about 200 or more mess
On Wed, 3 Jan 2001, C. Stephen Gunn wrote:
> I agree that you could educate ifconfig in the ways of netgraph
> and hide it all behind the command interface you propose. It's a
> migration to a broader view of interfaces for ifconfig(8). Right
> now, ifconfig(8) is basically a front-end for ioct
On Wed, 03 Jan 2001 09:50:41 MST, Wes Peters wrote:
>> We're on the same page. I was just observing that it was a software change
>> to ifconfig. We're teaching it tricks about creating/associating netgraph
>> nodes with interfaces. Not just configuring interfaces.
>
> That *is* configuring i
"C. Stephen Gunn" wrote:
>
> On Tue, 02 Jan 2001 10:23:23 MST, Wes Peters wrote:
>
> > > Well.. It's a change to ifconfig for normal interface configuraton.
> >
> > No, what I'm saying is that ifconfig would look exactly like it does now
> > for standard IP-over-EthII and for vlan id, and would
On Tue, Jan 02, 2001 at 07:18:10AM -0800, Alfred Perlstein wrote:
> I notice that if_fxp.c seems to fail silently when unable to
> allocate network buffers, perhaps the fact that the kernel can
> be doing about 200 or more messages per-second makes me guess
> that it's not helping things, especia
Hi,
i have just run a test locally (on a 4.2R system, queues with weight
1 and 10, transfers on different tcp port) and the results
are exactly what one would expect -- one flow gets 10 times the bw of the
other one.
So i believe you have done some mistake in your config or your
measurement (e.g
14 matches
Mail list logo
