Hi,
Sat, Jun 26, 2010 at 21:30:12, tuexen wrote about "Re: SCTP panic with
sctp_send()":
> > As seen from code, if uap->tolen is zero, `to' isn't initialized and remains
> > NULL. This error is identical to -CURRENT.
> Thanks for reporting it. It is fixed in r209540 for current.
Thanks! (for
Hi,
Sat, Jun 26, 2010 at 17:11:13, tuexen wrote about "Re: SCTP panic with
sctp_send()":
> > As seen from code, if uap->tolen is zero, `to' isn't initialized and remains
> > NULL. This error is identical to -CURRENT.
> How can the crash be reproduced?
Any code with sctp_send() under ktrace.
Hi,
FreeBSD 7.3-RELEASE i386
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc05955ca
stack pointer = 0x28:0xe783bb94
frame pointer = 0x28:0xe783bc80
code
The following reply was made to PR kern/136803; it has been noted by GNATS.
From: Valentin Nechayev
To: Bruce Cran
Cc: bug-follo...@freebsd.org
Subject: Re: kern/136803: [sctp] [panic] Kernel panic and hanging on using
SCTP
Date: Sat, 8 Aug 2009 10:06:06 +0300
Hi,
Fri, Aug 07
Fri, Nov 16, 2007 at 02:40:01, kmacy wrote about "Re: kern/21998: [socket]
[patch] ident only for outgoing connections":
> Need to confirm that this issue still applies.
Yes, nothing is changed (at least for versions known to me)
> http://www.freebsd.org/cgi/query-pr.cgi?pr=21998
-netch-
___
Mon, Dec 06, 2004 at 18:21:05, josemi wrote about "Re: FreeBSD kernel pppd -
mppe/mschapv1/2/radius support":
>> MPPE isn't possible due to lack of support in kernel for PPP terminal
>> discipline.
>> For others, you can use port (net/pppd23) as base. This is the most
>> reasonable variant now
Fri, Nov 26, 2004 at 13:24:31, anthonyv wrote about "FreeBSD kernel pppd -
mppe/mschapv1/2/radius support":
> After extensively googling FreeBSD pppd's support for mppe, mschapv1,
> mschapv2 and radius, I've stumbled into a mess of patches for very random
> versions of pppd and FreeBSD.
> Does
Hi,
Mon, Nov 29, 2004 at 19:15:29, glebius wrote about "Re: route cacheing for
gif(4) should be optional":
A>> However there have been reasons for
A>> storing the rtentry pointer in struct gif. In the old days ip_output()
A>> required an rtentry pointer to be passed on, this is no longer the
Wed, Sep 22, 2004 at 05:07:13, jinmei wrote about "Re: freeaddrinfo(NULL)":
> I was not talking about things like whether NULL had been specially
> designed or not. I was basically talking about any invalid argument
> to freeaddrinfo.
Well, garbage in pointer is unquestionably invalid, but whe
Wed, Sep 22, 2004 at 03:58:05, jinmei wrote about "Re: freeaddrinfo(NULL)":
> As Umemoto-san said, if we made freeaddrinfo(NULL) "safe", the
> application programmers might tend to rely on the "safety net" and
> the uncareful coding style. This can be worse than the segfault here,
Let you try
Fri, Sep 10, 2004 at 12:58:26, brooks wrote about "Re: original interface name?
(5.*)":
>> Device number among with driver name are enough to determine needed
>> information based on driver information and boot logs.
>> It is pointless to use interface without such information, and it is pointl
Fri, Sep 10, 2004 at 21:30:11, max wrote about "Re: original interface name? (5.*)":
>> Hi,
>> is there a stable way to determine original interface name (before
>> any renaming) in 5.3? I.e. as driver + sequence number?
> From inside the kernel you can use ifnet.if_dname + ifnet.if_dunit, from
Hi,
is there a stable way to determine original interface name (before
any renaming) in 5.3? I.e. as driver + sequence number?
-netch-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail
Thu, Mar 25, 2004 at 01:59:34, fjoe (Max Khon) wrote about "race condition in ipfw
restart (please review the fix)":
MK> ipfw restart has race condition: there is "sleep 2" statement after
MK> killall natd but if natd will not die in 2 seconds ipfw can't
MK> start nat daemon (natd: Unable to bi
Trying to set up ipsec'ed tunnel with explicit routing to it.
Having 2 FreeBSD's (quarta - 4.9, grizzly - 5.2.1).
[EMAIL PROTECTED]:~>>
# ifconfig gre0
gre0: flags=9051 mtu 1476
tunnel inet 193.193.193.138 --> 193.193.193.11
inet 10.0.0.2 --> 10.0.0.1 netmask 0x
[EMAIL PRO
What is the difference between ssh protocol 1 and protocol 2 stream control?
I tried protocol 1 in openssh and protocol 2 in openssh and Ylonen's
SSH 2.3.0 via PSTN 56K line. With protocol 1 interactive delays are
reasonable. With protocol 2, in both openssh and Ylonen's ssh,
delays are unreasonab
16 matches
Mail list logo
