Re: [pfSense Support] Re: Less bandwidth available behind the firewall

2010-01-13 Thread Klaus Lichtenwalder
Am Mittwoch, den 13.01.2010, 11:14 -0500 schrieb Ugo Bellavance:
[...]
> 
> ## Linux box
> 
> net.ipv4.tcp_tso_win_divisor = 3
> net.ipv4.tcp_adv_win_scale = 2
> net.ipv4.tcp_app_win = 31
> net.ipv4.tcp_window_scaling = 1
> 
> net.core.rmem_default = 107520
> net.core.wmem_default = 107520
> net.core.rmem_max = 131071
> net.core.wmem_max = 131071
> 
[...]

Sorry, I'm not a BSD guy, but the Linux memory values seem somewhat low.
How much RAM do you have in that box? Theses values and the following
could be set somewhat more generous, depending on available RAM and BDP
(bandwidth delay product)

net.ipv4.tcp_mem=311904 415872  623808
net.ipv4.tcp_wmem= 4096 16384   4194304
net.ipv4.tcp_rmem= 4096 87380   4194304

Klaus

-- 
-------- 
 Klaus Lichtenwalder, Dipl. Inform.,  http://lklaus.homelinux.org/Klaus/
 PGP Key fingerprint: A5C0 F73A 2C83 96EE 766B  9C62 DB6D 1258 0E9B B6D1



signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


Re: [pfSense Support] Re: Less bandwidth available behind the firewall

2010-01-13 Thread Klaus Lichtenwalder
Am Mittwoch, den 13.01.2010, 11:14 -0500 schrieb Ugo Bellavance:
[...]
>=20
> ## Linux box
>=20
> net.ipv4.tcp_tso_win_divisor =3D 3
> net.ipv4.tcp_adv_win_scale =3D 2
> net.ipv4.tcp_app_win =3D 31
> net.ipv4.tcp_window_scaling =3D 1
>=20
> net.core.rmem_default =3D 107520
> net.core.wmem_default =3D 107520
> net.core.rmem_max =3D 131071
> net.core.wmem_max =3D 131071
>=20
[...]

Sorry, I'm not a BSD guy, but the Linux memory values seem somewhat low.
How much RAM do you have in that box? Theses values and the following
could be set somewhat more generous, depending on available RAM and BDP
(bandwidth delay product)

net.ipv4.tcp_mem = 311904   415872  623808
net.ipv4.tcp_wmem = 4096   16384   4194304
net.ipv4.tcp_rmem = 4096   87380   4194304

Klaus



-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org



[pfSense Support] Test-Upgrade from 1.2.3 to 2.0RC3 Alix

2011-06-24 Thread Klaus Lichtenwalder
Hi all,

I'm running pfSense 2.0RC3 (embedded) as a virtual instance to test
importing my old config into the new system. Real target will be my alix
board. I manually edited the interface section to account for the
different network names and of course network topology.
Loading the config file works fine, but after the reboot I get:


Warning: ksort() expects parameter 1 to be array, null given in
/etc/inc/certs.inc on line 359

Warning: ksort() expects parameter 1 to be array, null given in
/etc/inc/certs.inc on line 359

Warning: ksort() expects parameter 1 to be array, null given in
/etc/inc/certs.inc on line 359
..

 ** WARNING **

 Configuration could not be validated. A previous configuration was
restored.

Anything I could check for?
Klaus
-- 
----
 Klaus Lichtenwalder, Dipl. Inform.,  http://www.lichtenwalder.name
 PGP Key fingerprint: BF52 72FA 1F5A 1E29 C0F8  498C C4C6 633C 2821 97DA



signature.asc
Description: OpenPGP digital signature


Re: [pfSense Support] Test-Upgrade from 1.2.3 to 2.0RC3 Alix

2011-06-25 Thread Klaus Lichtenwalder
Am 24.06.2011 14:11, schrieb Ermal Luçi:
>> ..
> 
> I just put some more error checking in the code.
> Please test with latest snapshots of tomorrow.
> 
> Also would be useful if it happens again to have your certificate
> section from the xml
> even in private e-mails.
> 

