Added to table.
Quoth Gil Freund:
Looks Ok. I tried (all Atheros 5212):
Make 0.880.900.93
=== === ===
Askey Problem OK OK
Gigabyte GN-WIAG02Problem
My update:
Make0.880.900.93
=== === ===
Askey Problem OK OK
Gigabyte GN-WIAG02 Problem Problem OK
Philips (IBM OEM) OK OK
Marc A. Volovic wrote:
Added to table.
Quoth Gil Freund:
Looks Ok. I tried (all Atheros 5212):
Make 0.880.900.93
=== === ===
Askey Problem OK OK
Gigabyte
its a requirement , you must mount in the jail for the deveice, see man
jail. the wiki is missing some stuff
fdescfs on /usr/jails/pfsense/dev/fd (fdescfs)
procfs on /usr/jails/pfsense/proc (procfs, local)
devfs on /usr/jails/freesbie/dev (devfs, local, multilabel)
On Sat, 2005-11-12 at 10:50
D=/here/is/the/jail
cd /usr/src
mkdir -p $D
make world DESTDIR=$D
make distribution DESTDIR=$D
mount_devfs devfs $D/dev
is a more correct way to build your environment prpoerly
also look at /etc/defaults/rc.conf | grep jail for autostarting a proper
jail environment
Niether the ARP nor the IP is in my DHCP list (static arp entries are
enabled, which actually don't seem to work, so i suppose it's from
there).
I have the 'anti-lockout rule' disabled too.
On 11/12/05, jonathan gonzalez [EMAIL PROTECTED] wrote:
spoofed ip/arp ;) ??
Szasz Revai Endre wrote:
Enable yes
Interface (selected
public carp address that I want to use 192.168.5.100)
Failover ip (same
address as above 192.168.5.100)
Peerip (used
the carp sync real ip address of the other carp in my array 192.168.10.2)
Shared key (used a 16
byte aes key)
This end is a mobile
This carp init thing does not seem to be such and issue on
this version. Looks like it is nearly licked.
I did not see much change in the cvstrac though so not sure
what was done.
Present testing shows the carp to come up fine on the wan
but it is a little slow.
Will report more on
Just a note that these do not seem to work all that well. Maybe
new Feaures should be disabled by default. Rather than enabled.
I get a pile of rdr errors
Regards
alan
If there is a negoitation in ipsec tunnels and you change an
ipsec setting or add a new tunnel.
Ipsec seems to report errors about being unable to bind to
the addresses on the box.
On further review of this the issue seems
to lie in the fact that the tunnel end of the ipsec is running
A via padlock chipset. If I replace the
tunnel end with the same config.xml file and a wrap board the tunnel works
perfectly.
From: alan walters
Sent: Saturday,
On 11/12/05, Gil Freund [EMAIL PROTECTED] wrote:
Spoken too soon
See attached dmesg output. This is on a 0.90 upgraded to 0.93.
Seems OK on a full 0.93 install.
Philips (IBM OEM) OK OK OK
TP-Link TL-WN660G Problem Problem OK
Scott Ullrich schrieb:
You need both cables plugged in so it can fetch the package manifest
from our site.
Ok, got it up with this hint...
but then the next show-stopper came up:
squid 2.5.irgendwas not working
ah...mhh, aha...
with regards
Andreas Bahr
(an ordinary m0n0wall
Hello list,
today got the pfsense up but I was astonished to
see, that the squid package was labeled as Not
working.
So I'm currently in a need to install an external
*SMALL* proxy outside the firewall and the
internal http-proxy. The internal proxy is a
McAfee Webshield, which allows a
Maybe you should wait for official versions. Please, I don't want a
handfull of emails on test versions when I wake up. It's not fun.
On 11/12/05, alan walters [EMAIL PROTECTED] wrote:
Just a note that these do not seem to work all that well. Maybe new Feaures
should be disabled by
On 11/12/05, Andreas Bahr [EMAIL PROTECTED] wrote:
Hello list,
today got the pfsense up but I was astonished to
see, that the squid package was labeled as Not
working.
Astonished to see this on a Alpha project?
So I'm currently in a need to install an external
*SMALL* proxy outside the
On the packages page, in the version column for squid, it says *NOT WORKING*.
On 11/12/05, Andreas Bahr [EMAIL PROTECTED] wrote:
Scott Ullrich schrieb:
You need both cables plugged in so it can fetch the package manifest
from our site.
Ok, got it up with this hint...
but then the next
Fixed.
On 11/12/05, alan walters [EMAIL PROTECTED] wrote:
If there is a negoitation in ipsec tunnels and you change an ipsec setting
or add a new tunnel.
Ipsec seems to report errors about being unable to bind to the addresses on
the box.
18 matches
Mail list logo
