Hi !
The schedule name: Peter
The schedule-description: wenn Peter da ist
Month: 05/07
Time: 00:00 - 23:59
Time Range Description: empty
after that add another schedule with e.g. Month 05/17, Time 00:00 - 23:59
Time Range Description: empty
- Add Time
- Do NOT hit save, but delete the old range
Duplicated. Will patch shortly. Thanks
Fuchs, Martin wrote:
Hi !
The schedule name: "Peter"
The schedule-description:
"wenn Peter da ist"
Month: 05/07
Time: 00:00 - 23:59
Time Range Description:
empty
after that add another
schedule with e.g. Month 05/17, Time 00:00 -
Hello,
How can i see the signal, and most important, how to list the noise from the
clients in my ap interface?
Thanks,
Gusmão
Until then, this is a function of your browser, you can look at ways to
get your browser to clear HTTP basic authentication credentials without
closing the browser.
Bill Marquette wrote:
This was committed to the RELENG_1 branch (sponsored by two different
entities) right after the branch
On 5/7/07, Chris Buechler [EMAIL PROTECTED] wrote:
Until then, this is a function of your browser, you can look at ways to
get your browser to clear HTTP basic authentication credentials without
closing the browser.
Unfortunately, short of closing the browser (assuming the save
credentials
In Firefox:
Tools- clear private data- un-check all except authenticated
sessions and hit ok
On 5/7/07, Chris Buechler [EMAIL PROTECTED] wrote:
Until then, this is a function of your browser, you can look at ways to
get your browser to clear HTTP basic authentication credentials without
Bill Marquette wrote:
On 5/7/07, Chris Buechler [EMAIL PROTECTED] wrote:
Until then, this is a function of your browser, you can look at ways to
get your browser to clear HTTP basic authentication credentials without
closing the browser.
Unfortunately, short of closing the browser (assuming
I've been banging my head on the wall trying to get remote IPSEC to work
with mobile clients and have had very little luck so far. From what I
can tell, I've configured things properly on both ends but I receive a
strange error message in the IPSEC logs when I try to connect. It states
racoon:
http://pfsense.org/mirror.php?section=tutorials/mobile_ipsec/
-Original Message-
From: Tim Nelson [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 11:20 PM
To: support@pfsense.com
Subject: [pfSense Support] IPSEC Mobile Client
I've been banging my head on the wall trying to get
That tutorial is aimed at a site to site link although I used it as a
basis to configure my pfSense box...
--Tim
Holger Bauer wrote:
http://pfsense.org/mirror.php?section=tutorials/mobile_ipsec/
-Original Message-
From: Tim Nelson [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07,
On 5/7/07, Tim Nelson [EMAIL PROTECTED] wrote:
That tutorial is aimed at a site to site link although I used it as a
basis to configure my pfSense box...
Come again? That tutorial is suited for mobile clients.
Scott
-
To
I'm sorry... I should clarify. When I said 'mobile clients' I meant end
users/computers away from that site. I did not mean other pfSense boxes
with dynamic IP's on them. I've configured my IPSEC client as specified
in that tutorial.. but at this point I'm not sure if it is a problem
with my
You can't see the noise but you can get the signal (sort of) by
looking at the RSSI value. Take a look at the wireless status page.
http://forum.pfsense.org/index.php/topic,1368.0.html for more info.
-lsf
On 5/7/07, Fábio Gusmão [EMAIL PROTECTED] wrote:
Hello,
How can i see the signal, and
Since upgrading to the beta version, my wireless gets stuck in a loop
where it goes up and down. In the logs, I get the following entries:
May 7 18:01:53 hostapd: ath0: STA 00:XX:XX:XX:XX:XX IEEE 802.11:
deassociated
May 7 18:01:53 hostapd: ath0: STA 00:XX:XX:XX:XX:XX IEEE 802.11:
Holger Bauer wrote:
Hello Holger,
I've been banging my head on the wall trying to get remote IPSEC to work
with mobile clients and have had very little luck so far. From what I
can tell, I've configured things properly on both ends but I receive a
strange error message in the IPSEC logs
Chris Buechler wrote:
I presume you're talking about a stock FreeBSD install?
I'm talking about the FreeBSD sources that were used to compile the
kernel that pfsense uses.
I don't believe the NAT-T patches are in the pfsense kernel, something
about a security issue with them was reported
On 5/7/07, Matthew Grooms [EMAIL PROTECTED] wrote:
The racoon binary was obviously compiled with NATT support on a system
that had the kernel patch applied. Otherwise it wouldn't be attempting
to set the UDP_ENCAP_ESPINUDP_NON_IKE socket option doesn't exist in
udp.h until the patch is applied
I'll take a look at the wireless on 1.2 once I get my lab back up and
running. I just moved a month ago, got internet (cable) today, will
get ADSL tomorrow and hopefully finnish cabling my apartment sometime
this week, so maybe i can be ready to do some testing in the weekend.
However I have
It seems to be sporadic. I've only noticed it with 802.11B enabled
(instead of G only) on my wrap. Its happened twice, and each time
cycling the atheros card using the interface fixes the problem. My wrap
stays running and I can get to it on the wired interface.
Espen Johansen wrote:
I'll
Scott Ullrich wrote:
Yes, you are correct. Whoever made the default option to check NAT-T
support should really consider reverting this. We now build all of
the binaries on each image run. Having that as the default does not
seem like a sane way of working this considering that someone has
20 matches
Mail list logo
