Hi,

i upgraded a 1.0.1 Box to the latest Snapshot via Shell: http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/updates/pfSense-Full-And-Embedded-Update-1.2-BETA-1-TESTING-SNAPSHOT-05-14-2007.tgz

Everything wents fine, only the SSH didn't come up after the upgrade. (SSH failed to start)

I tried to disable the ssh deamon "System: Advanced functions", deleting the host_keys (rm /etc/ssh/ssh_host_*) under "Diagnostics: Execute command" and reenable the SSH Deamon again. But still doesn't work, it won't came up. Any additional ideas?

PS: Another Box with a few days earlier Snapshot works perfect.

[FIRST!]

The Sourceimage has to be decompressed FIRST!

Use

Code:

#>./mkflash_new.sh 256 pfSense.img

It seems there is no support fpr Memory Disks on your System.
Does a

Code:

#> kldload /boot/kernel/geom_md.ko

helps out?

May i ask you if this is correct?
Client (MTU 1500) -> LAN (MTU 1500) -> IPSEC -> WAN (MTU 1300) -> INET <- WAN (MTU 1300) <- IPSEC <- LAN (MTU 1500) <- Client (MTU 1500)

Unfortunately this doesnt help that much. I lowered the MTU on both sides to 1300 but the problem still exists.

Maybe this is important:
The WAN connections on both sides are fixed IP Adresses connected to somewhat transparent routers from the ISPs.
We dont use PPPoE over her. Maybe the MTU have to be modified on this machines instead?

Ok, some News: We have upgraded the RC3 to 1.0.1. Konfiguration was successfully imported and works great.
But there are still some strange behaviors. Example:
Copy a file via SCP from B to A works well, but vice versa it stop at 132 KB.
But a copy from B to A between Windows 2003 Server works. XP not.

Is this a matter of MTU? Where? Wich MTU has to be modified if it goes that way?
Do you need additional informations from me? Any other idea?

You are right, we will upgrade tommorrow evening.
Basicly this was the answer i want to hear

Since we are running 1.0.1 on A, isn't it a bad idea to upgrade B to the latest snapshot?
Upgrading A too is impossable because of 500 km between me and B ....

Greets and thanks for your prompt response!

Hi,

We have a strange Problem here with our IPSEC connection from pfSense to pfSense.

172.18.18.0/24 LAN <-> pfsense A <-> WAN <-> pfSense B <-> LAN 172.16.16.0/24

A: WRAP pfSense v1.01
B: WRAP pfSense v1.0RC3 (very busy Box, no chance to upgrade until yet)
Traffic from (A) to (B) is running fine, but the traffic from (B) to (A) stops after a specific amount of data (ex: scp stops at 132KB).

We played around with MTU, but nothing helps.
The problem looks pretty nearly exactly like this thread (http://forum.pfsense.org/index.php/topic,963.0.html),
but we do not have any D-Link, pure pfSense

I do not have any idea, could some light a fire for me, pls?

Greetings,
Marcel

http://wiki.pfsense.com/wikka.php?wakka=FlashHowToSkript

http://wiki.pfsense.com/wikka.php?wakka=FlashHowToSkript

[resize]

Hi,

New in this Forum, i say hello to everyone interested.
I have recreate a skript to create 128, 256, 512 or 1gb Images out of the original 64mb embedded one.
Works only on FreeBSD, feel free to modify it for Linux.

How to use:
Save skript in your homedir.
#> mv mkflash_new.txt mkflash_new.sh
#> chmod +x mkflash_new.sh
Download latest Snapshot from http://www.pfsense.com/~sullrich/
Get pfSense.img.gz from there and place it in your homedir
Unpack pfSense.img.gz with
#> gzip -d pfSense.img.gz
Be shure to get root-rights
#> su
execute skript like:
Usage: /home/marcel/mkflash_new.sh {128|252|512|1024} {Originalimage}
Example: #> /home/marcel/mkflash.sh 128 /home/marcel/pfSense.img

Voila, take a look on the new image-file:
pfSense-128MB.img.gz
pfSense-128MB.img.gz.md5

Have fun,
Marcel

edit: changed heading to resize image....