On Sun, Jan 17, 2010 at 12:04:43PM +0100, Luigi Rizzo wrote:
> On Sun, Jan 17, 2010 at 05:42:58PM +0900, Hajimu UMEMOTO wrote:
> > Hi,
> >
> > > On Sun, 10 Jan 2010 19:52:32 +0100
> > > Luigi Rizzo said:
> >
> > rizzo> We only need one 'me' option that matches v4 and v6, because the
> >
Synopsis: [ipsec] [patch] IPSec doesn't work with link-local addresses on
FreeBSD 6
Responsible-Changed-From-To: freebsd-net->bz
Responsible-Changed-By: bz
Responsible-Changed-When: Tue Jan 19 07:34:08 UTC 2010
Responsible-Changed-Why:
This is mine; I have looked before.
http://www.freebsd.org/
The following reply was made to PR bin/142547; it has been noted by GNATS.
From: Kevin Dorne
To: James McNaughton
Cc: bug-follo...@freebsd.org
Subject: Re: bin/142547: wpa_supplicant(8) drops connection on key
renegotiation
Date: Mon, 18 Jan 2010 22:31:18 -0800
On Mon, Jan 18, 2010 at 09:23:1
On Tue, Dec 15, 2009 at 04:03:31PM -0500, Steven Friedrich wrote:
> Ok, I am able to load firmware with:
> uathload -d /dev/ugen4.3
> but it also appears to do so when I plug it in...
>
> Now what? It doesn't show up in ifconfig...
I think this problem is fixed in r202607. Please let me know if
Old Synopsis: IPSec doesn't work with link-local addresses on FreeBSD 6
New Synopsis: [ipsec] [patch] IPSec doesn't work with link-local addresses on
FreeBSD 6
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Jan 18 22:32:41 UTC
On Sun, Jan 17, 2010 at 5:02 PM, Brett Lee wrote:
> Brett Lee wrote:
>>
>> Hello -
>>
>> Am using FreeBSD 6.3 as a dhcp6 client, trying to get DDNSv6 operational
>> in this environment. When I execute 'dhcp6c -d lnc0' from the command line,
>> the following messages are logged on the (ISC 4.1.0p1
Pyun YongHyeon wrote:
> On Mon, Jan 18, 2010 at 10:40:55AM -0500, Charles Owens wrote:
>> Hello,
>>
>> I'm working with a system (IBM System x3550 M2) that has four onboard
>> bce(4) NICs. Using FreeBSD 8.0, the first two seem to function fine,
>> but the second two do not, yielding messages like
> > I'm working with a system (IBM System x3550 M2) that has
> four onboard
> > bce(4) NICs. Using FreeBSD 8.0, the first two seem to
> function fine,
> > but the second two do not, yielding messages like this when
> a cable is
> > inserted:
> >
> > Jan 12 10:37:19 dmz55 kernel: <2<>N2M>NINM
Synopsis: [lagg] tcpdump on lagg interface during high pps wedges netcode
State-Changed-From-To: open->feedback
State-Changed-By: emaste
State-Changed-When: Mon Jan 18 20:54:42 UTC 2010
State-Changed-Why:
Results of testing on more recent 7.x (or newer branch) requested
http://www.freebsd.org/cg
Synopsis: [vlan] [patch] handle parent interface link layer address changes in
if_vlan(4)
State-Changed-From-To: open->patched
State-Changed-By: thompsa
State-Changed-When: Mon Jan 18 20:35:53 UTC 2010
State-Changed-Why:
Committed, thanks!
Responsible-Changed-From-To: freebsd-net->thompsa
Resp
Synopsis: [bge] Broadcom 5715S no carrier on HP BL460c blade using 6.3-RELEASE
State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Mon Jan 18 20:32:13 UTC 2010
State-Changed-Why:
I've committed patch to address this(r202293, r202294). Would you
try latest bge(4) an
On Mon, Jan 18, 2010 at 10:40:55AM -0500, Charles Owens wrote:
> Hello,
>
> I'm working with a system (IBM System x3550 M2) that has four onboard
> bce(4) NICs. Using FreeBSD 8.0, the first two seem to function fine,
> but the second two do not, yielding messages like this when a cable is
> inser
Hello,
I'm working with a system (IBM System x3550 M2) that has four onboard
bce(4) NICs. Using FreeBSD 8.0, the first two seem to function fine,
but the second two do not, yielding messages like this when a cable is
inserted:
Jan 12 10:37:19 dmz55 kernel: <2<>N2M>NINM IM INISMI AI S AIIS SAA
22
Jeff Blank wrote:
> I wrote:
>> I've just upgraded a 7.1-REL server to 8.0-REL and have lost my
>> ability to use vlan(4) on top of lagg(4) on top of em(4).
A workaround for this is to disable hardware vlan tagging:
# ifconfig em0 -vlanhwtag
(don't forget to do all em interfaces and put it in rc
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
15 matches
Mail list logo