https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706
Eugene Grosbein changed:
What|Removed |Added
Resolution|--- |Overcome By Events
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706
Lutz Donnerhacke changed:
What|Removed |Added
Status|New |Open
--- Comment #1 from Lutz D
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706
Bug ID: 246706
Summary: [netgraph] kernel panic due to corrupted memory
Product: Base System
Version: 11.3-STABLE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236383
Eugene Grosbein changed:
What|Removed |Added
Attachment #202920|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236383
Eugene Grosbein changed:
What|Removed |Added
Summary|[netgaph] Kernel panic |[netgraph] Kernel panic
Synopsis: [netgraph] kernel panic, when getting info about my traffic by module
ng_ipacct and oppenning www page in browser
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: vwe
Responsible-Changed-When: Wed Jan 14 23:30:06 UTC 2009
Responsible-Changed-Why:
Over
Hello,
When trying to use a netgraph ksocket for a tcp connection, we get a
kernel panic on opening the connection. The panic is a result of a
KASSERT() on the value of a flag which we don't set ourselves and which
we don't appear to have control over.
Details of our investigation follow. What ca
Scott Lamb writes:
> > If you have time, please try applying the patch below to your kernel.
> > Leave the mpd configuration as it was, and let's see if we get a
> > normal error instead of a kernel panic (I don't have a test setup
> > for this myself just now).
>
> Yep. I get this message when I
On Fri, Jan 04, 2002 at 08:20:23PM -0800, Archie Cobbs wrote:
> If you have time, please try applying the patch below to your kernel.
> Leave the mpd configuration as it was, and let's see if we get a
> normal error instead of a kernel panic (I don't have a test setup
> for this myself just now).
Archie Cobbs writes:
> > Taking out my "set iface route" lines in mpd.conf made it no longer
> > crash and I can talk to just the VPN host. So I tried next a "route add
> > vpnhost mygw" before starting the VPN. It worked. So that's definitely
> > the problem. It would be nice if there were a sli
Scott Lamb writes:
> Looks like I have a slightly different situation than you're describing.
> I'm not specifying a "set ipcp ranges" anywhere. The peer chooses an
> inside address that's different from but within the same /24 as its
> outside address. I'm trying to run everything within two /16
Looks like I have a slightly different situation than you're describing.
I'm not specifying a "set ipcp ranges" anywhere. The peer chooses an
inside address that's different from but within the same /24 as its
outside address. I'm trying to run everything within two /16s over the
VPN (which inclu
Scott Lamb writes:
> FreeBSD 4.5-PRERELEASE (as of a few days ago) is crashing consistently
> when I try to initiate a PPTP connection to with mpd-netgraph 3.3 (from
> ports).
This is due to a problem caused by the peer's "outside" PPTP IP address
(the one from mpd.links) being equal to its "insi
Hi,
FreeBSD 4.5-PRERELEASE (as of a few days ago) is crashing consistently
when I try to initiate a PPTP connection to with mpd-netgraph 3.3 (from
ports).
mpd ups the interface happily:
mpd: [vpn] IPCP: rec'd Configure Ack #3 link 0 (Ack-
Sent)
mpd: IPADDR a.b.c.d
mpd: [vpn] IP
16 matches
Mail list logo
