OK - figured this part out.
I needed to use "ping -S ..." when pinging a
ipsec-network host from the pf device itself.
Any ideas on how to make this work for iperf in client mode?
Is there any way to specify a "default System IP Address"?
I see that a Virtual IP can only be created for LAN or W
On Fri 24 Feb 2012 21:45:15 NZDT +1300, Jürgen Echter wrote:
> i had to re-setup my firewall and restored my config. all went well
> so far, but i can't edit anything because i have on every screen a
> pic which says 'packages are being reinstalled in the background'.
> this is on since a few hour
I obtained a couple of Tenda W322U to use as access points after finding
reports that they work well with pfsense. ralink chipset, run driver.
Initially everything's perfect - plug in, device shows up and can be
configured. Needs an entry in loader.conf.local but hey.
Then the kernel panics - not
I have a question on VPN/IPSEC behavior and looking for insight here.
In my setup, I have 2 networks connected via ipsec.
192.168.0.0/24 pf ---internetcisco/linksys-192.168.10.0/24
+ All traffic between hosts on 192.168.0.0/24 and 192.168.10.0/24 works fine.
+ pf is setup as
*"Windows RADIUS server with captive portal*" Can you tell me or can you
please direct me to good guide to setup Win Radius with Captive Portal.
Cris Thanks for your answer!
On 26 April 2012 13:49, Chris Buechler wrote:
>
>
> On Thu, Apr 26, 2012 at 3:12 AM, Abdullah Nihan wrote:
>
Firewall: NAT: Port Forward:
Interface: LAN
Protocol: TCP
Destination: ANY
Destination port range: from http to http
Redirect target ip: 127.0.0.1
Redirect target port : other 8080
Make sure it showing under the LAN segment in the correct order
From: Ryan Rodrigue [mailto:radiot
Ryan, your solution worked just fine, but in addition I added a fw rule to
catch all http (port 80) traffic and had it redirected to 8080, that way you
don't need to change the proxy on the individual hosts
K_o_l
How and where did you add such a rule? I would like it to work in
transpar
On 4/27/2012 11:44 AM, Vick Khera wrote:
> Reading http://doc.pfsense.org/index.php/Inbound_Load_Balancing
>
> I find a couple of issues, which seem to be changes in 2.0.
>
> 1) the default probe is 10 seconds, not 5. There is no way to tweak that.
There is in 2.1
> 2) there is no "sticky" opt
Ryan, your solution worked just fine, but in addition I added a fw rule to
catch all http (port 80) traffic and had it redirected to 8080, that way you
don't need to change the proxy on the individual hosts
From: list-boun...@lists.pfsense.org [mailto:list-boun...@lists.pfsense.org]
On Behalf O
Reading http://doc.pfsense.org/index.php/Inbound_Load_Balancing
I find a couple of issues, which seem to be changes in 2.0.
1) the default probe is 10 seconds, not 5. There is no way to tweak that.
2) there is no "sticky" option
The commentary about 1.2 implementation using NAT and issues with
Hi there,
when I fire up svscan on one of my pfsense 2.0.1 boxes, it starts
"supervise tinydns" processes. These supervise processes spawn plenty of
processes that end up as zombies, each of which dies some seconds. I.e.,
I have a block of 5-6 s traversing my process list.
Constantly. The Tin
On 27/04/12 11:00, bsd wrote:
>> I've been using the above miniPCI card in an Alix board for over a
>> year now - entirely trouble free.
Great. Thanks.
--
Pete Boyd
thegoldenear.org
openplanit.co.uk
___
List mailing list
List@lists.pfsense.org
http:/
Le 26 avr. 2012 à 21:40, Pete Boyd a écrit :
> Hi. I'm choosing a miniPCI wireless card from www.msdist.co.uk to go in
> an ALIX 2D3. The only cards there that appear to be supported by
> FreeBSD 8.1 are the Wistron DCMA81 (Atheros AR5213A), Wistron CM9-GP
> (Atheros AR5213A) and the Compex WLM54
13 matches
Mail list logo
