On 2/10/2011 5:23 PM, Joe Holden wrote:
On 10/02/2011 15:56, Jeremy Chadwick wrote:
(I was considering cross-posting this to freebsd-pf but decided against
it, instead starting here first. Please keep me CC'd as I'm not
subscribed to freebsd-net)
I'm looking into the possibility of using my ho
On Mon, Jul 12, 2010 at 9:58 PM, Chris Buechler wrote:
> On Mon, Jul 12, 2010 at 5:24 AM, Jack Vogel wrote:
>> I've not heard anything yet, will see what happens later this morning.
>>
>
> Of the info I currently have, it doesn't panic on a stock 8.1-RC2, but
>
On Mon, Jul 12, 2010 at 5:24 AM, Jack Vogel wrote:
> I've not heard anything yet, will see what happens later this morning.
>
Of the info I currently have, it doesn't panic on a stock 8.1-RC2, but
it wasn't the same config - there weren't any VLANs configured. I'm
getting VLANs configured on the
On Fri, Jul 9, 2010 at 12:18 PM, Jack Vogel wrote:
> Is this kernel 32 bit?
It does exactly the same with 32 and 64 bit.
> And is my code altered, it seemed some debug I saw
> was
> not familiar.
Nothing in sys/dev/e1000 is changed. Copying Ermal who wrote most/many
of the changes. They don't t
On Fri, Jul 9, 2010 at 1:03 AM, Jack Vogel wrote:
> Damn, thats bad, and this is with what installed exactly, RC1, 2? I'll have
> someone in validation install to see if we can repro this tomorrow, let me
> know what it is asap.
>
Here are some pictures of the screen, with the backtrace, the ifco
On Fri, Jul 9, 2010 at 1:03 AM, Jack Vogel wrote:
> Damn, thats bad, and this is with what installed exactly, RC1, 2? I'll have
> someone in validation install to see if we can repro this tomorrow, let me
> know what it is asap.
>
This is RELENG_8_1 as of date=2010.06.25.00.00.00 It's pfSense 2.
On Thu, Jul 8, 2010 at 5:55 PM, Pyun YongHyeon wrote:
> On Thu, Jul 08, 2010 at 05:36:44PM -0400, Chris Buechler wrote:
>> On Thu, Jul 8, 2010 at 5:03 PM, Jack Vogel wrote:
>> > Am confused, does not the code in 8.1 have that fix, looked to me like it
>> > did?
>>
On Thu, Jul 8, 2010 at 5:03 PM, Jack Vogel wrote:
> Am confused, does not the code in 8.1 have that fix, looked to me like it
> did?
>
Maybe I'm confused, but it looks like RELENG_8_1 has the IGB_DBA_ALIGN
rather than 1.
-IGB_DBA_ALIGN, 0,/* alignment, bounds */
+
I'm seeing what appears to be the problem described in this thread with
the latest RELENG_8_1, reportedly fixed by this diff.
http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013258.html
Except that fix was reverted in r206211.
http://svn.freebsd.org/viewvc/base/releng/8.1/sys/de
one of our users has reported a regression in dc(4) on RELENG_8, the
cards work fine on 7.2 and previous versions, but no longer function
at all with RELENG_8 as of about a week ago.
http://forum.pfsense.org/index.php/topic,24964.msg129488.html#msg129488
dmesg from it working, from 7.2:
cbb0:
;/
> /
> No, there isn't any ARP at all on that address on the network when
> this is a problem, verified with tcpdump. That also shouldn't impact
> the system's ability to talk to its own IPs.
>
> thanks for the response though!
>
>
>> / - Original Mess
Hi,
VANHULLEBUS Yvan wrote:
Hi all.
We (NETASQ) had some IPsec related kernel crashes, and hunted them,
here are some informations and a possible patch:
First, problem only occurs when asynchronous crypto is done
(hardware encryption such as hifn cards, or software patch to do
encryption on a
Chris Buechler wrote:
somehow it ends up switching MTU to 2290 when we never configure it as
such. This breaks bridging to an Ethernet interface because if_bridge
requires the MTU to be the same on both interfaces.
For the sake of the archives and anyone who finds this thread in the
Chris Buechler wrote:
In FreeBSD 7.1 using this patch:
http://people.freebsd.org/~sam/ath_hal-releng7.patch
and 7.2 with stock ath(4) (the above does not cleanly apply to 7.2),
there are numerous pfsense users seeing problems with ath when
bridging. This did not occur in 7.0. Upon
In FreeBSD 7.1 using this patch:
http://people.freebsd.org/~sam/ath_hal-releng7.patch
and 7.2 with stock ath(4) (the above does not cleanly apply to 7.2),
there are numerous pfsense users seeing problems with ath when bridging.
This did not occur in 7.0. Upon investigation of a few systems, tho
houldn't impact
the system's ability to talk to its own IPs.
thanks for the response though!
> - Original Message - From: "Chris Buechler"
>
> To:
> Sent: Sunday, May 17, 2009 9:08 PM
> Subject: multi-homed systems stop answering ARP on local addresses
>
There seems to be a regression between 6.x and 7.0 and 7.1 related to
ifconfig aliases on multi-homed hosts. Not sure on anything newer than
7.1 (this is pfSense, we're just starting to test 7.2 builds). For
periods of time, the system will stop answering ARP on some of its own
addresses and he
The following reply was made to PR kern/127528; it has been noted by GNATS.
From: Chris Buechler
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/127528: [icmp]: icmp socket receives icmp replies not owned
by the process.
Date: Wed, 13 May 2009 23:08:05 -0400
A brief addition to
Chris Buechler wrote:
Has anyone ever tried connecting a Blackberry Bold to a FreeBSD access
point using an Atheros card? The card is an Atheros 5212, using
FreeBSD 7.0. Every other wireless device that has been tried on this
network works fine, but this Blackberry connects, gets a DHCP lease
Has anyone ever tried connecting a Blackberry Bold to a FreeBSD access
point using an Atheros card? The card is an Atheros 5212, using FreeBSD
7.0. Every other wireless device that has been tried on this network
works fine, but this Blackberry connects, gets a DHCP lease, and then
sends ARP re
The following reply was made to PR kern/127528; it has been noted by GNATS.
From: Chris Buechler <[EMAIL PROTECTED]>
To: "Bruce M. Simpson" <[EMAIL PROTECTED]>
Cc: freebsd-net@FreeBSD.org, [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: kern/127528: [icmp]: icmp socket rec
Bruce M. Simpson wrote:
[EMAIL PROTECTED] wrote:
Old Synopsis: icmp socket receives icmp replies not owned by the
process.
New Synopsis: [icmp]: icmp socket receives icmp replies not owned by
the process.
This PR is bogus because:
ICMP has no concept of datagrams being "owned" by a process
Chris Buechler wrote:
I've been seeing pretty frequent and repeatable scp stalls between two
FreeBSD 7.0 servers (7.0-RELEASE-p2 to be exact) on a 100 Mb LAN.
They're two HP servers, an Opteron 275 and a dual Xeon 3.4 (don't
recall the models but I can get them if it's
I've been seeing pretty frequent and repeatable scp stalls between two
FreeBSD 7.0 servers (7.0-RELEASE-p2 to be exact) on a 100 Mb LAN.
They're two HP servers, an Opteron 275 and a dual Xeon 3.4 (don't recall
the models but I can get them if it's relevant) using the onboard bge(4)
cards. The c
Sam Leffler wrote:
John T. Yocum wrote:
Hello,
I have a system running pfSense, which is built on top of FreeBSD
7.0-RELEASE-p3. In the system I have an Atheros wireless card, which
when I enable hostap, changes it's MTU to 2290. If an explanation is
listed on a man page, I apologize, I did
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
26 matches
Mail list logo
