On Tue, Apr 19, 2005 at 08:27:19AM -0700, Sam Leffler wrote:
S> >change message will report either all state changes or those where at
S> >the time of reporting the state changed relative to the last report.
S> >The same assumption is true for the OpenIGPd we are working on at the
S> >moment.
S>
S>
On Tue, Apr 19, 2005 at 08:36:28AM +0100, Robert Watson wrote:
> On Mon, 18 Apr 2005, Kris Kennaway wrote:
>
> >This on an u10 running
> >
> >FreeBSD 5.3-STABLE (NETBOOT) #1: Sun Dec 12 18:38:35 JST 2004
> >
> >It may already be fixed, but since this is clearly a very infrequent
> >problem (the o
All,
at:
http://people.freebsd.org/~mlaier/pf37/
you will find the first shot at the long awaited import of a new version of
pf. This is level with what is likely to be shipped as OpenBSD 3.7 and
includes *most* of the features. Some are not yet implemented:
- Filtering on route labels
On 4/19/05, Eivind Hestnes <[EMAIL PROTECTED]> wrote:
> Thanks for the advice. Didn't do any difference, though.. Perhaps I
> should try to increase the polling frequency..
> >>I have an Intel Pro 1000 MT (PWLA8490MT) NIC (em(4) driver 1.7.35) installed
> >>in a Pentium III 500 Mhz with 512 MB RAM
John-Mark Gurney wrote:
dnr wrote this message on Tue, Apr 19, 2005 at 18:01 +0300:
are there any solution for emulating a network switch between network interfaces under FreeBSD 5.3?
i cannot use ng_hub because it does not filter packets by their mac addresses...
the purpose is switching betwe
The rule of thumb I have seen on Intel/UNIX based routers is that you
want 1GHz of CPU for every gigabit of throughput.
Also, on gigabit NICs, make sure you have a 64-bit PCI bus on the
motherboard.
Michael F. DeMan
Director of Technology
OpenAccess Network Services
Bellingham, WA 98225
[EMAIL
Thanks for the advice. Didn't do any difference, though.. Perhaps I
should try to increase the polling frequency..
Jerald Von Dipple wrote:
Hey man
You need to bump
kern.polling.burst: 150
Upto at least 15
Regards,
Jerald Von D.
On 4/19/05, Eivind Hestnes <[EMAIL PROTECTED]> wrote:
Hi,
I h
dnr wrote this message on Tue, Apr 19, 2005 at 18:01 +0300:
> are there any solution for emulating a network switch between network
> interfaces under FreeBSD 5.3?
> i cannot use ng_hub because it does not filter packets by their mac
> addresses...
> the purpose is switching between ngeth0,ngeth1
On Tue, Apr 19, 2005 at 08:36:28AM +0100, Robert Watson wrote:
> On Mon, 18 Apr 2005, Kris Kennaway wrote:
>
> >This on an u10 running
> >
> >FreeBSD 5.3-STABLE (NETBOOT) #1: Sun Dec 12 18:38:35 JST 2004
> >
> >It may already be fixed, but since this is clearly a very infrequent
> >problem (the o
Andre Oppermann wrote:
Gleb Smirnoff wrote:
On Tue, Apr 19, 2005 at 02:08:28PM +0200, Andre Oppermann wrote:
A> Gleb Smirnoff wrote:
A> > A> You have to be careful here indeed. If the link is rapidly flapping
A> > A> then you only want to report changes in status. For example when
A> > A> it goin
hello,
are there any solution for emulating a network switch between network
interfaces under FreeBSD 5.3?
i cannot use ng_hub because it does not filter packets by their mac addresses...
the purpose is switching between ngeth0,ngeth1 and em0.
any ideas are welcome
Donatas G.
__
Hi everybody,
I'm trying to connect an IPv6 streaming client to an IPv6 server through a
GPRS connection.
The client protocol stack should be like this
RTP / UDP / IPv6 / PPP(client) / L2TP / UDP / IPv4 / PPP (kernel) /
Bluetooth
For the moment, I've to implement this one to test.
Gleb Smirnoff wrote:
>
> On Tue, Apr 19, 2005 at 02:08:28PM +0200, Andre Oppermann wrote:
> A> Gleb Smirnoff wrote:
> A> > A> You have to be careful here indeed. If the link is rapidly flapping
> A> > A> then you only want to report changes in status. For example when
> A> > A> it going down, up
On Tue, Apr 19, 2005 at 02:08:28PM +0200, Andre Oppermann wrote:
A> Gleb Smirnoff wrote:
A> > A> You have to be careful here indeed. If the link is rapidly flapping
A> > A> then you only want to report changes in status. For example when
A> > A> it going down, up, down and all these events got qu
Gleb Smirnoff wrote:
> A> You have to be careful here indeed. If the link is rapidly flapping
> A> then you only want to report changes in status. For example when
> A> it going down, up, down and all these events got queued it doesn't
> A> make sense to report down->down. This could indeed conf
Andre,
On Tue, Apr 19, 2005 at 11:49:36AM +0200, Andre Oppermann wrote:
A> > we are working on fixing LORs in if_link_state_change() path, and
A> > adding possibility to call if_link_state_change() pseudorecursively,
A> > when link of interface depends on link of the other.
A> >
A> > I'm postin
Gleb Smirnoff wrote:
>
> Dear networkers,
>
> we are working on fixing LORs in if_link_state_change() path, and
> adding possibility to call if_link_state_change() pseudorecursively,
> when link of interface depends on link of the other.
>
> I'm posting this patch for wider review. An importan
On Mon, 18 Apr 2005, Kris Kennaway wrote:
This on an u10 running
FreeBSD 5.3-STABLE (NETBOOT) #1: Sun Dec 12 18:38:35 JST 2004
It may already be fixed, but since this is clearly a very infrequent
problem (the other 7 machines with the same kernel have been running for
months) it will be hard to t
18 matches
Mail list logo
