I found out the problem it is openwrt if i have both vlans (bridged on pfsense) as trunk input  , any way if one is then only untagged to a single switchport, the openwrt don't forward traffic back on the vlan trunk

thx

max

PERFECT!!

Thank you so much!!

@phil.davis:

Boots much better now there is a kernel  ;)

;D :D ;D :D

Oh you need probably a different thread for you.
You have a different issue than the modem show up on your list.

Please create another thread.

Sounds interesting.

I have a test machine running pfsense 2.1 with old snaphot on PVE 2.2.
Will do a PVE update and try the newer snapshots of pfsense because I had some problem with CPU detection.

Thank you for your work!

Use NPt to map the non-routable segment to the routed segment.

No it does not work that way.
What you are trying to do is something not possible in pfSense.

Usually some firewalls have an option to NAT before IPSec VPN which is not supported by pfSense.

You either NAT or not the whole thing.

@foonus:

We identified that something changed after the 12-13 that causes this "Fatal Trap 12" on certain setups.      . . . .
http://forum.pfsense.org/index.php/topic,63484.0.html

This crash occurs in attach processing of the keyboard driver.The crash in the referenced topic occurs in detach processing of the bge driver.
It is not obvious these are related other than having a similar crash cause: "Fatal Trap 12".

I think this approach is not the right
To add a new language requires changing the system functions.
Perhaps it is best to search pfsense.mo files, compiling a list of languages ​​on it.
And MO Files Management (add / delete / replace) possible make as separate package as my old package for 2.0.х

Hi,

it running last but one but now the latest and that work for me.
Many thanks!

Regards Andreas

Thanks to all for the pointer. pfSense community is awesome! :D

Try with tomorrows snapshots.

@bradenmcg:

I've been occasionally hit by WAN link problems as you mentioned, so I've been searching all over for the best place to discuss and try to help resolve them.

I see you have recently posted to http://forum.pfsense.org/index.php/topic,57258.0.html (DHCP on WAN suddenly started failing) and http://forum.pfsense.org/index.php/topic,63599.0.html (WAN link goes down every 12 hours (DHCP related?)) I suggest you continue the discussion in the more appropriate of those two topics.

@bradenmcg:

The one thing that is baffling to me is that I did not have any problems on 1.2.x or earlier 2.0 builds, I only started to see issues on 2.0.2 or 2.0.3, which makes me wonder if "stuff was changed."

Change in version number almost always means stuff was changed. There is a link on the pfSense doc pages (http://doc.pfsense.org) to "release notes" summarizing changes in recent releases.

This is a more detailed tutorial on how to enable TRIM.

http://forum.pfsense.org/index.php/topic,63656.msg344604.html#msg344604