Scott,
The Shared Physical Netork option is not setting
net.link.ether.inet.log_arp_movement in my box. I check and save, and unckek
and save, and this always stay in 1. I´m using sysctl -a to list the
onfigurations. It only print 1 -> 0 at the top to the page.
System:
1.0.1-SNAPSHOT-03-15
Sorry, This particular issue turned out to be a typo in the virtual IP
address. It was trying to do right but of course would not work. As for why
the WAN connection did not work correctly when I tested using the interface
address, I am not sure. I deleted and recreated all rules and forward
I plundered through the archives and couldnt find any help on this issue. I
have a 1.0.1 PFSense unit in Bridge between WAN & OPT1 interface. I have (for
testing) an allow * in & out rule on all 3 interfaces (the LAN is unplugged and
just used for management when needed). I can create various dr
Great, Glad to see that feature. I have not needed to do it with this snap
shot. I had to do it previousy when changing NAT rules for client machines.
I have not needed to with the new version. I am assuming this has been clean
up more?
Robert
On Thursday 29 March 2007 22:38, Scott Ullri
On 4/2/07, Diego Morato <[EMAIL PROTECTED]> wrote:
Scott,
The Shared Physical Netork option is not setting
net.link.ether.inet.log_arp_movement in my box. I check and save, and unckek
and save, and this always stay in 1. I´m using sysctl -a to list the
onfigurations. It only print 1 -> 0 at
On 4/1/07, Kelvin Chiang <[EMAIL PROTECTED]> wrote:
Hi, I realized that even though the Client-Specific-Configuration is
deleted, the openvpn-csc directory still have the file in there. This cause
the openvpn server still uses the options stated in this file. Does anyone
experience the same thi
I've just tested the most recent pfsense update available on
http://snapshots.pfsense.com/FreeBSD6/RELENG_1/updates/
Here is the system's firmware information:
1.0.1-SNAPSHOT-03-27-2007
built on Mon Apr 2 19:21:19 EDT 2007
My results indicate that IPSEC over OPTx still does not work without
expli
On 4/2/07, Vaughn L. Reid III <[EMAIL PROTECTED]> wrote:
I've just tested the most recent pfsense update available on
http://snapshots.pfsense.com/FreeBSD6/RELENG_1/updates/
Please show the IPSEC rules that are relevant to the interface in
question as you did prior.
Thanks!
--
Here are the rules for the interface in question that seem to make the
IPSEC tunnel work:
Rules in the format listed below:
Format: Protocol Source Port Destination Port
Gateway Schedule
1. UDP * * Interface IP Address 500 * Blank
2. ESP *
On 4/2/07, Vaughn L. Reid III <[EMAIL PROTECTED]> wrote:
Here are the rules for the interface in question that seem to make the
IPSEC tunnel work:
[snip]
Look in /tmp/rules.debug and search for IPSEC.
Do you see rules permitting traffic to the interface?
Scott
---
Interesting,
This version of the firmware doesn't even list the VPN tunnel that is
configured for the OPT interface in the vpn section of /tmp/rules.debug.
The tunnel definition is listed in the GUI, and it's working with the
manual rules because I'm in the process of accessing remote resources
n
Just to be thorough, I added two more rules to the firewall's OPT
interface to make sure all the IPSEC stuff gets through. I'm fuzzy on
if the last two are needed, but just to be safe, I added them.
Here are all the rule that I've added:
Rules in the format listed below:
Format: Protocol Sou
Dear All,
I have a couple of inquiries where I need people who have experience to
convey some of their knowledge to me.
1- Does pfsense support 802.1x authentications; I mean does it act as
an authenticator for any 802.1x supplicant, in another word, does it allow
EAP authentication requ
13 matches
Mail list logo
