Curtis LaMasters wrote:
Firewall Rules should look something like this...
TCP | * | * | 192.168.1.10 | 80 (HTTP| * | | NAT HTTP to 1st server
TCP | * | * | 192.168.1.11 | 80 (HTTP| * | | NAT HTTP to 2nd server
TCP | * | * | 192.168.1.12 | 80 (HTTP| * | | NAT HTTP to 3rd server
NAT rules shou
Curtis LaMasters wrote:
Firewall Rules should look something like this...
TCP | * | * | 192.168.1.10 | 80 (HTTP| * | | NAT HTTP to 1st server
TCP | * | * | 192.168.1.11 | 80 (HTTP| * | | NAT HTTP to 2nd server
TCP | * | * | 192.168.1.12 | 80 (HTTP| * | | NAT HTTP to 3rd server
NAT rules shou
Firewall GW
TCP * | * 192.168.2.130 80 * Server 1
TCP * | * 192.168.2.150 80* Server 2
TCP * | * 192.168.2.160 80* Server 3 not working
TCP * | * 192.168.2.160 80* Server 3 Works fine
NAT Ru
All,
If you are not using the VPN on the pfsense firewall, but rather passing
VPN traffic through the firewall to another server AND you have
multiple VPN servers that you are passing WAN traffic to based on the
remote IP, is this doable on pfSense? If so, is there a document you
can point me
My apologies that should say "our pfsenses" and not "our flenses"
From: Atkins, Dwane P [mailto:atki...@uthscsa.edu]
Sent: Tuesday, March 03, 2009 10:30 AM
To: support@pfsense.com
Subject: [pfSense Support] Captive Portal Issues
We have been running
We have been running pfSense as a Captive Portal for quite sometime.
Lately, our flenses have had services that were locking up. You could
view items on the GUI, but could not execute a Captive Portal lookup or
a Halt System or Reboot System. And if you ssh'ed into the system, you
could not execu
Firewall Rules should look something like this...
TCP | * | * | 192.168.1.10 | 80 (HTTP| * | | NAT HTTP to 1st server
TCP | * | * | 192.168.1.11 | 80 (HTTP| * | | NAT HTTP to 2nd server
TCP | * | * | 192.168.1.12 | 80 (HTTP| * | | NAT HTTP to 3rd server
NAT rules should look something like thi
Von: Abdulrehman [mailto:arvagabo...@gmail.com]
Gesendet: Dienstag, 3. März 2009 07:16
An: support@pfsense.com
Betreff: Re: [pfSense Support] Not all Virtual IP's forwarding correctly
> Don't confuse guys up here...!
> 1. where your IP is blocked...at ISP end or somewhere on internet..?
This is because IGMP works above the network Layer...thats why it is not
recognized as a transport protocol...You should disable IGMP if there is no
requirement on your network for it.
Regards
Abdulrehman
On Tue, Mar 3, 2009 at 3:17 PM, Simon Gerber wrote:
> Why are IGMP Packets recognized as E
Hi
On the OpenNTPD page I suggest the text be changed from
"Select the interface the NTP server will listen on."
"Select the interface(s) the NTP server will listen on."
I assume this minor change more accurately describes that pfsense seems to be
able to serve NTP on multiple LAN interfaces.
Why are IGMP Packets recognized as ESP (Encapsulated Security Payload)
in GUI?
Console:
10:15:43.276143 IP 1.1.1.1 > 224.0.0.1: igmp query v2 [max resp time 20]
GUI:
Mar 3 10:15:44 WAN 1.1.1.1 224.0.0.1 ESP
Regards, Simon
-
11 matches
Mail list logo