On 10/4/05, Jörgen Haraldsson [EMAIL PROTECTED] wrote:
HiThe line says:rdr on ste0 proto esp from any to 192.168.1.20 port 500 - 192.168.2.100port 500I don't know if port 500 is the right port to use with esp.
But It does not matter what port i use.
Mmmhh.. I think this is an error!!! ESP is
I have updated crontab on both my routers.. DynDns is still
being blocked for abuse. ( both custom and dynamic 2 different routers ). 086.
Tx
The fixes for dyndns in 0.86 no longer cause my dyndns account to be
blocked, but the dyndns client is still running every minute after
2:01 am. The line for dyndns in my crontab is as follows:
1 2 * * * root/usr/bin/nice
-n20 /etc/rc.dyndns.update
This
Solved my own problem.
The solution was (re)setting the MTU size to 1500 (should allready be the
default i think).
Greetz,
Michiel de Jager
Citeren Michiel de Jager [EMAIL PROTECTED]:
Hi all,
I have for the first time replaced my m0n0wall installation with a pfsense
one.
I have a
Scott Ullrich wrote:
Thanks!!
The HD in the 2nd-try server is a 80GB Maxtor.
I tried again with a 40GB Maxtor - still no luck.
I then went and removed all IDE-HDs from the 1st-try server
(2*IDE,2*SCSI) and installed it on the 1st SCSI-disk, which is some 9GB
Quantum Atlas.
That worked.
On 10/5/05, Ben Browning [EMAIL PROTECTED] wrote:
The fixes for dyndns in 0.86 no longer cause my dyndns account to be
blocked, but the dyndns client is still running every minute after
2:01 am. The line for dyndns in my crontab is as follows:
1 2 * * * root
When you say resetting, where did you do this? I thought the default
was 1500 already.
Scott
On 10/5/05, Michiel de Jager [EMAIL PROTECTED] wrote:
Solved my own problem.
The solution was (re)setting the MTU size to 1500 (should allready be the
default i think).
Greetz,
Michiel de Jager
Yes, it should be 1500 already, but when i entered it again it works.
So somehow it wasn't 1500.
Michiel
Citeren Scott Ullrich [EMAIL PROTECTED]:
When you say resetting, where did you do this? I thought the default
was 1500 already.
Scott
On 10/5/05, Michiel de Jager [EMAIL
Hi,
I already read a lot of things about m0n0wall and the Pfsense, but I'm
not able to understand what's the minimal material needs to install a
WIFI-LAN. I mean, I would like to mount a system whith which I need a
WLAN and LAN connection. And I can't imagine that I don't need other
material
Try a WRAP 1E-2 or 1E-1 (Mainboard, Ethernet), write the Image with
an USB-Card-Reader on a 128MB CompactFlash (=HardDisk)
Add a MiniPCI-WLAN Card to your Wrap ... finisch.
(I Order @ http://www.tronico.net/)
Am 05.10.2005 um 17:12 schrieb Adrien Gundogan:
Hi,
I already read a lot of things
In my opinion
it goes to depend on the one that you desire to run in this Box
for a basic FW but
I run this in Pentium 120Mhz 64Mb RAM 540 HDand NIC prefer
run in PCI NIC's
if you go use AltQ traffic Shapper, check in man if your's
NIC is listed on suported devices for
I found the -i flag. But where is the script file that starts ntop. Then I
can edit that one. If I restart the fw then ntop would start up on both
interfaces.
I have several LAN interfaces and want to monitor all.
Audun
-Original Message-
From: Scott Ullrich [mailto:[EMAIL PROTECTED]
Oops, wrong address. :)
(Doh!)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Uninstall and reinstall the package. Editing the script will be
useless as its created on every bootup.
Scott
On 10/5/05, Audun Brekke [EMAIL PROTECTED] wrote:
I found the -i flag. But where is the script file that starts ntop. Then I
can edit that one. If I restart the fw then ntop would
That's my opinion to !
But pfsense want me to fill in a port.
From: Dan Swartzendruber [EMAIL PROTECTED]
Reply-To: support@pfsense.com
To: support@pfsense.com
Subject: Re: [pfSense Support] Port Forward of ESP protocol
Date: Tue, 04 Oct 2005 13:45:11 -0400
At 01:43 PM 10/4/2005, you wrote:
Yes that's correct.
The port 500 is because pfsense want a portnr.
I have used 50 to but it's just a protocolnr not a portnr that ipsec use.
Thanks for the link.
From: Tommaso Di Donato [EMAIL PROTECTED]
Reply-To: support@pfsense.com
To: support@pfsense.com
Subject: Re: [pfSense Support] Port
Looking to pick up a wrap system and mini-pci wireless.
I want to pick it up from these people as they are close http://www.xagyl.com/catalog/index.php?cPath=23osCsid=9f3cbb3facc76b814572962be73cab67
Anyone know if any of those cards are supported. I
checked the hardware list and they
Jörgen Haraldsson wrote:
Yes that's correct.
The port 500 is because pfsense want a portnr.
I have used 50 to but it's just a protocolnr not a portnr that ipsec use.
Whenever you select ESP as protocol, the port boxes are all grayed out.
The only way the port boxes are available is if
Yes, bigger drives can be a problem with certain mobo's. We've been
working on a fix for a few days and may be getting close. Stay
tuned...
Scott
On 10/5/05, Rainer Duffner [EMAIL PROTECTED] wrote:
Scott Ullrich wrote:
Thanks!!
The HD in the 2nd-try server is a 80GB Maxtor.
I tried
Yeah, that was needles question from me :-},I have been mistaken.
Ok.
So, in that case if I create new queueue in live system, where is connected
several clients, new connections will be made if I execute RESET STATES?
Regards.
-Original Message-
From: Scott Ullrich [mailto:[EMAIL
On 10/5/05, Robo.K. [EMAIL PROTECTED] wrote:
Yeah, that was needles question from me :-},I have been mistaken.
Ok.
So, in that case if I create new queueue in live system, where is connected
several clients, new connections will be made if I execute RESET STATES?
Yes, if you want to make
Hi
Im currently testing pfsense on a VIA mini-itx
solution, one nic on an ADSL model the other on a LAN switch.
Once a day Ive got the webconfigurator inaccessible
either from LAN or wan. All the other functions work fine.
This seems to happen after the ADSL disconnect /
Hello,
One day passed and the bug is here again...
here are my screenshots:
http://rapidshare.de/files/5923217/Wan_Bug_from_fresh_86.rar.html
both before and after the bug...
If you want something else... just ask!!!
regards.
Damien
Yes, I've done a fresh 0.86 install and followed all
scotts instructions...
--- Erik Kristensen [EMAIL PROTECTED] a écrit :
If I recall you switched to ez-ipupdate correct? Per
Scotts instructions?
-Erik
-- Original Message ---
From: Damien Dupertuis [EMAIL PROTECTED]
Ok, then based on you now using ez-ipupdate, it is not DynDNS that is causing
the problem. There is something else wrong and we are going to have to figure
it out.
-Erik
-- Original Message ---
From: Damien Dupertuis [EMAIL PROTECTED]
To: support@pfsense.com
Sent: Thu, 6 Oct
Indeed, this does not sound like a DynDNS bug at this point. What
happens if you click renew in the interfaces status screen?
Scott
On 10/5/05, Erik Kristensen [EMAIL PROTECTED] wrote:
Ok, then based on you now using ez-ipupdate, it is not DynDNS that is causing
the problem. There is
Indeed, this does not sound like a DynDNS bug at
this point. What
happens if you click renew in the interfaces status
screen?
You mean If I click renew on my browser when I see the
interface status page??? nothing odd... I don't
understand the point of your question...
Scott
On
27 matches
Mail list logo
