On Sun, 28 Dec 2008, Tijl Coosemans wrote:
> On Saturday 27 December 2008 21:21:25 Qing Li wrote:
>> I believe all of the affected ports have been updated to
>> include the conditional blocks around RTF_LLINFO.
emulators/wine has not been adjusted yet, pending this discussion.
> Yes, and I'm OK
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
_
From: Eygene Ryabinkin [mailto:rea-f...@codelabs.ru]
To: Gerry Weaver [mailto:ger...@compvia.com]
Cc: freebsd-net@freebsd.org
Sent: Mon, 29 Dec 2008 01:10:37 -0600
Subject: Re: pfil + if_bridge hooks not being called
Gerry, good day.
Sun, Dec 28, 2008 at 07:59:57PM -0600, Gerry Weave
Anyone know what causes this error message?
+ipsec_common_input: no key association found for SA 69.x.x.x[0]/04e317a1/50
+ipsec_common_input: no key association found for SA 69.x.x.x[0]/04e317a1/50
+ipsec_common_input: no key association found for SA 69.x.x.x[0]/04e317a1/50
+ipsec_common_input: n
Hi all,
I have been working with SCTP and more specifically with the mobility
features of SCTP at my work. Basically, I have been trying to use SCTP
to perform handover tests between 2 separate Wifi networks. I use IPv6
for all my tests.
I have a local LAN (wired-network), on which I have 3 machi
On Mon, 29 Dec 2008, Gabe wrote:
Anyone know what causes this error message?
+ipsec_common_input: no key association found for SA 69.x.x.x[0]/04e317a1/50
from what I remember without looking, this means that you ahve an
IPsec policy for src/dst but no SA matching this pair or rather no
matchi
Hi,
are both machines (T and you PC) running FreeBSD?
Best regards
Michael
On Dec 29, 2008, at 12:33 PM, > wrote:
Hi all,
I have been working with SCTP and more specifically with the mobility
features of SCTP at my work. Basically, I have been trying to use SCTP
to perform handover tests b
On Mon, 29 Dec 2008, Bjoern A. Zeeb wrote:
On Mon, 29 Dec 2008, Gabe wrote:
Anyone know what causes this error message?
+ipsec_common_input: no key association found for SA
69.x.x.x[0]/04e317a1/50
from what I remember without looking, this means that you ahve an
IPsec policy for src/dst bu
Hello M.Tüxen,
No, only the PC is running under FreeBSD 7.0. T is running under Linux (kernel
version is 2.6.21 and the distribution used is Fedora Core 7). SCTP is running
on T thanks to the lksctp implementation, we loaded the sctp module on it and
made the necessary configurations so that i
> From: Bjoern A. Zeeb
> To: Gabe
> Cc: freebsd-net@freebsd.org
> Sent: Monday, December 29, 2008 5:19:16 AM
> Subject: Re: +ipsec_common_input: no key association found for SA
>
> On Mon, 29 Dec 2008, Bjoern A. Zeeb wrote:
>
> > On Mon, 29 Dec 2008, Gabe wrote:
> >
> >> Anyone know what causes
> To: Bjoern A. Zeeb
> Cc: freebsd-net@freebsd.org
> Sent: Monday, December 29, 2008 6:18:36 AM
> Subject: Re: +ipsec_common_input: no key association found for SA
>
> > From: Bjoern A. Zeeb
> > To: Gabe
> > Cc: freebsd-net@freebsd.org
> > Sent: Monday, December 29, 2008 5:19:16 AM
> > Subject:
Gabe wrote:
>
> spdadd 192.168.10.0/24 192.168.20.0/24 any -P out ipsec
> esp/tunnel/box-box2/unique;
> spdadd 192.168.20.0/24 192.168.10.0/24 any -P in ipsec
> esp/tunnel/box-box2/unique;
One or the other of these should have "box2-box" in place of "box-box2".
Though this may just be an infor
Hi Aman,
I'm not that familiar with the Linux box configuration. If you
look at the INIT/INIT-ACK exchange, does the Linux box support
ASCONF and the SCTP-AUTH extension? Both are required...
Best regards
Michael
On Dec 29, 2008, at 2:36 PM, > wrote:
Hello M.Tüxen,
No, only the PC is runni
Hello M.Tüxen,
I performed a quick test and at the INIT/INIT-ACK exchange, I noticed the
following :
- In the INIT chunk, the Supported Extensions Parameter field indicates that
ASCONF, ASCONF-ACK, FORWARD-TSN, PKTDROP, STREAM_RESET and AUTH are supported
- In the INIT-ACK chunk, there is no f
Hi Aman,
comments in-line.
Best regards
Michael
On Dec 29, 2008, at 6:12 PM, > wrote:
Hello M.Tüxen,
I performed a quick test and at the INIT/INIT-ACK exchange, I
noticed the following :
- In the INIT chunk, the Supported Extensions Parameter field
indicates that ASCONF, ASCONF-ACK,
Kayven Riese wants to add you as a connection on Plaxo.
To accept this connection request, go to:
http://www.plaxo.com/invite?i=55229637&k=947635066&l=en&src=email&et=1&est=nolevels&etv=nnic1b2&el=en
Thanks!
The Plaxo team
More than 20 million people use Plaxo to keep in touch with the
people
On Mon, 29 Dec 2008, Gabe wrote:
This is what setkey -Da returns:
box# setkey -Da
Invalid extension type
Invalid extension type
box#
you are running with the NAT-T patch (as I see you say further down).
Try /usr/local/sbin/setkey -Da in that case.
--
Bjoern A. Zeeb The g
On Wed, 24 Dec 2008, Yony Yossef wrote:
I'm facing lots of UDP "Connection refused" errors while running multistream
iperf test. Analyzing it with wireshark showed several "ICMP Port
Unreachable" problems.
I've overriden it with "sysctl net.inet.udp.blackhole=1", but I'm not sure
this is th
On Mon, 29 Dec 2008, Gabe wrote:
I guess more importantly would be the ipsec configuration:
spdadd 192.168.10.0/24 192.168.10.165/32 any -P in none;
spdadd 192.168.10.165/32 192.168.10.0/24 any -P out none;
spdadd 192.168.10.0/24 192.168.20.0/24 any -P out ipsec
esp/tunnel/box-box2/unique;
sp
On Mon, 29 Dec 2008, Bjoern A. Zeeb wrote:
On Mon, 29 Dec 2008, Gabe wrote:
This is what setkey -Da returns:
box# setkey -Da
Invalid extension type
Invalid extension type
box#
you are running with the NAT-T patch (as I see you say further down).
Try /usr/local/sbin/setkey -Da in that case.
20 matches
Mail list logo
