Hi Christian and Fabricio,
Thanks for your hints. I followed (most of) them, and now, IAS answers the
RADIUS requests correctly. (RADIUS auth log on pfsense shows Login and Logout
activity correctly, IAS event log shows successful/unsuccessful RADIUS requests)
BUT: now I struggle with the CP
Tested. Same results!
There is still the problem. :(
I think the rules are created in somewhere, but the problem is that they are not
shown.
Thanks for the help.
Fuchs, Martin wrote:
Please try an image from here:
http://pfsense.trendchiller.com/DISTRIBUTION/1.2-BETA-1-PRERELEASE/
any
That's very strange...
I'm running 4 systems by now with this snapshot and it really works fine...
Let me ask: it's when you creatre the client or server settings that they
disappear afterwards ? but they work ? or don't they work properly ?
Von: Pablo Montoro Escaño
Gesendet: Do 26.04.2007
The rules don't appear neither in Client nor in Server.
I don't know if if it's working, but I have passed the configuration to an old
image (1.0.1) and I could see the rules created. So I think the rules are, but
it is just they don't appear.
Fuchs, Martin wrote:
That's very strange...
So just try the latest snapshot...
you should see your rules created but there will be one client and one server
entry (undeletable and empty)
edit your config.sml and look for openvpn... there will be two tags:
config/config under server and client.
delete those and reupload the config.xml
please try the following with ther latest snapshot:
(you should see your rules created but there will be one client and one server
entry (undeletable and empty))
edit your config.sml and look for openvpn... there will be two tags:
config/config under server and client.
delete those and
This is fixed however a blank line will appear in the newer version.
We know about this problem and will be hunting for the culprit.
Scott
On 4/26/07, Pablo Montoro Escaño [EMAIL PROTECTED] wrote:
The rules don't appear neither in Client nor in Server.
I don't know if if it's working, but I
Right!
Last snapshot is working.
Thanks all for your help.
Fuchs, Martin wrote:
please try the following with ther latest snapshot:
(you should see your rules created but there will be one client and one
server entry (undeletable and empty))
edit your config.sml and look for openvpn...
Hi, I am experiencing the following, does anyone have experience the
same?
I define CARP Failover for 2 boxes of pfsense, the master synchronizes
all profiles to the slave and the slave does not synchronize to the
master. I defined 2 CARP virtual IP, one for WAN and one for LAN. When
it comes to
I was using a pfsense 1.0-EMBEDDED in Wrap hardware and the Atheros PCI card
did work well
When I changed to 1.0.1 it quit working and also with 1.2-BETA
chip=0xff16168c
[EMAIL PROTECTED]:17:0:class=0x02 card=0x chip=0xff16168c
rev=0x01
hdr=0x00
class=
On 4/26/07, Pedro Paulo Oliveira Jr [EMAIL PROTECTED] wrote:
I was using a pfsense 1.0-EMBEDDED in Wrap hardware and the Atheros PCI card
did work well
When I changed to 1.0.1 it quit working and also with 1.2-BETA
chip=0xff16168c
[EMAIL PROTECTED]:17:0:class=0x02
Scott,
Just to our knowledge base:
This problem happens with every Wrap board if the BIOS is not upgraded to
1.11
-Original Message-
From: Scott Ullrich [mailto:[EMAIL PROTECTED]
Sent: quinta-feira, 26 de abril de 2007 14:01
To: support@pfsense.com
Subject: Re: [pfSense Support]
And to add to this the console on the wrap can get really screwy on
older bios versions as well.
Scott
On 4/26/07, Pedro Paulo Oliveira Jr [EMAIL PROTECTED] wrote:
Scott,
Just to our knowledge base:
This problem happens with every Wrap board if the BIOS is not upgraded to
1.11
I upgraded and it worked very well.
-Original Message-
From: Scott Ullrich [mailto:[EMAIL PROTECTED]
Sent: quinta-feira, 26 de abril de 2007 15:21
To: support@pfsense.com
Subject: Re: [pfSense Support] Drivers Problem with new Firmware
And to add to this the console on the wrap can get
Since a picture is worth a thousand words, let me start with that...
http://www.gliffy.com/publish/1062004/
I can't figure out how to configure pfSense
(1.0.1-SNAPSHOT-03-27-2007) to allow telnet from any LAN PC to the
telnet server. I have plugged OPT1 in to the partner's switch and it
gets
The telnet server probably has no route back to 192.168.1.0/24.
You'll need to either add a route on that machine pointing back at
your OPT interface or use advanced outbound nat and nat the traffic
from your 192.168.1.0/24 network to something (like the 172.22.99.197
address of your firewall)
16 matches
Mail list logo
