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
On 2/27/11 3:29 AM, Eugene Grosbein wrote:
On 27.02.2011 17:08, Eugene Grosbein wrote:
[skip]
For performance reasons, I need to create similar setup using in-kernel "ipfw
nat"
what does not have such "multiple instances" feature but has its own
"keep-state" mechanics:
To correct myself: of
On 28.02.2011 22:44, Julian Elischer wrote:
> On 2/27/11 3:29 AM, Eugene Grosbein wrote:
>> On 27.02.2011 17:08, Eugene Grosbein wrote:
>>
>> [skip]
>>
>>> For performance reasons, I need to create similar setup using in-kernel
>>> "ipfw nat"
>>> what does not have such "multiple instances" featur
On 2/28/11 8:53 AM, Eugene Grosbein wrote:
On 28.02.2011 22:44, Julian Elischer wrote:
On 2/27/11 3:29 AM, Eugene Grosbein wrote:
On 27.02.2011 17:08, Eugene Grosbein wrote:
[skip]
For performance reasons, I need to create similar setup using in-kernel "ipfw
nat"
what does not have such "mu
Jay Borkenhagen writes:
> Hi,
>
> After having been disappointed by one vendor *, I am returning to this
> list to seek recommendations for 1000Base-SX PCI NICs. I am looking
> to run them on FreeBSD 8 and beyond, and I need support for MTU > 1500
> bytes (initially around 4470, but possibl
vfs.nfsrv.nfs_privport controls wither or not NFS enforces the
traditional RPC semantics that require that requests come from
"privileged" ports. By default this check is disabled. Hardening
guides typically suggest this be enabled, usually via the rc.conf knob
nfs_reserved_port_only=YES.
I'm tr
I am getting started with IPv6 and I am trying to get rtadvd working on
the carp interface but it is not working so far.
### I have carp failover between two firewalls. The default gateway for
###hosts internal to the firewall is 172.31.98.103 for IPv4
###and 2001:470:dead:98::103 for
Hi,
whenever I try to set my mini PCI-e card (Anatel AR5BXB6) as Master
(tdmaslot 0), kernel shows PANIC msg like the below.
It's OK when I set the card as not Master like tdmalsot 1,2, and more. What
is the problem? And how can I fix it?
Interestingly, the kernel PANIC occurs when I use this car
I installed wireshark on my 9-CURRENT machine yesterday and found that
the interface description fields are all set to 0xa5. From reading the
code it looks like the data is being fetched via pcap.
Device: usbus1
Description: \xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5
\xa5\xa5\xa5\xa5
On Tuesday, March 01, 2011 03:49:41 Kyungsoo Lee wrote:
> Hi,
>
> whenever I try to set my mini PCI-e card (Anatel AR5BXB6) as Master
> (tdmaslot 0), kernel shows PANIC msg like the below.
> It's OK when I set the card as not Master like tdmalsot 1,2, and more. What
> is the problem? And how can I
On 1 March 2011 02:28, User Red35 wrote:
>
> I am getting started with IPv6 and I am trying to get rtadvd working on
> the carp interface but it is not working so far.
>
>
> ### I have carp failover between two firewalls. The default gateway for
> ### hosts internal to the firewall is 172.31.9
11 matches
Mail list logo