All,
As a follow up to myself I installed an Intel PCIe NIC and disabled the on
board RTL based one and all my problems went away. Been running with 4GB
installed for a couple days now with absolutely no network issues. So seems
like there's some problem with RTL NICs and >= 4GB of RAM.
--
Paul H
Petar Bogdanovic wrote:
Hi,
I'm using an alix2c0 board with two winstron CM9 ath(4)-cards and
FreeBSD 7:
ifconfig ath0 (...) mediaopt hostap mode 11a channel 36 ssid sn.a
-bgscan
ifconfig ath1 (...) mediaopt hostap mode 11g channel 11 ssid sn.g
-bgscan
When I try to raise th
> > I'm trying to build the "bce" driver as a kernel module under
> RELENG_7 but I'm
> > finding that not all of the functions in the driver are exported as
> symbols. This
> > makes it difficult to "call" a function from ddb because I get the
> error "Symbol
> > not found". I'm building and l
John Hay wrote:
You don't need to go to the kernel for this sort of thing unless you
specifically need to implement route policy based on which interface(s)
a packet came in on.
Yes I know that. But in the world of adhoc wireless mesh networking
there are very few non-linux people, so the
Julian Elischer wrote:
OLSR is an overlay network
Nope -- the express intention was that it could be used for basic IP
connectivity, for mobile devices. In OLSR, every node is a potential IP
forwarder unless it explicitly advertises itself as being unwilling to
forward.
and any machine th
Old Synopsis: Enabling samba wins in nsswitch.conf causes sshd, ftpd, etc
services to die
New Synopsis: [nsswitch] Enabling samba wins in nsswitch.conf causes sshd,
ftpd, etc services to die
Responsible-Changed-From-To: freebsd-i386->freebsd-net
Responsible-Changed-By: linimon
Responsible-Change
On Thu, May 1, 2008 at 10:04 PM, David Christensen <[EMAIL PROTECTED]> wrote:
> I'm trying to build the "bce" driver as a kernel module under RELENG_7 but I'm
> finding that not all of the functions in the driver are exported as symbols.
> This
> makes it difficult to "call" a function from ddb
Mark Hills wrote:
On Wed, 23 Apr 2008, Andre Oppermann wrote:
http://people.freebsd.org/~andre/tcp_output-error-log.diff
Please apply this patch and enable the sysctl net.inet.tcp.log_debug=1
and report any output. You likely get some (normal) noise from syncache.
What we are looking for is r
Julian Elischer wrote:
John Hay wrote:
This confuses me
The whole point of a FIB is to decide the *next* hop for a
given input packet. So questions.
1) A packet arrives on an interface. If this interface is
associated with more than one FIB, which FIB does it get
given to?
which ever
John Hay wrote:
This confuses me
The whole point of a FIB is to decide the *next* hop for a
given input packet. So questions.
1) A packet arrives on an interface. If this interface is
associated with more than one FIB, which FIB does it get
given to?
which ever one you select, using t
On Fri, May 02, 2008 at 04:44:20PM +0100, Bruce M. Simpson wrote:
> John Hay wrote:
> >The linux guys seems to have multiple fibs (or whatever they call them)
> >which they can chain together by giving them different priorities. The
> >effect seems to be that a packet will be matched through the hi
John Hay wrote:
The linux guys seems to have multiple fibs (or whatever they call them)
which they can chain together by giving them different priorities. The
effect seems to be that a packet will be matched through the highest
priority fib to the lowest until a route match is found en then is us
Hi,
I'm using an alix2c0 board with two winstron CM9 ath(4)-cards and
FreeBSD 7:
ifconfig ath0 (...) mediaopt hostap mode 11a channel 36 ssid sn.a
-bgscan
ifconfig ath1 (...) mediaopt hostap mode 11g channel 11 ssid sn.g
-bgscan
When I try to raise the traffic (i.e. dd | ssh A
Synopsis: [bce] On board second lan port 'bce1' with Broadcom NetXtreme II
BCM5708 1000Base-T 0.9.6 driver in Dell 1950 and 2950 behave super slow
State-Changed-From-To: feedback->closed
State-Changed-By: vwe
State-Changed-When: Fri May 2 09:47:48 UTC 2008
State-Changed-Why:
We're sorry to not
> >This confuses me
> >
> >The whole point of a FIB is to decide the *next* hop for a
> >given input packet. So questions.
> >1) A packet arrives on an interface. If this interface is
> > associated with more than one FIB, which FIB does it get
> > given to?
> >
>
> which ever one you sel
15 matches
Mail list logo
