Hi all,
I would like to have some of the configuration parameters of my driver
to be present as part of the /boot/device.hints file. After adding a
variable I could see that variable and it's value as part of kevn's
ouput.
Can any one please let me know how to access the value of these
varia
On Mon, Sep 18, 2006 at 11:46:09PM +0200 I heard the voice of
Julian Stacey, and lo! it spake thus:
>
> I'd been wondering why I was the first person to notice the problem.
Actually, I noticed it a while back (6 months or so? Something like
that...) when I tried to run pppctl from my workstation
Hi,
> On Mon, 18 Sep 2006 23:46:09 +0200 (CEST)
> "Julian Stacey" <[EMAIL PROTECTED]> said:
jhs> I'd been wondering why I was the first person to notice the problem.
I'm not sure why there was no report about it, but I had never been
using inet socket. I don't want to open inet socket f
> Tested. It Works. Thanks !
> I tested the patch on PPP running under both kernels IPV4+6 & V4only
> just to be sure, it works on both, & allows me to type dial & down
> (all I tried or wanted.)
I'd been wondering why I was the first person to notice the problem.
Then I noticed my kernel (unlike
On 18 Sep 2006 18:00:53 -, Larry Baird <[EMAIL PROTECTED]> wrote:
>From my testing on a new 6.x box I just set up, I was wondering if
this was the step that was being left out. Glad to hear it was something
easy.
Thanks for all of the help, I am now up and running after the
installworld.
On Mon, Sep 18, 2006 at 09:43:41PM +0200, Joerg Pulz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Hi,
>
> first of all, a big thanks to Yvan and Larry, and all others, for their
> work. IPSEC_NAT_T is working fine for me with either IPSEC or FAST_IPSEC
> with RELENG_6 as serv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
first of all, a big thanks to Yvan and Larry, and all others, for their
work. IPSEC_NAT_T is working fine for me with either IPSEC or FAST_IPSEC
with RELENG_6 as server and FAST_IPSEC with CURRENT (small modifications
after patching where nec
In article <[EMAIL PROTECTED]> you wrote:
> On Mon, 18 Sep 2006, Scott Ullrich wrote:
>
>> 1. Reinstalled kernel with NAT-T support
>
> you need to re-install the includes/header files too (which is part of
> installworld).
>From my testing on a new 6.x box I just set up, I was wondering if
this
On 9/18/06, Bjoern A. Zeeb <[EMAIL PROTECTED]> wrote:
On Mon, 18 Sep 2006, Scott Ullrich wrote:
> 1. Reinstalled kernel with NAT-T support
you need to re-install the includes/header files too (which is part of
installworld).
Okay, now that makes more sense. For the record, I am using FreeSBI
On Mon, 18 Sep 2006, VANHULLEBUS Yvan wrote:
On Mon, Sep 18, 2006 at 03:04:04PM +, Bjoern A. Zeeb wrote:
On Mon, 18 Sep 2006, VANHULLEBUS Yvan wrote:
By default in FreeBSd's port, NAT-T support is enabled if support is
detected on the system (checks for some structs in
include/net/pfkeyv2
On Mon, 18 Sep 2006, Scott Ullrich wrote:
1. Reinstalled kernel with NAT-T support
you need to re-install the includes/header files too (which is part of
installworld).
--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
___
freebsd
Hello all,I'm writing you because I found that at some point in the past, you
had trouble with FreeBSD and the smb_maperror: Unmapped error 1:158 message.
For the folks who wrote about it, has anyone here resolved this issue?
I have also copied the freebsd mailing list on the issue.
The backgrou
On 9/18/06, VANHULLEBUS Yvan <[EMAIL PROTECTED]> wrote:
By default, I have set the value of port's configuration to "kernel",
which is exactly "use it if supported".
I just checked ./configure --enable-natt=yes (which forces NAT-T
support) on a FreeBSD 6.1 without NAT-T patchset, and I got that:
On Mon, Sep 18, 2006 at 03:04:04PM +, Bjoern A. Zeeb wrote:
> On Mon, 18 Sep 2006, VANHULLEBUS Yvan wrote:
>
> >By default in FreeBSd's port, NAT-T support is enabled if support is
> >detected on the system (checks for some structs in
> >include/net/pfkeyv2.h).
> >
> >Can you compile again ips
On Mon, 18 Sep 2006, VANHULLEBUS Yvan wrote:
By default in FreeBSd's port, NAT-T support is enabled if support is
detected on the system (checks for some structs in
include/net/pfkeyv2.h).
Can you compile again ipsec-tools port, but not clean it, and check in
config.h if you have NAT-T support
On Sun, Sep 17, 2006 at 11:58:17AM -0400, Scott Ullrich wrote:
> On 9/17/06, VANHULLEBUS Yvan <[EMAIL PROTECTED]> wrote:
> >Make sure your ipsec-tools port have been recompiled after your system
> >has been patched / compiled / upgraded, and use
> >/usr/local/sbin/setkey.
> >
> >FreeBSD's setkey do
Hello Mike,
> Although it sounds silly, could you try recompiling 6.1 and 7.0 with a
> non-SMP kernel and see how they perform? That would at least tell us if
> it's a general performance problem in 6.x and 7.x, or if SMP is somehow
> hurting performance in this case.
I have this numbers spr
On Mon, Sep 18, 2006 at 03:25:25PM +0300, Dmitry Pryanishnikov wrote:
>
> Hello!
>
> On Thu, 29 Jun 2006, Nikolas Britton wrote:
> >Last I checked somebody was developing an experimental driver and
> >Marvell had just released the code to their FreeBSD 5.x/6.x driver:
> >mykbsd60x86-8.12.2
Hello!
On Thu, 29 Jun 2006, Nikolas Britton wrote:
Last I checked somebody was developing an experimental driver and
Marvell had just released the code to their FreeBSD 5.x/6.x driver:
mykbsd60x86-8.12.2.3.tar (bindary kmod package)
mykbsd60x86-8.12.1.3-src.tgz (source code)
I can confirm th
[EMAIL PROTECTED] wrote: Send freebsd-net mailing list submissions to
freebsd-net@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-net
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can
Current FreeBSD problem reports
Critical problems
Serious problems
S Tracker Resp. Description
o kern/92552 netA serious bug in most network drivers from 5.X to 6.X
f kern/93220 net[inet
21 matches
Mail list logo
