Hi Scott,
2006/9/27, Scott Ullrich [EMAIL PROTECTED]:
Please provide a patch in duff -rub format.
Hmm... see attachment *giggles*
Yes i must first upgrade to new configuration or copy my configfiles
i have no backup made before i have made the changes.
just for be sure
diff -rub
Hi,
i have pfsense taked yesterday in production use
(SNAPSHOT from 2006-09-26).
My configuration is
wan public.226/28
DMZ public.241/28
lan privateip/24
now i have the Problem my config for ftp-proxying our ftp-server
is probably wrong. i can connect to the ftp, but it passed only
one type of
This is extensively covered at the forum and there even is a faq entry at
faq.pfsense.com (I think).
However, quick guide:
- Delete all NAT/firewallrules you created for the ftpserver (most likely wrong
as it doesn't work) to start over.
- at interfaceswan enable ftp helper
- at firewallnat,
Hi,
first thanks for your work and hints, but
i have seen the entrys in forum and faq, but this covers not my problem.
I think you have not really understand what i would, or better i have
not clearly enough described my problem.
Our ftp-server is on an public ip-address (our complete dmz).
so
As the ftp server has a routed public IP disable the ftp-helper at WAN (or keep
it disabled, it is by default). Then all you need is firewallrules permitting
tcp traffic from source any to destination public IP of ftp-server port 21
and additional to that the portrange range that the ftp server
Hi,
2006/9/28, Holger Bauer [EMAIL PROTECTED]:
As the ftp server has a routed public IP disable the ftp-helper at WAN (or keep it
disabled, it is by default). Then all you need is firewallrules permitting tcp
traffic from source any to destination public IP of ftp-server port 21 and
Try the image from the 27th. Your a day behind me.
On 9/28/06, Captain Bablam [EMAIL PROTECTED] wrote:
Scott,
The issue remains in the snapshot listed below. For
troubleshooting purposes I will send the server side logs and client
side logs, any other information you would like to see? In
The host is up,
PPTP (not through a proxy) works fine. Here is an attempt with a
direct connect (no proxy). What I keep seeing on the server side is 2
things;
1. I cannot mod the server0.conf, I mod it and the changes don't keep
(I did disable that particulat server before I attempted to
Use a different port then if 443 is already in use (webGUI?)
Scott
On 9/28/06, Captain Bablam [EMAIL PROTECTED] wrote:
The host is up,
PPTP (not through a proxy) works fine. Here is an attempt with a
direct connect (no proxy). What I keep seeing on the server side is 2
things;
1. I
Also,
I only get that complaint upon restart of the process, the initial
startup is fine, binds the port and all is good.
-W
On 9/28/06, Captain Bablam [EMAIL PROTECTED] wrote:
Nope,
Webgui is running on TCP/81.
-W
On 9/28/06, Scott Ullrich [EMAIL PROTECTED] wrote:
Use a
Scott,
See attached, some good troubleshooting and very interesting
information. This is all server side (despite the name of the file).
This was all configuring the server side and viewing the errors,
fricin weird stuff. Let me know what else you would like to see in
the way of
Good morning all,
The default quagga script that installed with the package did
not seem to do the trick. I modified it a little to include the
creation of the directory and perms where the PID file needs to live.
I can start the script manually /etc/rc.d/quagga start which is what
I have
It works I just have to start it manually,
I have my entire internal network running on EBGP with crunched
down timers for fast convergence. It works awesome. The two others
peers are an openwrt box and an FC5 box all running quagga. No static,
all dynamic, the daemon just has to come up
Quagga is not even listed in the packages area. Not sure how you even
installed this, but either way its not working out of the box.
On 9/28/06, Captain Bablam [EMAIL PROTECTED] wrote:
It works I just have to start it manually,
I have my entire internal network running on EBGP with
Someone listed a link to the ports tree,
So I installed it. Let me know if I can help you out getting
it mainstream.
-W
On 9/28/06, Scott Ullrich [EMAIL PROTECTED] wrote:
Quagga is not even listed in the packages area. Not sure how you even
installed this, but either way its not
On 9/28/06, Captain Bablam [EMAIL PROTECTED] wrote:
Someone listed a link to the ports tree,
So I installed it. Let me know if I can help you out getting
it mainstream.
Only packages that appear in System - Packages are supported.
OK good to know thank you,
Are there plans to support quagga? I thought I saw that on the
list a while back?
-W
On 9/28/06, Scott Ullrich [EMAIL PROTECTED] wrote:
On 9/28/06, Captain Bablam [EMAIL PROTECTED] wrote:
Someone listed a link to the ports tree,
So I installed it.
On 9/28/06, Captain Bablam [EMAIL PROTECTED] wrote:
OK good to know thank you,
Are there plans to support quagga? I thought I saw that on the
list a while back?
I am not sure at this point.
-
To unsubscribe, e-mail:
It will do NAT by default if the interface has a gateway. Otherwise you can
create rules at firewallnat, outbound if you enable advanced outbound nat.
Holger
-Original Message-
From: Lew Maggio [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 28, 2006 5:55 PM
To: support@pfsense.com
A pfSense newbie here. I have a configuration question. I understand
Cisco PIX configs well enough to describe the goal. I am trying to
translate this concept to pfSense. Let me describe my network a little.
This is a typical belt and suspenders configuration with dissimilar
firewalls for the
All,
I had recently been contacted by a user that was attempting to use my
free 2K/XP IPSEC client with pfsense. The racoon key daemon was tripping
up over a modecfg exchange that wasn't supported by the version of
ipsec-tools installed. My reference gateway platform is FreeBSD so I
think
On 9/28/06, Matthew Grooms [EMAIL PROTECTED] wrote:
All,
I had recently been contacted by a user that was attempting to use my
free 2K/XP IPSEC client with pfsense. The racoon key daemon was tripping
up over a modecfg exchange that wasn't supported by the version of
ipsec-tools
On 9/28/06, Captain Bablam [EMAIL PROTECTED] wrote:
OK good to know thank you,
Are there plans to support quagga? I thought I saw that on the
list a while back?
Time. 'nuf said.
--Bill
-
To unsubscribe, e-mail:
Bill Marquette wrote:
On 9/28/06, Matthew Grooms [EMAIL PROTECTED] wrote:
I think we pretty much support everything that FreeBSD 6.1 supports.
It'd be interesting to know what mode(s) were being requested that we
don't allow though.
Well in this case, it would be features that ipsec tools
Bill Marquette wrote:
I think we pretty much support everything that FreeBSD 6.1 supports.
It'd be interesting to know what mode(s) were being requested that we
don't allow though.
The other bit I forgot to mention, racoon supports Hybrid and XAuth for
user based roaming client
25 matches
Mail list logo
