Does anyone have bge(4) network card with working hardware vlan support?
I have one, and it works with vlans only with the following patch. This
is fresh FreeBSD-6-CURRENT, HP workstation xw4100, built-in network
card.
--- /usr/src/sys/dev/bge/if_bge.c Fri Mar 18 09:14:18 2005
+++ if_bge.c
Hi,
Unfortunately, there's no way in the FreeBSD NFS client to
disable data caching. Setting the ac* values to 0 will have
the effect of disabling the attribute cache, which means
that you'll never fetch attributes from the cache, but force
an over-the-wire getattr call each time. But this does
Julian Elischer wrote:
Dag-Erling Smørgrav wrote:
"Mike Jakubik" <[EMAIL PROTECTED]> writes:
Really? Ive never been able to compile it on any 5.x box.
[...]
bison -y -p wack -d config_gram.y
config_gram.y:91.10: parse error, unexpected ":", expecting ";" or "|"
config_gram.y:191.10: parse erro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Is there a way to disable client-side caching? I've looked, and
>> can't seem to find one. Or, do I have this wrong and there is
>> something else that is causing this?
>
>
> Take a look through "man mount_nfs" for:
>
> -a Set the re
On Apr 7, 2005, at 3:51 PM, Eli Dart wrote:
Looking at the packet contents, it appears to be fetching back the
last few blocks of the log file.
My guess is that this is the client keeping its NFS cache fresh.
The client is never, ever, ever going to read that file (or any file
on that filesystem) o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi List,
We've just deployed a new syslog server infrastructure consisting of
two hosts -- one NFS server that has a large disk array attached via
fibre channel and one NFS client that receives syslog messages,
mounts the server's disk, and writes to
Dag-Erling Smørgrav wrote:
"Mike Jakubik" <[EMAIL PROTECTED]> writes:
Really? Ive never been able to compile it on any 5.x box.
[...]
bison -y -p wack -d config_gram.y
config_gram.y:91.10: parse error, unexpected ":", expecting ";" or "|"
config_gram.y:191.10: parse error, unexpected ":", expec
On Thu, April 7, 2005 11:12 am, Dag-Erling Smørgrav said:
> You're probably using the wrong version of bison.
Yes, Theo Schlossnagle already mentioned this to me. The compile process
was using the port version of bison, removing it solved the problem.
Thanks.
___
The problem is that some visitors might need to connect to the home VPN
gateway(s) from my work office. Thus, we could not decide which VPN
gateway solution they use.
On the other hand, what is the status of FreeBSD on the support of
NAT-T? Would it be supported in FreeBSD in later issues, e.g.
John Mok wrote:
Dear Tom,
Thank you for your quick reply.
I would like to know more on the issue. To my understanding, since the
source address of the IP packet from the client would be modified on
the NAT, normally it would fail AH check on the IPsec VPN gateway, or
the FreeBSD NAT has built-in
On Fri, 8 Apr 2005, John Mok wrote:
Hi,
> Thank you for your quick reply.
>
> I would like to know more on the issue. To my understanding, since the
> source address of the IP packet from the client would be modified on the
> NAT, normally it would fail AH check on the IPsec VPN gateway, or the
>
Dear Tom,
Thank you for your quick reply.
I would like to know more on the issue. To my understanding, since the
source address of the IP packet from the client would be modified on the
NAT, normally it would fail AH check on the IPsec VPN gateway, or the
FreeBSD NAT has built-in compliance with
John Mok wrote:
Hi,
I'm new to FreeBSD. Is it possible make a FreeBSD box with firewall +
NAT, such that client PC(s) from the NATed internal network could
connect to a VPN gateway on the Internet :-
client PC - FreeBSD Firewall + NAT Internet IPsec VPN
gateway
192.168.x.x/16
Hi,
I'm new to FreeBSD. Is it possible make a FreeBSD box with firewall +
NAT, such that client PC(s) from the NATed internal network could
connect to a VPN gateway on the Internet :-
client PC - FreeBSD Firewall + NAT Internet IPsec VPN
gateway
192.168.x.x/16
"Mike Jakubik" <[EMAIL PROTECTED]> writes:
> Really? Ive never been able to compile it on any 5.x box.
> [...]
> bison -y -p wack -d config_gram.y
> config_gram.y:91.10: parse error, unexpected ":", expecting ";" or "|"
> config_gram.y:191.10: parse error, unexpected ":", expecting ";" or "|"
> con
Charles Swiger <[EMAIL PROTECTED]> writes:
> It's dead, I think: Cisco's lawyers started making predatory noises
> about their "intellectual property". Some people from NetBSD are
> working on a replacement called CARP, which you might want to check
> out-- it seems that FreeBSD will be picking u
16 matches
Mail list logo