Ermal,

I don't know whether this is the newest you meant, but up to now there's
no other image than: pfSense-2.0-RC3-1g-i386-20110624-1747-nanobsd.img

I restored my config and got the following, different result:

v cut here 
Updating configuration

 ** WARNING **

 Configuration could not be validated. A previous configuration was
restored.

 The failed configuration file has been saved as /conf/config.xml.bad}

done.
Cleaning backup cache...done.
...
Synchronizing user settings...
Warning: Invalid argument supplied for foreach() in /etc/inc/auth.inc on
line 211
done.
Starting webConfigurator...

 ** WARNING **

 Configuration could not be validated. A previous configuration was
restored.

 The failed configuration file has been saved as /conf/config.xml.bad}

done.

Configuring IPsec VPN...
Warning: Invalid argument supplied for foreach() in /etc/inc/vpn.inc on
line 274
done
Generating RRD graphs...done.
cut here^^^


The error in auth.inc seems to remove the admin account, btw. I had to
restore the Webconfigurator credentials:

  The webConfigurator admin password and privileges will be reset to
  the default (which is "pfsense").
  Do you want to proceed [y|n]?y

  Warning: Invalid argument supplied for foreach() in /etc/inc/auth.inc
  on line 196
  Failed to locate the admin user account! Attempting to restore access.


  The password for the webConfigurator has been reset and
  the default username has been set to "admin".

But to no avail...
Right now I can't log in...

Klaus

-- 
----
 Klaus Lichtenwalder, Dipl. Inform.,  http://www.lichtenwalder.name
 PGP Key fingerprint: BF52 72FA 1F5A 1E29 C0F8  498C C4C6 633C 2821 97DA



signature.asc
Description: OpenPGP digital signature


Re: [pfSense Support] Test-Upgrade from 1.2.3 to 2.0RC3 Alix

2011-06-25 Thread Klaus Lichtenwalder
Am 25.06.2011 20:52, schrieb Evgeny Yurchenko:
> 
> On Jun 25, 2011, at 2:06 PM, Klaus Lichtenwalder wrote:
> 
>> Am 24.06.2011 14:11, schrieb Ermal Luçi:
>>>> ..
>>>
>>> I just put some more error checking in the code.
>>> Please test with latest snapshots of tomorrow.
>>>
>>> Also would be useful if it happens again to have your certificate
>>> section from the xml
>>> even in private e-mails.
>>>
>>
>> Ermal,
>>
>> I don't know whether this is the newest you meant, but up to now there's
>> no other image than: pfSense-2.0-RC3-1g-i386-20110624-1747-nanobsd.img
>>
>> I restored my config and got the following, different result:
>>
[...]

>>
>> ---
> By old config you mean config from 1.2.3?
> 
> 
Correct. I just want to take my old config without too much hassle, as
probably regenerating manually would be. And from the list I gather that
people are able to do this...

Klaus

-- 

 Klaus Lichtenwalder, Dipl. Inform.,  http://www.lichtenwalder.name
 PGP Key fingerprint: BF52 72FA 1F5A 1E29 C0F8  498C C4C6 633C 2821 97DA



signature.asc
Description: OpenPGP digital signature


Re: [pfSense Support] Test-Upgrade from 1.2.3 to 2.0RC3 Alix

2011-06-26 Thread Klaus Lichtenwalder
Am 25.06.2011 21:13, schrieb Evgeny Yurchenko:
> ok, ok, we understand -)
> You are spamming the list by sending the same message every 5 minutes.
> 

Can you show headers? I definitely sent it only once

Klaus

-- 
----
 Klaus Lichtenwalder, Dipl. Inform.,  http://www.lichtenwalder.name
 PGP Key fingerprint: BF52 72FA 1F5A 1E29 C0F8  498C C4C6 633C 2821 97DA



signature.asc
Description: OpenPGP digital signature