After several days I "solved" the problem:

Either pfsense or the WRAP board is very sensible about long cables (My old router - linksys WRT54GL - worked with the same configuration perfectly).

| telephone socket – 1m cable -- Modem -- 20m cable -- WRAP board

does not work properly. In my case the connection came up, but pfsense was not routing any traffic (do not ask me why).

| telephone socket -- 20m cable -- Modem -- 1m cable -- WRAP board works smoothly.

Just in case someone has the same problem...

Hi, thx for reply

We are using reflected connections because local servers wasn't able to access other server using the Public IP, only the local IP

We need to be able to access Public IP

How can I make it works?

Tommy Boucher
Vice-President
Kenotronix Ltée
www.kenotronix.com

Is your WRAP on the most recent BIOS version?

I have a WRAP and last time I tried it, it worked fine. The WRAP is no longer manufactured or supported by its creator. Given its age, and the fact that the ALIX is a much better replacement for it that is supported, I doubt any heroic measures will be taken to make an "official" wrap-specific image.

There are no amd64 NanoBSD builds (yet, probably not for 2.0). The NanoBSD builds have their own set of features and limitations. They aren't right for everyone.

The major differences are:

NanoBSD only outputs to serial console (though there may be a VGA variant before 2.0 release) NanoBSD keeps the media read only except for discrete write operations. (This makes it unusable for many packages) NanoBSD has two main OS slices, and one separate configuration slice. Upgrade operations overwrite the currently unused "alternate" slice, and then boot from that. NanoBSD has no installer, it can only be imaged to a disk and run directly. NanoBSD only comes in 512MB, 1GB, 2GB, and 4GB sizes, so using it on HDDs would waste quite a lot of space. Using variable sizes is a non-trivial task.

The OS itself is basically the same between the two variants, though there are some kernel differences (a few drivers are left out, like certain SCSI drivers and RAID controllers).

Thanks…

it had nothing to do with the interface configuration or deleting and re-adding rules...

I think it was ARP cache issue more than anything else...

@dreamslacker:

Under Advanced system settings, you can disable NAT.  That will turn the box into a pure non-gateway router.

No that's to disable the filter. It also disables NAT, but that's not what you want if you only want to disable NAT. For that, see:
http://doc.pfsense.org/index.php/How_can_I_completely_disable_NAT%3F

Just do the regular installation using a live ISO. but keep in mind that you shouldn't install services like Squid to create massive read/write on the card as it will poot!

One more thing you need to consider is package management. dont try to install more than one package at the same time as it will create write errors at next boot and the package management will fail itself.

hope it helps.

Should be alright. Give it a whack.

hi
don't want to minimize the write access, i want redirect it to the hdd

thx

Sorry for the mistyping in fact is pfsense, Im changing from m0n0wall to pfsense because it is more flexible and complete.

Ill try your sugested configuration.

For the uVerse 2Wire routers yuo have to have the WAN connected to the 2Wire DMZ set up as DHCP, which is sounds like you did.

pfsense also can manage multiple Vlans on a single NIC.

Look in your interfaces to see if there is a vlan with the 172 set up on that nic

Consider bridging your LAN and WAN interfaces.  This will turn pfSense into a filtering bridge and should do what you need.

Unfortunately both of the howtos you linked are contributed and aren't on our Wiki or I could update them rather easily.

I did add a note here:
http://doc.pfsense.org/index.php/Port_Forward_Troubleshooting#Common_Problems

About needing an IP bypass for a port forward to a server behind a captive portal.

Several older copies of the config are kept in /conf/backup/

So if you get dropped to a shell prompt because something didn't work at boot, you could always pull one of the 25-30 or so backup configs from there.

Just install pfSense onto the new hardware and restore the config. It may ask you to reassign interfaces but aside from that, as long as the number of interfaces is the same (or greater) there shouldn't be any issues.

It would probably be possible to compile pfSense for it, but it likely doesn't have enough flash memory to store the OS or enough RAM to run it.

problem solved !!

Thanks Jimp !!! :)