Angelo Turetta wrote:
Joe Holden wrote:
Hi collective,
It's an Athlon 64 board, with an MCP51 NIC, this card is supported
under Linux using the forcedeth driver, having taken a look at
if_nve.c, it doesn't appear to be supported.
It's supported by the nfe(4) driver, which has already been
Hi folks,
FreeBSD-6.2-amd64
Onboard NIC
Motherboard ASUS M2N-E
[url]http://www.excaliberpc.com/ASUS_M2N-E_nForce570_Ultra_Motherboard/M2N-E/partinfo-id-567211.html[/url]
Fixed IP address
IP address of server (LAN) - 192.168.0.10
Just finished standard installation to install the captioned OS.
I'd like to know the status of the iwi driver vs. iwiNG. I've been
using iwiNG for some time now and I don't see any notes in the CVS log
of iwi that the changes have been merged.
Dave.
--
|David Gilbert, Independent
Richard Tector wrote:
Or perhaps it doesn't. All I can remember is it requires the bpf
netgraph module.
ng_bpf is not from this opera. It does just packets filtering by
bpf-like filter program and it is not related to interfaces and traffic
capturing.
--
Alexander Motin [EMAIL PROTECTED]
Hi.
Alex Povolotsky wrote:
mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to reset.
Tried two completely different boxes, so it cannot be a hardware problem.
I'm updating to 6.2 now, but have little hope. What can I turn on in
kernel to fix it or at least to make computer
Alex Povolotsky пишет:
mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to reset.
Tried two completely different boxes, so it cannot be a hardware problem.
It's easy to reproduce? Can you try make debug-friendly kernel?
[ Removing -stable from CC ]
On Monday 19 February 2007 15:57, Alex Povolotsky wrote:
mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to
reset. Tried two completely different boxes, so it cannot be a hardware
problem.
I'm updating to 6.2 now, but have little hope. What can I
Alex Povolotsky wrote:
Richard Tector wrote:
Alex Povolotsky wrote:
Richard Tector wrote:
Alex Povolotsky wrote:
mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to
reset. Tried two completely different boxes, so it cannot be a
hardware problem.
Which version of mpd are you
Is it possible to tweak various TCP timeouts in FreeBSD 6.2? Such as:
how long a connection can stay in a FIN_WAIT_2 state.
TIA
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any
Joe Holden wrote:
Hi collective,
It's an Athlon 64 board, with an MCP51 NIC, this card is supported under
Linux using the forcedeth driver, having taken a look at if_nve.c, it
doesn't appear to be supported.
It's supported by the nfe(4) driver, which has already been committed to
satimis wrote:
Hi folks,
FreeBSD-6.2-amd64
...
The onboard NIC seems not detected.
In the absence of required information, I speculate your machine has
msk(4) or another recent chipset which may be supported in
FreeBSD-CURRENT but not FreeBSD-STABLE.
Please post the full output of
On Mon, Feb 19, 2007 at 12:02:45PM -0500, David Gilbert wrote:
I'd like to know the status of the iwi driver vs. iwiNG. I've been
using iwiNG for some time now and I don't see any notes in the CVS log
of iwi that the changes have been merged.
what/where is iwiNG ?
luigi
On Tuesday 20 February 2007 15:23, Luigi Rizzo wrote:
On Mon, Feb 19, 2007 at 12:02:45PM -0500, David Gilbert wrote:
I'd like to know the status of the iwi driver vs. iwiNG. I've been
using iwiNG for some time now and I don't see any notes in the CVS
log of iwi that the changes have been
Andrey V. Elsukov wrote:
Alex Povolotsky пишет:
mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to
reset. Tried two completely different boxes, so it cannot be a
hardware problem.
It's easy to reproduce? Can you try make debug-friendly kernel?
RELATIVELY easy. It happens about
At 11:35 AM 2/20/2007, Alex Povolotsky wrote:
Thanks a lot, I've added invariants and witness; if it won't yield
any information, I'll try more.
So far, this cursed thing is working with some load for 2 hours,
that's much. It does NOT, surely NOT try to tunnel tunnelled
traffic; any
Mike Tancsa wrote:
At 11:35 AM 2/20/2007, Alex Povolotsky wrote:
Thanks a lot, I've added invariants and witness; if it won't yield
any information, I'll try more.
So far, this cursed thing is working with some load for 2 hours,
that's much. It does NOT, surely NOT try to tunnel tunnelled
Sten Daniel Soersdal wrote:
Richard Tector wrote:
Alex Povolotsky wrote:
Richard Tector wrote:
Alex Povolotsky wrote:
mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to
reset. Tried two completely different boxes, so it cannot be a
hardware problem.
Which version of mpd are
Ian Smith wrote:
On Mon, 19 Feb 2007, admin wrote:
Ian Smith wrote:
On Mon, 19 Feb 2007, admin wrote:
Andre Santos wrote:
On 2/18/07, admin [EMAIL PROTECTED] wrote:
Hi, I'm trying to use ipfw's limit clause to limit the number of
connections a single IP can
Anyone out there running IS-IS on a FreeBSD machine, please contact me.
It's my understanding that IS-IS requires link-layer multicast support.
Therefore I would like to hear from anyone who is running an
implementation of it on FreeBSD successfully. I want to make sure it
continues to
admin wrote:
Wrong: the implied check-state done by the limit lets the connection
through (i.e. performs the action) iff there's state recorded for it
(src-addr+src-port+dst-addr+dst-port). If however it's a SYN packet
incoming and the number of current states is trying to cross the limit,
Here is a better patch for the netstat output. I haven't had time to
look at the kernel yet.
If this patch is good for you I'll commit it on -CURRENT. It cleans up
the group membership output significantly and displays the Link-layer
information separately.
If anyone 'out there' has been
Hello!
Is there anybody here who can say I'm running mpd with 400 pptp
connections, and it works without a flaw?
I mean 400 ACTIVE connections.
If yes, I'll ask lots of questions. If no, I'll have to look for other
pptp server. Cannot afford CISCO right now.
Alex.
On Tue, 20 Feb 2007, Julian Elischer wrote:
admin wrote:
Wrong: the implied check-state done by the limit lets the connection
through (i.e. performs the action) iff there's state recorded for it
(src-addr+src-port+dst-addr+dst-port). If however it's a SYN packet
incoming and
23 matches
Mail list logo
