On Oct 31, 2007, at 9:50 AM, Garrett Cooper wrote:
Garrett Cooper wrote:
Tom Judge wrote:
Garrett Cooper wrote:
Mike Silbersack wrote:
On Fri, 19 Oct 2007, Garrett Cooper wrote:
Just to clarify, how are the two hooked together? Is it over
gigabit switch, a 10mbps hub, or directly cabled
Current FreeBSD problem reports
Critical problems
S Tracker Resp. Description
o kern/115360 net[ipv6] IPv6 address and if_bridge don't play well toge
1 problem total.
Serious problems
S Tracker
Hi,
Just to close this thread - I've confirmed that it was indeed a switch
problem.
The "funny" thing, is howcome only CARP triggered it.
On Thu, October 18, 2007 9:33, Klavs Klavsen said:
> Hi guys,
>
> I have had a FreeBSD 6.2 (-p1 - yes I know :) firewall running for a
> while, with pf fw rul
Hi guys,
I can see that there's been problems in the past with CARP and vlan support.
I would be happy, if you could tell me if you have any experience with
running carp on vlan interfaces?
I intend to run it on a FreeBSD 6.2 with em interfaces. This works fine
for another firewall, but it has n
On Monday 05 November 2007 08:59:39 Klavs Klavsen wrote:
> Hi,
>
> Just to close this thread - I've confirmed that it was indeed a switch
> problem.
>
> The "funny" thing, is howcome only CARP triggered it.
>
Out of curiosity - could you tell me the model? I have similar trouble, not
yet confirme
hi
I implemented SIOCGIFINDEX in linuxulator and I would like you
to review the patch.. the implementation is trivial, just mapping
it to the native fbsd call.
the patch can be found here: http://www.vlakno.cz/~rdivacky/linux_socket.patch
I have a report that it helps some java program. please r
On Mon, Nov 05, 2007 at 04:34:59PM +0100, Roman Divacky wrote:
> hi
>
> I implemented SIOCGIFINDEX in linuxulator and I would like you
> to review the patch.. the implementation is trivial, just mapping
> it to the native fbsd call.
>
> the patch can be found here: http://www.vlakno.cz/~rdivacky/
On Nov 5, 2007, at 07:05, Klavs Klavsen wrote:
Hi guys,
I can see that there's been problems in the past with CARP and vlan
support.
I would be happy, if you could tell me if you have any experience with
running carp on vlan interfaces?
I intend to run it on a FreeBSD 6.2 with em interfac
Klavs Klavsen wrote:
Hi,
Just to close this thread - I've confirmed that it was indeed a switch
problem.
The "funny" thing, is howcome only CARP triggered it.
Because CARP uses multicast, and there are a ton of buggy and/or
misconfigured switches out there that break, block, or are otherw
Hello folks,
I'd really like to get this done soon. I've been using it locally and I
think it's ready for wider testing. The patch is at:
http://people.freebsd.org/~mtm/src-etc.ipv6.diff
I'll quickly summarize the changes, but there's a longer explanation
attached to the patch.
The main goal
I've been working on doing some bandwidth accounting with ipfw count
rules, but I've come across a very crappy problem. After adding the
following two lines to /etc/rc.conf, I'm posed with a question during
boot:
Loading divert daemons are you sure [yn]:
And there it sits, forever, waitin
On 11/5/07, Mike Makonnen <[EMAIL PROTECTED]> wrote:
> Most IP related knobs will have an ipv4_ and ipv6_ version. To make the
> transition easier rc.subr(8) will "automagically" DTRT for the following
> knobs:
> gateway_enable => ipv4_gateway_enable
> router_enable => ipv
Garrett Cooper wrote:
On Oct 31, 2007, at 9:50 AM, Garrett Cooper wrote:
I'm running tcpdump on my Mac and I noted a lot of 'bad checksums'
(0x081c was the official error in all cases), then consulted the msk
driver. It appears that there's a bug with Yukon II chipsets with the
hardware checks
FreeBSD 4.x, netstat -m:
70/4336/26624 mbufs in use (current/peak/max)
Never any doubt - if peak=max, I hit the limit. Super
useful. Furthermore, by watching the peak I can see
when I am getting close, rather than waiting for
denied requests to pile up after the fact.
FreeBSD 6.x, netstat -m:
Eric F Crist wrote:
I've been working on doing some bandwidth accounting with ipfw count
rules, but I've come across a very crappy problem. After adding the
following two lines to /etc/rc.conf, I'm posed with a question during boot:
Loading divert daemons are you sure [yn]:
About which lines
15 matches
Mail list logo
